NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Firefox cannot access routerlogin.net but Chrome and Edge can - what's wrong?
Hello I cannot access www.routerlogin.net using Firefox, but on the same machine Chrome and Microsoft Edge can access it. On Firefox, www.routerlogin.net redirects to this page: https://w...
> Which says I am not connected to my wifi [...]
Possibly relevant:
Additional steps taken:
Deleted all Firefox cookies and site data again then rebooted the computer
Updated router firmware to 1.2.0.76_1.0.1
Chrome now works
Firefox still redirects to the page listed above
> Which says I am not connected to my wifi [...]
Possibly relevant:
Antinode,
Thank you! I read the link you provided. While I did not think that I had turned off my wifi like the poster said (I am able to access the router using Edge and Chrome), I did notice the alternate router address of 10.0.0.1 and this does work in Firefox, so problem solved.
Thanks again
Maurice Frank
Antinode:
One more thing the article mentioned is DNS over HTTPS so I found that setting in Firefox. It was checked so I unchecked it.
Firefox then connected using www.routerlogin.net, although there was an HTTPS not available warning. But I did get through.
I decided to leave DNA over HTTPS checked / enabled because that is how it was before and nothing else was broken, and I can use the 10.0.0.1 address in Firefox
Thanks again
Maurice
> [...] the alternate router address of 10.0.0.1 [...]
You can get that if the router (WAN/Internet port) is connected to
another router. Doing that can cause problems, by the way.> [...] DNS over HTTPS [...]
Yup. When they work, those "routerlogin" names have some benefits,
such as not needing to know if your router's at "192.168.0.1", or
"192.168.1.1", or "10.0.0.1", or whatever. But when they fail for some
reason, and those reasons are getting more common, they can cause much
confusion.