Certificate has expired error?

milesfbim

2020-05-30T15:44:06.105Z [ERROR] [Monocle Error] certificate has expired
[ ‘[Monocle Error]’, ‘certificate has expired’ ]
[Monocle Disconnected]
[Monocle Reconnecting] … in 383 seconds (attempt #76)
[Monocle Connecting]
2020-05-30T15:50:29.481Z [ERROR] [Monocle Error] certificate has expired
[ ‘[Monocle Error]’, ‘certificate has expired’ ]
[Monocle Disconnected]
[Monocle Reconnecting] … in 387 seconds (attempt #77)
[Monocle Connecting]
2020-05-30T15:56:56.821Z [ERROR] [Monocle Error] certificate has expired
[ ‘[Monocle Error]’, ‘certificate has expired’ ]
[Monocle Disconnected]
[Monocle Reconnecting] … in 393 seconds (attempt #78)
[Monocle Connecting]
2020-05-30T16:03:30.178Z [ERROR] [Monocle Error] certificate has expired
[ ‘[Monocle Error]’, ‘certificate has expired’ ]
[Monocle Disconnected]
[Monocle Reconnecting] … in 395 seconds (attempt #79)
[Monocle Connecting]
2020-05-30T16:10:05.523Z [ERROR] [Monocle Error] certificate has expired
[ ‘[Monocle Error]’, ‘certificate has expired’ ]
[Monocle Disconnected]
[Monocle Reconnecting] … in 402 seconds (attempt #80)
[Monocle Connecting]
2020-05-30T16:16:47.892Z [ERROR] [Monocle Error] certificate has expired
[ ‘[Monocle Error]’, ‘certificate has expired’ ]

Monocle

@milesfbim

Thanks for the post . I am now able to reproduce the error on my end. Looking into it now.

Thanks, Robert

Dalekw1

@Monocle Server Error.PNG

DAD405

On a Installation running on an Orange-pie (like raspberry)
Just for the records in case system matter.

Monocle

So the issue seems to be that a ROOT certificate in the verification chain has expired as of today.

You can see the issue here:
https://www.sslshopper.com/ssl-checker.html#hostname=monoclecam.com

Common name: USERTrust RSA Certification Authority
Organization: The USERTRUST Network
Location: Jersey City, New Jersey, US
Valid from May 30, 2000 to May 30, 2020
Serial Number: 13ea28705bf4eced0c36630980614336
Signature Algorithm: sha384WithRSAEncryption
Issuer: AddTrust External CA Root

REF:

milesfbim

Thanks does that mean it will be fixed?

Monocle

@milesfbim

Yes, I’ll get it fixed – -hopefully by the end of the day.

Monocle

The SSL issue should be resolved now!

We had the certificate provider reissue a new SSL certificate with a new verification chain (eliminating the expired root) and replaced the SSL certificates on our servers.
Please let me know if anyone is still having connectivity issues.

PS: If you unlinked/disabled the Monocle skill, you will have to RE-LINK the skill to your Alexa account.

Thanks, Robert

TangoFoxtrot

Many thanks for getting this fixed so quickly. Had to restart my gateway but beyond that all looking good again now.

Loving the system overall, it’s been really great!

samern

@Monocle I’m still seeing an issue. Now my account is relinked and all the devices discovered fine, but the Echo Show still won’t display anything (keeps insisting that the cameras are not responding). I rebooted my controller and restarted my cameras to no avail. Any thoughts/tips/comments?

supermikez

@Monocle I’m also still seeing the same issue @samern is seeing–account and devices are fine. Echo Show won’t display anything - saying cameras are not responding. But I can play my camera feeds through VLC.

DAD405

Monocle-gateway is Working again.
Just tested cam Display on echo show and Working.
Thank you for getting it sorted out quick.

milesfbim

All working here now good work guys 👍

bobkschmidt

@supermikez @Monocle
Same issue here. Thought it was something on my end. Any troubleshooting?

andrerod

@samern said in Certificate has expired error?:

g an issue. Now my account is relinked and all the devices discovered fine, but the Echo Show still won’t display anything (keeps insisting that the cameras are not responding). I rebooted my controller and restarted my cameras to no avail. Any th

I’m seeing the same issue. Essentially i see the requests arriving at port 443 using tcp dump but the monocle gateway log doesn’t show them arriving at the gateway. This started happening since yesterday.

Essentially it’s all the same as other folks mentioned from a end user perspective - alexa says it can’t connect to the cameras.

Monocle

For those of you where its still not working … what system/OS are you running your Monocle Gateway on?
In the meantime … I’ll go check the SSL certificates for the gateways and see if there are any problems there.

Thanks, Robert

Monocle

@andrerod

Can you share the log output from Monocle Gateway while you are making a camera requests. I would expect it to at least show you an “Initialize Camera” blurb. This should be followed immediately by the incoming camera TCp/RTSP requests on port 443. Using tcp dump, are the incoming connections you see coming from Alexa devices in your home?

Thanks, Robert

andrerod

Hey Robert,

Somehow adding an explicit “@tunnel” tag for some of the cameras did the trick and i now see the requests at least being processed by the monocle-gateway. That fixed most of my cameras - somehow two of them are still not working (i see some requests return 401s (unauthorized) from the cameras and im not quite sure yet why but i think the problem must be on my side ? - i did update all the credentials, i believe, correctly, just in case but no luck yet.).

samern

@Monocle I am running Ubiquiti/Unify with an NVR and have a newer Echo Show. The Echo clearly knows the cameras are there because it discovered them.

bobkschmidt

@andrerod @Monocle this fixed the issue for me (Amcrest/Windows 10/ QNAP QVR Pro). Never needed @tunnel until today, but it works :)