Firefox cannot access routerlogin.net but Chrome and Edge can - what's wrong?

[MauriceFrank]

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://www.netgear.com/home/services/routerlogincom.html

Which says I am not connected to my wifi but I can browse the internet and I can also access my HP printer using wifi.

I get this when connected to both the 2.4 and 5 Ghz netowrks on my router.

What am I doing wrong? Is there a Firefox setting I need to change?

My Environment:

R6900v2

Dell XPS 15 9500 (one week old)

Windows 10 64 bit - 10.0. 19042 Build 19042 (up to date)

Firefox 85.0 64 bit - up to date

I tried clearing the Firefox cache (but not cookies - I will lose many logins)

I tried 92.168.1.1 and it did not work either

Thanks for any advice

Maurice Frank

[antinode · Accepted solution]

> Which says I am not connected to my wifi [...]

   Possibly relevant:

      https://community.netgear.com/t5/x/x/m-p/1976674

[MauriceFrank]

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

[antinode · Accepted solution]

> Which says I am not connected to my wifi [...]

   Possibly relevant:

      https://community.netgear.com/t5/x/x/m-p/1976674

[MauriceFrank]

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

[MauriceFrank]

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

[antinode]

> [...] 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.