NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
unable to access router admin page due to https
Trying to hit routerlogin.net keeps switching over to "https" when it wants "http". This is true in all browsers I've tried (except Midori). And thus it prevents me from login in to the admin interface.
Interestingly, I installed the Midori browser and that let me get there. Looking at the admin settings, under "Advanced Setup" => "Web Services Management" the box "Always use https to access router" is checked.
How can I get my normal Chrome browser to hit the admin page?
Thx.
The workaround is to simply turn off https at the router. Login on a browser that allows it (I used Midori), go to Advanced -> Advanced Setup -> Web Services Management, uncheck "Always use HTTPS to access Router" and click "Apply". This is of course less secure, and Netgear really should "keep up", but...
9 Replies
Replies have been turned off for this discussion
- It's because most web browsers now try to force HTTPS/secure connections. You may be able to disable this in the browser settings or look up online how to do so using the more advanced settings
I've tried asking the AI how to disable the forcing of https in the browser, and everything it suggested fails (including explicit ip, incognito mode, ...). Was just wondering if somebody knew how to do this *correctly* in Chrome.
have you tried using its IP address?
Ok, turns out the problem is not http vs https, the router is listening on 443 fine (confirmed with telnet).
It's a cert issue. This is the error I get:
ERR_SSL_KEY_USAGE_INCOMPATIBLE
This happens on both Edge and Chrome, but Midori is fine, although it does say "warning". I did update the firmware, same error.
And it doesn't matter whether I use the IP or routerlogin.net. And note that this was NOT a problem 1 year ago (last time I accessed the admin interface).
I emailed support, we'll see.
Most likely this will be a browser issue. Since the onboard Certs are not updated by NG, they may come incompatible since browsers are updated more often then what NG updates on router. These can be ignored for the router log in. NG most likely won't fix it on there side.
