Hello,
Until the upgrade to the new Edge (Chromium) I was able to connect to my router setup at the 192.168.0.1.
Actually Edge was the only browser that would connect. I tied three others. Nothing has changed in my setup. The IP is still the same and the User and Password is the same. I actually had the working connection web page pinned in Edge.
This is all I receive now. (screenshot) https://prnt.sc/tktjn9
This page isn't working now
192.168.0.1 sent an invalid response.
ERR_INVALID_HTTP_RESPONSE
I had to re-install a different browser which at one time also would not connect, but apparently they fixed that in their update. Now I am able to connect to the Netgear setup page via this other browser. This is like Russian roulette now trying to connect
to the router's/modem setup. Why would one have to use a different browser for accessing different things?
Edge one was the only one to connect and now is no good. What I gather from some groups is that Edge and Chrome sees 192.168.0.1 as a unsecure page or it just blocks it as not trusted. When I spoke to Netgear in the past and they suggested Edge since the others did not work anymore with their products setup. I recently called Netgear and they stated they already know that the recent Edge (Chromium) is now one that does not work with their router/modem setup page. So the way this looks is that soon you will not be able to connect to your router via it's IP in a browser to set anything up and you will have to use a Ethernet cable each time you want to make a change in the settings.
What ever was merged over from Chromium is now blocking or not even seeing the IP/setup.
I have looked in the settings of Edge to Whitelist (set Trusted) for the Netgear IP 192.168.0.1 default access IP. I do not see anything to do so. Also a friend is having the same issue on his new Netgear router/modem (C7000 series). So fixing this would help both of us. I have been setting networks up for many years and have never run into a a browser not being able to access a routers setup via the IP access.
Can we please look into fixing this issue?
Thank you