Authentication Error even when new token

[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

[McKinley]

@slime-uk @admin @Monocle

Same auth/API token error - Disconnected from monocle server on 9/30

Tried going to website+forums and received a cloudflare error saying possible load balancing is needed.

• not sure if they are related

Thank you

[mp101]

@SchmuFoo yup started yesterday afternoon uk for me

[Anundertaker]

@slime-uk same here

@admin @Monocle - thanks!

[Vicore]

It looks like the same issues as before, if you log out of the skill in Alexa you can not log back in and get a “login failed” please contact support banner. I assume it is a cert that needs updating. @Monocle

[memarkham303]

@Monocle I’m in the same boat. Rats.

[Monocle]

@ALL

Please try again. Not a certificate issue this time – just a temporary database server outage yesterday and one of the services that makeup the backend failed to reconnect. Added improved “reconnect” logic today so hopefully this issue will “self-heal” next time.

(In some cases, you may have to restart your Monocle Gateway service.)

Thanks, Robert

[memarkham303]

@Monocle Thanks, it’s better now!

[Anundertaker]

@Monocle many thanks - running fine now.

[mp101]

@Monocle thank you
Working again

[Anundertaker]

@admin @Monocle

The Alexa skill disabled itself and now won’t authenticate, as of today.

Thanks once again for your help!

[deepbluesee]

@Anundertaker

Yes same problem here! Skill disabled be itself and no login possible!