ALEXA ECHO SHOW 5 - TOKEN ERROR - Assistance Needed: Troubleshooting "monocle-gateway"
-
Subject: Assistance Needed: Troubleshooting “monocle-gateway”
Hello,
I’m encountering difficulties with the “monocle-gateway” setup. Upon execution, the following error arises:
Monocle error unexpected server response: 401
Monocle API Authentication Error; invalid or missing token
Important Points:The token is properly installed.
Cameras are successfully configured on the monocle website and tested.
The issue seems to lie with the server startup.
My device is an ALEXA ECHO SHOW 5.
Could someone provide assistance on this matter? -
Hi
This appears to be a global issue at the moment as i am receiving this on multiple setups.
@Monocle Are you able to have a look as appears to be a backend issue?
I think it is also stopping people linking the alexa skill.
-
@RS said in ALEXA ECHO SHOW 5 - TOKEN ERROR - Assistance Needed: Troubleshooting "monocle-gateway":
This appears to be a global issue at the moment as i am receiving this on multiple setups.
Yes I have the same problem since a few days (~2 Days) and “happy” to see that I am not alone.
-
-
@edgbarr
Same error for a couple of days now:Jan 31 14:02:45 monacle monocle-gateway[82757]: Monocle API Authentication Error; invalid or missing token. Jan 31 14:02:45 monacle monocle-gateway[82757]: 2024-01-31T14:02:45.866Z [ERROR] [Monocle Error] Unexpected server response: 401 Jan 31 14:02:45 monacle monocle-gateway[82757]: [ '[Monocle Error]', 'Unexpected server response: 401' ]
-
same here.
-
Yep, same. Tried creating a new API key for giggles, but no luck.
-
-
Same issue here, I tried to reconfigure the entire camera as well as regenerating the token, no luck so far.
-
Hello everyone! (This is my first post here, so please be gentle lol)
The same issue is happening on my server, and I’m happy I came across this post when doing a google search. I recently upgraded my home server that I had for years to a pretty new snazzy model. I tried running the application and have the same missing token error.
I have kinda a related side question - since I moved the monocle folder to a new hardware setup, is there anything further I have to do to normally get it working? (I’ve read somewhere about generating a new token, but I’m honestly a bit inexperienced with this software - I got it working a couple of years ago and it’s been pretty steady.
-
This post is deleted! -
@thurmane0 There is currently an issue with authentication with the alexa skill associated with Monocle. My assumption is you would need to create a new token as you have moved to new hardware, but i am no expert. but, you wont be able to authenticate in the skill if you get that far.
I just didnt want you to fight the token issue and then get stuck and assume there is something wrong with your token…if you run into issue at all, assume it is on the authentication side (several open topics on the forum) and not spend many cycles on the token until the auth issue is solved by @Monocle.
Of course, just my two cents…
-
-
-
Who knows an alternative to monocle ?
-
@bouboun59 I hope Robert is OK.
-
@Graham2607 said in ALEXA ECHO SHOW 5 - TOKEN ERROR - Assistance Needed: Troubleshooting "monocle-gateway":
@bouboun59 I hope Robert is OK.
Robert have GoogleHome Now… Alexa left Robert :d
-
If the person developing this doesn’t want to host this anymore, I am willing to host this/get this on my dev account to get this going for everyone.
-
@ALL.
Sorry, about the delay in getting this issue resolved. I was away from my office all last week and unable to access the necessary details and resources to work on this problem.
PLEASE TRY AGAIN NOW. (You may need to restart your Monocle Gateway instances.)
The issue started when I replaced all the SSL certificates at the end of January. Even though we have a pre-paid and valid 5 year certificate, the SSL rules require that it gets replaced annually now. So after updating all the certificates and restarting all the services that allow Monocle to function, it all appeared to be working from my local testing. However somewhere in the changes … the Monocle/Alexa authentication service failed to re-connect to the Monocle backend database properly. Perhaps it was holding onto (cached) the previous SSL for its secure connection which then expired. I’ll have to dig a bit deeper to better understand why it continued to fail to connect over the course of several days, but I believe this was the underlying issue causing failed account re-linking, failure to refresh Alexa tokens and failure for Monocle Gateway to reconnect and throw 401 errors.
Please let me know if any of you have further issues getting Monocle working again.
Thanks, Robert
-
Robert have GoogleHome Now… Alexa left Robert :d
Not on GoogleHome :-)
Mostly on HomeAssistant now for everything except cameras :-)-Robert