@dannyboy91

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

@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.

@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

@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

@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.

Working again. Thanks.

OK, everything should be working again now.

Thanks, Robert

Working great now. Thanks so much!

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

@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

@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

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

@vmsman Thank you for replying. I went to your chat, but not sure what to do there. Are you affiliated with Monocle? Thanks again!

@berto1886 My fault, problem solved. I’d to add a second address to my raspberry (where monocle gateway is installed) where the 443 door is totally dedicated to this service and not in sharing with apache server