NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
cnsdave
Jan 28, 2024Initiate
Microsoft Edge and now Chrome browsers cannot connect to router via http://
RBR50 Orbi Router and satellites - version: 2.7.5.4
Microsoft Edge and now Chrome browsers cannot connect to router via http://. I had to download Firefox browser to get this to work today. Ple...
- Jan 29, 2024
I finally got this to work using Windows 11 and Edge by going to the Privacy option. I added an exception rule in the manage enhanced security for websites tab to include http://192.168.1.1. I also changed the Orbi configuration to not use https:// for web management login. This change fixed chrome to but I'm not sure why (cache maybe). Go figure.
michaelkenward
Jan 28, 2024Guru - Experienced User
cnsdave wrote:
RBR50 Orbi Router and satellites - version: 2.7.5.4
Microsoft Edge and now Chrome browsers cannot connect to router via http://.
I have used Chrome and Edge and they work just fine.
I have Edge in there right now. (I don't use Chrome much these days.)
But you may have to jump through a security warning.
- cnsdaveJan 29, 2024Initiate
I finally got this to work using Windows 11 and Edge by going to the Privacy option. I added an exception rule in the manage enhanced security for websites tab to include http://192.168.1.1. I also changed the Orbi configuration to not use https:// for web management login. This change fixed chrome to but I'm not sure why (cache maybe). Go figure.
- michaelkenwardJan 29, 2024Guru - Experienced User
cnsdave wrote:
I also changed the Orbi configuration to not use https:// for web management login. This change fixed chrome to but I'm not sure why (cache maybe). Go figure.
That one has lot a lot of people. Setting https breaks things.
- CrimpOnJan 29, 2024Guru - Experienced User
michaelkenward wrote:
That one has lot a lot of people. Setting https breaks things.
Hmmm. I am aware that modern web browsers complain about both types of web connection:
- HTTP because unencrypted connections are by definition "not secure", and
- HTTPS because the router's web SSL certificate is "self-signed" and thus not authenticated by one of the well-known certificate authorities. (See Wikipedia: https://en.wikipedia.org/wiki/Certificate_authority )
Browsers can be told to proceed to the Orbi web server in both situations.
What sort of things does https "break"?