Microsoft Edge and now Chrome browsers cannot connect to router via http://

[cnsdave]

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. Please fix your products to use a current cert. I am running the latest firmware. This has been going on for almost 5 years now. Shame on NetGear.

[cnsdave · Accepted solution]

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.

[FURRYe38]

Be sure to clear your browser caches. 

Try https:// next time

FW works wth current browsers. 

---

@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 had to download Firefox browser to get this to work today. Please fix your products to use a current cert. I am running the latest firmware. This has been going on for almost 5 years now. Shame on NetGear.

---

[CrimpOn]

---

@cnsdave wrote:

Microsoft Edge and now Chrome browsers cannot connect to router via http://. I had to download Firefox browser to get this to work today. Please fix your products to use a current cert. I am running the latest firmware. This has been going on for almost 5 years now. Shame on NetGear.

---

I use Microsoft Edge, Chrome, Firefox, and Opera to access the Orbi web interface on an RBR50 with no problem.

Because of the modern paranoia (as described in many previous posts), the browser may complain, but there is always an option on the page somewhere called "Advanced" or "Details" (or something similar) that offer an option to go there anywhere and stop complaining.

• With http, the complaint is "unsecure"
• With https, the complain is "self-signed SSL certificate"

When the user is on the local network, neither of these complaints represents a real problem.

Netgear cannot possibly get a registered SSL certificate for "orbilogin.net" because "WHO IS THIS???"  Answer: Oh, thousands of individuals and companies have products that use this certificate. We don't want a certificate for someone specific, (such as Netgear corporate)."  It is a MESS.

[michaelkenward]

---

@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.

[cnsdave · Accepted solution]

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]

---

@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.

[CrimpOn]

---

@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"?

[michaelkenward]

---

@CrimpOn wrote:

---

@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"?

---

I'll have to go back and experiment. But I tried it once, a few years back, and all hell broke lose with the GUI.

[schumaku]

@ScubaSteve007 wrong section for the Orbi Pro - beta fix for your Orbi Pro SXR80 router and SXS80 satellites is available -> here.

Have requested a moderator to move your reply away from the Orbi Wi-Fi 5 (AC) and Orbi with Voice Mesh section already.