LAN Bookmark fails in Firefox only

[GwentLarry]

Netgear D6220 Firmware V1.0.0.52_1.0.52, iMac OS 10.16.6, Firefox Quantum 69.0.1 (64-bit), Safari 13.0.1

I usually access the admin web page for my D6220 Netgear modem/router from Firefox via the address https://www.routerlogin.net/start.htm This has just now stopped working - Firefox reporting "Unable to connect".

The modem is functioning - I can access the internet and email without difficulty.

Bizarrely, if I use the LAN IP address for the modem/router (10.175.0.1), Firefox connects to the admin web page straight away.

Even more strangely, if I use Safari, I can connect to the admin web page for my D6220 Netgear modem/router using both https://www.routerlogin.net/start.htm and the LAN IP address (10.175.0.1)

I have rebooted and done a factory reset of the modem.

I have restarted Firefox in Safe mode with add-ons disabled, restarted my iMac, deleted the Firefox cache, restarted the modem. No change.

This is a very recent issue, happening in the last 2-3 weeks.

I can't even decide if it's a Firefox problem or a D6220 Netgear modem/router - I've already tried the Firefox forums and nobody has a solution ....

Suggestions please 🙂

[DexterJB]

Hi @GwentLarry, does the issue persist when using another computer or device (mobile)?

Dexter

[antinode]

> [...] https://www.routerlogin.net/start.htm This has just now stopped
> working - Firefox reporting "Unable to connect".

   "https://"?  I'd expect that to fail.  I'd give "http://" a better
chance of working.

> [...] and the LAN IP address (10.175.0.1)

   If you specified neither scheme, "http://" or "https://", explicitly,
then a helpful web browser might first have tried "https://", but
reverted to "http://" if the "s" one failed.

> Suggestions please 🙂

   When dealing with a web site (like the management web site of a
Netgear router) which listens at port 80 (HTTP) and not at 443 (HTTPS)),
be very careful about the URL(s) which you use?

[GwentLarry]

No, there are no problems connecting from either a phone or tablet.

However, I use Safari on both of these and connecting from Safari on my desktop isn't a problem either. The connection problem only ocurs on my desktop with Firefox. Which, I appreciate, strongly suggests it's a Firefox issue rather than a Netgear modem issue but I've already spent quite a bit of time on the Firefox forums without resolving the problem.

My guess is that it's somethng to do with recent security improvements in Firefox but I've been unable to locate precisely what the issue might be. I came to the Netgear forums in case anyone was aware of some incompatibility between recent Firefox upgrades and the Netgear modem.

Thanks,

[GwentLarry]

Except that I don't have any issues with https://www.routerlogin.net/start.htm when using Safari ...

And http://www.routerlogin.net/start.htm:80 fails as well even when I restart Firefox in safe mode with all extensions/addons off.

I think the issue is more to do with Firefox than the modem but I've already spent quite a bit of time on the Firefox forums and not got a solution. I was just trying here in case anyone was aware of an issue between the latest Firefox versions and the Netgear browser interface.

Thanks,

[michaelkenward]

---

@GwentLarry wrote:

My guess is that it's somethng to do with recent security improvements in Firefox but I've been unable to locate precisely what the issue might be.

---

Almost certainly the case. Quite why you prefer https over http is down to you. It does nothing for your local security.

If I go the https route I get a security error. If I click through all the warnings of death and destruction I get where I want to be.

If I go the http route I get none of the warnings and go straight to where I want to be.

[GwentLarry]

Problem has vanished !!!!!

No idea why but the problem no longer happens.

I did try changing some of the Firefox site-specific security settings. None of which had any affect, so I changed them back to the initial settings.

I can only guess that something, somewhere in Firefox had got corrupted and that changing security settings and changing them back re-wrote the setting correctly.