For anyone else who runs into this i never did resolve it, i just made a task to restart the service every half hour.

@mfoster978

Here’s is a log.txt I pasted the log into.

https://drive.google.com/file/d/1FO3geAw1FBGNntQnoj_adqiVaLk8zcav/view?usp=drivesdk

Please let me know what you think.

Thanks,
Mike

Pastebin - sanitized Gateway output

https://pastebin.com/5GUuM0RW

First run is the Overview “camera” which is the problem child

Second run is a working camera - Amcrest front door.

@edgbarr

The computer running Monocle Gateway does not need a public IP address on the Internet. It can certainly be a private IP address inside your network behind your router/NET. It does however require outbound Internet access to communicate with the monocle services. This computer also need to be accessible on your network from the Alexa devices. The Alexa devices will talk to the Monocle Gateway when requesting camera stream rather than talking to your IP cameras directly.

Another question, if I change the Monocle settings on the official website, do I need to generate a new token?

No, settings are communicated for each camera stream every time the camera stream is requested/triggered from Alexa. We do suggest generating a new token if your IP address changes on the computer running Monocle Gateway. It’s not required but it can take up to 24 hours for the new IP address to get propagated in the DNS record. Thus a new token speeds this process up by issuing a new DNS record fore your Monocle Gateway instance.

Thanks, Robert

@arthur360

I notice two issues in the log file.

1.) It looks like there is another instance of Monocle Gateway running and is already using the ports 8555 and 443. This is probably because you have the Windows Service for Monocle Gateway running in the background. (see: https://monoclecam.com/monocle-gateway/install/windows#windows-service).
Try stopping the service before running the Monocle Gateway executable in your command shell.

2.) The second error : [ERROR] [Monocle Error] getaddrinfo ENOTFOUND api.monoclecam.com is suggesting that the computer can’t communicate to the Internet or at least is not able to resolve the address api.monoclecam.com via a DNS server.

Thanks, Robert

@Monocle thanks for the heads up Robert. I’m looking at my driveway right now on an echo and it’s working.

@Monocle said in ALEXA ECHO SHOW 5 - TOKEN ERROR - Assistance Needed: Troubleshooting "monocle-gateway":

But it’s still a side-project and freely provided and hosted :-). So support is not always immediate and sadly in this case a bit more delayed than usual. I’m usually able to address any server-side related outage in a more timely manner. But I dropped the ball this time around.
Thanks, Robert

Thanks a lots @Robert it was a joke ;)
Your work it’s very good, and i know, that isn’t easy to manager a free project.
Monocle it’s very cool project, and I will make a donation

great

good job
a long life for you and monocle ;)

Working great now. Thanks so much!

OK, everything should be working again now.

Thanks, Robert

Working again. Thanks.

@andi said in Unable to login via Alexa Skill:

@Monocle Hi Robert,

Thank you for your fast and in-depth support. I could solve the issue by switching to the Desktop version of the website. It seems the Alexa App uses Google Chrome on my Android device.

Using the Desktop Version the login worked fine.

With best regards

Andreas

Glad to hear its working now.

@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

@Deathstalker

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

@cincyitguy @toto was kind enough to point me at this post. Just to completely agree I cannot get this to work either. Like you certain the streams are there and there are no network issues but the same dreaded cannot connect to the camera…so no help but at least you know your not alone.

@Toto thanks great Toto, well your reply telling me that it’s a known unresolved problem. The fact it doesn’t work…not so great.

@dannyboy91

Hi. I think you need the @fixaudio tag as well