NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
400 Bad Request on local admin browser
I'm now getting to 400 Bad request pop up in various browser admin pages when accessing my Orbi RBR50 that's been on the same latest firmware for over a year now. I get the 400 error always when ...
Update:
I restored an older backup from last year and this resolved the issue with the web UI not displaying some menus and the 400 bad request error. I can navigate around the web UI fine using Safari and HTTPS. This back up was not materially different in terms of config.
However, Chrome still refuses access using HTTPS and I prefer not to set the Netgear to HTTP only, so I will stick with Safari.
This also shows that its worth taking backups every few months as the most recent one I had was corrupt in some odd way to cause just the web UI to misbehave but only with some menu options/selections. Fickle stuff this Orbi and app.
It might be worth giving Chrome another try. Netgear is in an awkward spot regarding the most modern web browsers:
- When a user attempts to connect using http (unencrypted), browsers complain insecure because by definition unencrypted transmission is thought to be unsafe.
- When a user attempts to connect using https (encrypted), browsers complain insecure because the SSL certificate used by the web server is self-signed. For many years, Netgear had registered a number of URLs with a certificate authority, including routerlogin.com, routerlogin.net, orbilogin.com, orbilogin.net. These authorities certified, "Yes. When you connect to one of these URLs, you are connecting to Netgear (a corporation based in San Jose, California). Several years ago, that certificate expired and Netgear did not renew it (was not allowed to renew it?). After all, this router does not belong to Netgear, it belongs to ME. It's in MY HOUSE. Not on Netgear property. Does YOUR router belong to Netgear?
So, Netgear is screwed either way.
Using the IP address rather than the URL to open the unencrypted (http) web site at least avoids the SSL certificate issue.
The solution is to find the option buried in small print toward the bottom of the page and tell the browser, "Shut Up. I know that this web site is MINE. It's on MY NETWORK. Go there and quit complaining!"
The Community Forum has dozens of posts about the 400 error. If using a different browser doesn't make it stop, you might browse through those posts and see what solutions people found.