Authentication Error even when new token

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

SchmuFoo

@Monocle I think this feedback was for @justincheger

Monocle

@SchmuFoo

You are correct. I updated the post. Thanks, Robert

deepbluesee

@Monocle
Today Same error again

slime-uk

Getting a 401 again today - anyone else? Thanks

Oct 01 09:15:54 pimonoclerp3 monocle-gateway[597]: [Monocle Connecting]

Oct 01 09:15:55 pimonoclerp3 monocle-gateway[597]: Monocle API Authentication Error; invalid or missing token.
Oct 01 09:15:55 pimonoclerp3 monocle-gateway[597]: 2024-10-01T08:15:55.115Z [ERROR] [Monocle Error] Unexpected server response: 401
Oct 01 09:15:55 pimonoclerp3 monocle-gateway[597]: [ ‘[Monocle Error]’, ‘Unexpected server response: 401’ ]
Oct 01 09:15:55 pimonoclerp3 monocle-gateway[597]: [Monocle Disconnected]
Oct 01 09:15:55 pimonoclerp3 monocle-gateway[597]: [Monocle Reconnecting] … in 64 seconds (attempt #12)

SchmuFoo

@slime-uk said in Authentication Error even when new token:

Getting a 401 again today - anyone else? Thanks

Indeed