Navigation

    Home
    All Categories
    • KEEN Trail Camera
    • Announcements and News
    • Wishlist
    • #ReolinkTrial
    • Discussion About Products
    • Reolink Captures
    • Reolink Client & APP
    #ReolinkTrial
    Reolink Captures
    Log in to post
    Guest
    • Guest
    • Register
    • Login

    Spring Renewal - Share Spring Time-lapse to Win Cameras

    Learn More

    360° Fisheye Indoor Camera - Why We Made Fisheye & What We Have Done Learn More

    Full Introduction and Tips for Shooting Time-lapse Video with Reolink Camera Learn More

    New Reolink Client v.8.8.5 - Auto Upgrade Client Feature! Learn More

    HTTPS "Not Secure"

    Reolink Client & APP
    3
    3
    49
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • bradleythomasthornton_579789494964573
      bradleythomasthornton last edited by

      Today I become unable to locally access my NVR via LAN and when I turned HTTPS on in server settings I was able to access the NVR again, however I am being presented with a "Invalid certificate" warning.

      Does anyone have any insight to what this is about?

      undefined

      Reply Quote
      Share
      • Share this Post
      • Facebook
      • Twitter
      • copy the link
        Copied!
      0
        • joseph chircop_497308027822318
          joseph_chircop Global Moderator @bradleythomasthornton last edited by joseph chircop_497308027822318

          @bradleythomasthornton_579789494964573 When you changed the server to HTTPS, it’s telling the browser to connect via a different port (443 – HTTPS), whereas normally, you connect via (80 – HTTP). Without an SSL Certificate (exchanged during handshake), the server would refuse the connection. So, in short words, HTTPS is simply not possible without a certificate which encrypts the communication between the NVR and the browser. So previously you were connecting to NVR using HTTP and all of a sudden you were not able. And when you enabled HTTPS then you were able to access. I think when you use HTTPS there was a redirect 301 and connected to HTTP and you got that message.

          Reply Quote
          Share
          • Share this Post
          • Facebook
          • Twitter
          • copy the link
            Copied!
          0
          • Crimp On_62210811129
            Crimp On @bradleythomasthornton last edited by

            Modern web browsers complain about any SSL certificate that is not properly "signed" by a recognized certificate authority. Companies who enable https (encrypted) web browsing often include an SSL certificate that is "self-signed", and web browsers throw a fit. (maybe not the correct technical term).

            Just ignore the warning and proceed to the NVR web site. The next time, that web browser should remember and not show the warning.

            Reply Quote
            Share
            • Share this Post
            • Facebook
            • Twitter
            • copy the link
              Copied!
            0
            View 0 replies
          • First post
            Last post
          All Categories
          Announcements and News Reolink Client & APP Discussion About Products #ReolinkTrial Reolink Captures Wishlist KEEN Trail Camera
          Never miss Reolink hot deals, news, and updates tailored for you.

          Thanks for your subscription!

          Please enter a valid email address.

          Oops… Something went wrong. Please try again later.

          You are already subscribed to this email list. :)

          Submission failed. Please try again later.

          Reolink Store|Support|About Us|Privacy Policy|Terms and Conditions

          Copyright 2023 © Reolink All Rights Reserved.

          Welcome Back!

          Hi there! Join the Commnunity to get all the latest news, tips and more!

          Join Now