Authentication Error even when new token

Monocle

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!

Monocle

Ok try again now … should be working now.

Looks like I have more work to do to get this stable again. I’ll be working on this later this week. The Amazon EC2 instance keeps locking up … which causes database connection issues.

Thanks, Robert

Anundertaker

Thanks Robert. Up and running again.

Good luck with the EC2 instance. 🤞

McKinley

@Monocle not sure if this is from the same issue. But it has been pretty unstable since the first auth issue a month ago. Here lately I have to restart the gateway. Sometimes needing to disable/enable the skill also.

Thanks Robert!

Anundertaker

@McKinley
@Monocle

Same for me regarding instability. I’ve had to manually restart my gateway service every few days. Today was the first time since September I’ve had issues with the Alexa skill as well, though.

Monocle

@Anundertaker @McKinley

Yes the instability is related to the same issue a few weeks back. I’m planning on digging into the issue and reworking a few things to regain stability this week. I think the hosted VM is running out of memory so going to upsize.

Thanks, Robert