NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

additude's avatar
additude
Virtuoso
Mar 28, 2020

Revoked security certificate with remote login

I have a RAX120 for over a year now that has a remote login issue which I have been troubleshooting "as time permits". I have set the RAX120 up for remote login to a static IP; https//:x.x.x.x:8080. In the past I have used other Netgear routers , Linksys routers, etc. for this connection without issue. Locally on the LAN I can log into the RAX120 from either from my laptop by accessing routerlogin.net or via the local IP for the router and as well from my iPhones "NightHawk" app.
But when I try to log in remotely over the web with either Edge or Chrome I receive:
Edge Error Code: ERROR_INTERNET_SEC_CERT_REVOKED
Chrome shows that "This Certificate is OK" under Certificate Status
When I check the certificate info I see that the certificate is pointed to www.routerlogin.net and is valid until Thursday, July 29, 2021 8:53:50 PM.
I have updated the router firmware, I am using Win10 which is recently completely updated. At one point in the past, when I first installed the RAX120 I swear the remote login from web IP worked just fine.
I have looked around and I have done some research but I have found nothing conclusive, however I realize that this has some connection issue to routerlogin.net
I need suggestions or an answer to resolve my remote login problem.
Thanks.

 

8 Replies

Sort By
  • additude's avatar
    additude
    Virtuoso
    Mar 28, 2020

    I used a Win 7 laptop to try and log in remotely to the router and that version of Explorer gave me security certificate warnings, but still provided me a link to "Proceed Anyways", which I used and I was able to successfully log in.

    I believe that this tells me that the issue is with the NETGEAR security certificate and not with the browser settings...

    • additude's avatar
      additude
      Virtuoso
      Mar 28, 2020

      I have completely read the user manual in regards to remote management from a computer and as well concerning the Nighthawk app with regards to accessing the router with a mobile phone.

      1. In my case, I can access the router remotely with the Nighthawk app.

      2. I can access the router remotely using google or edge on my phone and entering the https://x.x.x.x:8080 IP address

      3. I can access the remote router on a Win 7 PC, althought it throws a certificate error and I am allowed to "Proceed" with both Edge and Chrome

      4. I cannot access the remote router on a Win 10 PC with either Chrome or Edge because the ssl certificate error is "Certificate is Revoked" and there is no option to proceed.

      • additude's avatar
        additude
        Virtuoso
        Mar 29, 2020

        I am beginning to feel as though I am the only person with this problem or that I am totally overlooking something completely obvious.

        But then, maybe I am the only one wanting to talk about it. :)

        So, after more investigating, what I did recently was to lower all the security levels to their lowest level for "Internet Options", included both routerlogin.net and my routers remote IP address into "trusted sites" and then I created a desktop shortcut for MSIE, included my routers IP address-port as part of the target and then executed the shortcut as "Run As Administrator".

        That did not change anything. It still throws the certificate error.

        So then I created a Chrome desktop shortcut which included "--ignore-certificate-errors" plus my routers IP address-port and that actually allowed me to get the credentials sign-in box without any issue. So, there is a "Work-Around" per se in Chrome. But it's not a fix, it's still a bandaid.

        However in MSIE, there seems to be the typical MS "hamstringing" issue of protecting me from myself even if I am versed enough to make several technical changes.... therefore, it's not possible to get MSIE to disregard certificate errors for an individual WAN IP address. I did see that there is a way to make registry changes to disregard all certificate errors for all addresses, but I did not explore that option.

        Now, I may be out in Left Field somewhere, but it appears at this juncture that "WIN10, MSIE, Chrome", depending on what WIN10 service level upgrade is being executed, interprets routerlogin.net as a potential intermediary interception threat because WIN10 is looking for one thing and getting two. One from my Netgear router and one from routerlogin.net which is where the view certificate link points to. I think the way WIN10 deals with that is WIN10 "Revokes" the certificate locally, that causing the "Revoke" error with the view certificate reporting that the certificate is "OK".

        I am going to try a few more things.

        I'll be back.....