Authentication Error even when new token
-
@Monocle I’m in the same boat. Rats.
-
@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
-
@Monocle Thanks, it’s better now!
-
@Monocle many thanks - running fine now.
-
@Monocle thank you
Working again -
-
Yes same problem here! Skill disabled be itself and no login possible!
-
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
-
Thanks Robert. Up and running again.
Good luck with the EC2 instance. 🤞
-
@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!
-
-
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
-
@Monocle
Different das same Problem:
Reactive the skill ends up in logging in issue. -
I have been working on the service backend heavily today; so there were some extended outages yesterday/today.
Please try it again now. You may have to re-link the Monocle Skill to your Alexa account.Thanks, Robert