Authentication Error even when new token

sheminasalam1

This is the error

Monocle API Authentication Error; invalid or missing token.

Rich

I am getting an error when trying to enable the Monocle skill via the Alexa app, this might be linked? @Monocle could you take a look, please?

foz111

Same problem here, this happened a while ago requires owner to fix from memory

Rich

@foz111 Yeah, an expired cert, IIRC?

SchmuFoo

Hi just came here to check if there are other users who are facing this API 401 Error out of nothing

Sep 05 20:10:24 loxberry monocle-gateway[6382]: [RTSP Server Started]
Sep 05 20:10:24 loxberry monocle-gateway[6382]: Monocle API Authentication Error; invalid or missing token.
Sep 05 20:10:24 loxberry monocle-gateway[6382]: 2024-09-05T18:10:24.451Z [ERROR] [Monocle Error] Unexpected server response: 401
Sep 05 20:10:24 loxberry monocle-gateway[6382]: [ '[Monocle Error]', 'Unexpected server response: 401' ]
Sep 05 20:10:24 loxberry monocle-gateway[6382]: [Monocle Disconnected]
Sep 05 20:10:24 loxberry monocle-gateway[6382]: [Monocle Reconnecting] ... in 5 seconds (attempt #1)

McKinley

@Rich, I am having the same issue with account linking with Amazon Alexa - was working just fine until sometime this morning.

I checked my gateways logs - everything there seems fine - no api token error.

pathfinder

I am also receiving the “Monocle API Authentication Error; invalid or missing token.” error.

Monocle

FYI … Working on this issue now and it should be resolved and working again later today!

Thanks, Robert

Anundertaker

@Monocle Hi Robert,

Just got “Monocle API Authentication Error; invalid or missing token.” recurring, as of about the last couple of hours.

Thank you for your help with this.

nor1don

I am having the same error… I changed token but still the same issue.

Sep 11 00:27:03 raspberrypi monocle-gateway[11159]: 2024-09-10T21:27:03.441Z [ERROR] [Monocle Error] Unexpected server response: 401
Sep 11 00:27:03 raspberrypi monocle-gateway[11159]: [ ‘[Monocle Error]’, ‘Unexpected server response: 401’ ]
Sep 11 00:27:03 raspberrypi monocle-gateway[11159]: [Monocle Disconnected]
Sep 11 00:27:03 raspberrypi monocle-gateway[11159]: [Monocle Reconnecting] … in 23 seconds (attempt #4)
Sep 11 00:27:26 raspberrypi monocle-gateway[11159]: [Monocle Connecting]
Sep 11 00:27:26 raspberrypi monocle-gateway[11159]: Monocle API Authentication Error; invalid or missing token.
Sep 11 00:27:26 raspberrypi monocle-gateway[11159]: 2024-09-10T21:27:26.909Z [ERROR] [Monocle Error] Unexpected server response: 401
Sep 11 00:27:26 raspberrypi monocle-gateway[11159]: [ ‘[Monocle Error]’, ‘Unexpected server response: 401’ ]
Sep 11 00:27:26 raspberrypi monocle-gateway[11159]: [Monocle Disconnected]
Sep 11 00:27:26 raspberrypi monocle-gateway[11159]: [Monocle Reconnecting] … in 25 seconds (attempt #5)

justincheger

I am getting the same error on windows.

[Monocle Connecting]
Monocle API Authentication Error; invalid or missing token.
2024-09-11T00:52:07.365Z [ERROR] [Monocle Error] Unexpected server response: 401
[ ‘[Monocle Error]’, ‘Unexpected server response: 401’ ]
[Monocle Disconnected]

deepbluesee

Same error today i Changed nothing
Solution?

foz111

This was fixed but now seems to be broken again as the posts above suggest

nor1don

We wait for Developers to fix the issue. I hope they fix it soon. It has been a life saver solution to me.

Toto

@Robääääärrrtttt
your help is very welcome again :-)

Thank you in advance

Best
Toto

Monocle

Try it again now.

I think I see the underlying issue and will need to put in a more permanent fix but it should be working now.

Thanks, Robert

deepbluesee

@Monocle
Yes works again without any problems
Thanks

SchmuFoo

@Monocle Indeed after an daemon stop/start it is working again, Thank you very much

justincheger

I am still getting an error below, any help would be great

Windows Machine

2024-09-11T22:28:11.079Z [ERROR] [PROXY SERVER ERROR] Error: listen EADDRINUSE: address already in use 0.0.0.0:8555
[
  '[PROXY SERVER ERROR]',
  Error: listen EADDRINUSE: address already in use 0.0.0.0:8555
      at Server.setupListenHandle [as _listen2] (node:net:1319:16)
      at listenInCluster (node:net:1367:12)
      at doListen (node:net:1505:7)
      at processTicksAndRejections (node:internal/process/task_queues:84:21)
      at process.runNextTicks [as _tickCallback] (node:internal/process/task_queues:65:3)
      at Function.runMain (pkg/prelude/bootstrap.js:1848:13)
      at node:internal/main/run_main_module:17:47 {
    code: 'EADDRINUSE',
    errno: -4091,
    syscall: 'listen',
    address: '0.0.0.0',
    port: 8555
  }
]
2024-09-11T22:28:11.083Z [ERROR] [RTSP Server Error] listen EADDRINUSE: address already in use 0.0.0.0:8555
[
  '[RTSP Server Error]',
  'listen EADDRINUSE: address already in use 0.0.0.0:8555'
]
2024-09-11T22:28:11.083Z [ERROR] [PROXY SERVER ERROR] Error: listen EADDRINUSE: address already in use 0.0.0.0:443
[
  '[PROXY SERVER ERROR]',
  Error: listen EADDRINUSE: address already in use 0.0.0.0:443
      at Server.setupListenHandle [as _listen2] (node:net:1319:16)
      at listenInCluster (node:net:1367:12)
      at doListen (node:net:1505:7)
      at processTicksAndRejections (node:internal/process/task_queues:84:21)
      at process.runNextTicks [as _tickCallback] (node:internal/process/task_queues:65:3)
      at Function.runMain (pkg/prelude/bootstrap.js:1848:13)
      at node:internal/main/run_main_module:17:47 {
    code: 'EADDRINUSE',
    errno: -4091,
    syscall: 'listen',
    address: '0.0.0.0',
    port: 443
  }
]
2024-09-11T22:28:11.084Z [ERROR] [RTSP Server Error] listen EADDRINUSE: address already in use 0.0.0.0:443
[
  '[RTSP Server Error]',
  'listen EADDRINUSE: address already in use 0.0.0.0:443'
]

Monocle

@justincheger

This is a different error.

[RTSP Server Error] listen EADDRINUSE: address already in use 0.0.0.0:8555
...
[PROXY SERVER ERROR] Error: listen EADDRINUSE: address already in use 0.0.0.0:443

This is telling us that you probably already have an (second) instance of Monocle Gateway running. Probably in the background as a Windows service. Basically ports 443 and 8555 are already being used and the new instance cannot bind to those ports.

Try using this command to stop the background service first:
monocle-gateway.exe --stop

See this page for additional details:
https://monoclecam.com/monocle-gateway/install/windows#windows-service

Thanks, Robert