• Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    Certificate has expired error?

    Support
    12
    32
    1964
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • D
      DAD405 last edited by DAD405

      1C706059-48EF-4735-BBEB-03DCE9150C9C.jpeg

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

      1 Reply Last reply Reply Quote 0
      • Monocle
        Monocle last edited by

        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:

        • https://calnetweb.berkeley.edu/calnet-technologists/incommon-sectigo-certificate-service/addtrust-external-root-expiration-may-2020
        • https://support.sectigo.com/articles/Knowledge/Sectigo-AddTrust-External-CA-Root-Expiring-May-30-2020

        Monocle: https://monoclecam.com
        Getting Started | Troubleshooting Guide | FAQ | Contact Support

        1 Reply Last reply Reply Quote 0
        • M
          milesfbim last edited by

          Thanks does that mean it will be fixed?

          Monocle 1 Reply Last reply Reply Quote 0
          • Monocle
            Monocle @milesfbim last edited by

            @milesfbim

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

            Monocle: https://monoclecam.com
            Getting Started | Troubleshooting Guide | FAQ | Contact Support

            1 Reply Last reply Reply Quote 0
            • Monocle
              Monocle last edited by

              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

              Monocle: https://monoclecam.com
              Getting Started | Troubleshooting Guide | FAQ | Contact Support

              S 1 Reply Last reply Reply Quote 1
              • T
                TangoFoxtrot last edited by

                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!

                1 Reply Last reply Reply Quote 0
                • S
                  samern @Monocle last edited by

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

                  1 Reply Last reply Reply Quote 1
                  • S
                    supermikez last edited by

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

                    B 1 Reply Last reply Reply Quote 1
                    • D
                      DAD405 last edited by

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

                      1 Reply Last reply Reply Quote 0
                      • M
                        milesfbim last edited by

                        All working here now good work guys šŸ‘

                        1 Reply Last reply Reply Quote 0
                        • B
                          bobkschmidt @supermikez last edited by

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

                          1 Reply Last reply Reply Quote 0
                          • A
                            andrerod last edited by

                            @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 1 Reply Last reply Reply Quote 0
                            • Monocle
                              Monocle last edited by

                              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: https://monoclecam.com
                              Getting Started | Troubleshooting Guide | FAQ | Contact Support

                              S 1 Reply Last reply Reply Quote 0
                              • Monocle
                                Monocle @andrerod last edited by

                                @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

                                Monocle: https://monoclecam.com
                                Getting Started | Troubleshooting Guide | FAQ | Contact Support

                                1 Reply Last reply Reply Quote 0
                                • A
                                  andrerod last edited by

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

                                  B 1 Reply Last reply Reply Quote 0
                                  • S
                                    samern @Monocle last edited by

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

                                    1 Reply Last reply Reply Quote 0
                                    • B
                                      bobkschmidt @andrerod last edited by

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

                                      1 Reply Last reply Reply Quote 0
                                      • G
                                        Graham2607 @Monocle last edited by

                                        @Monocle Hi since expired certificate issue of 29th May my cameras no longer display on Echo show 10 2nd generation, just says ā€˜the camera is not responding’. Cameras are Qvis connected to network on fixed ip addresses. All been fine for a year.
                                        Tried disabling Alexa skill and re-enabling, rebooting show 10. still the same.
                                        These cameras are not connected via the Gateway. Stream works fine in VLC
                                        Any suggestions much appreciated

                                        Graham

                                        1 Reply Last reply Reply Quote 0
                                        • Monocle
                                          Monocle last edited by Monocle

                                          Thank you all for the reports and information provided!

                                          I think we have found and resolved the final issue with this SSL root expiry debacle. For those of you who were not using the monocle gateway or not using the @tunnel or @proxy tags, there was one more server certificate that was still using the old validation chain. This resource has been updated and everything should be working as it was prior to this certificate issue.

                                          Thanks, Robert

                                          Monocle: https://monoclecam.com
                                          Getting Started | Troubleshooting Guide | FAQ | Contact Support

                                          G S 2 Replies Last reply Reply Quote 0
                                          • G
                                            Graham2607 @Monocle last edited by

                                            @Monocle Hi Robert, I can confirm all is working again, many thanks for the swift action. Graham

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Privacy Policy  |  Terms & Conditions

                                            Ā© 2018 shadeBlue, LLC.