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 trying to display attached devices. Other menus options display OK but sometimes after a lot of wheel spinning.
I have been using Safari on MacOS and have cleared the history. Chrome has never connected for me due to the invalid Netgear certificate! I just tried Firefox and this also gives the 400 error.
I've tried a few router reboots and also restored a backup config.
Today I tried a full factory reset and restored the last backup config. The Orbi is working fine in terms of attached device access but the 400 error still remains when trying to browse and manage the admin interface.
I wonder if all the browsers are no longer liking the Orbi router web server or if something has changed in MacOS to trigger this?
Meanwhile the Orbi app shows the attached devices and their correct details.
Seems like the web admin UI via 192.168.1.1 is now becoming unusable - or will be if the menu options to restore a config file start to give a 400 error!
Anyone else experiencing this and got any bright ideas?
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.
8 Replies
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.
Jeffgear wrote:
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 trying to display attached devices. Other menus options display OK but sometimes after a lot of wheel spinning.
I have been using Safari on MacOS and have cleared the history. Chrome has never connected for me due to the invalid Netgear certificate! I just tried Firefox and this also gives the 400 error.
I've tried a few router reboots and also restored a backup config.
Today I tried a full factory reset and restored the last backup config.
Try a full factory reset and setup from scratch, WITHOUT loading the backup config. You maybe clearing the problem then reintroducing it when your applying the backup configuration file.
The Orbi is working fine in terms of attached device access but the 400 error still remains when trying to browse and manage the admin interface.
I wonder if all the browsers are no longer liking the Orbi router web server or if something has changed in MacOS to trigger this?
Meanwhile the Orbi app shows the attached devices and their correct details.
Seems like the web admin UI via 192.168.1.1 is now becoming unusable - or will be if the menu options to restore a config file start to give a 400 error!
Anyone else experiencing this and got any bright ideas?
What actual Fw version is loaded on the system?
Thanks
I won't be able try the factory reset without restoring the backup file for some time as I need the wifi running at home.
However, to answer the question about firmware that I'm running:
RBR50: V2.7.5.4
RBS50 and RBS50v2: V2.7.5.4
RBS50Y: V2.7.4.12
All the above are the latest versions and have been on these for 2+ years. I have tried with just the RBR online and satellites powered off.
I tried unticking the HTTPS option in the Local Web Mgt settings to revert to HTTP only and both Safari and Chrome connect fine. However, they both still do not display the home page with the device status etc and fail to display some menu options.
So looks like two separate issues:
(1) HTTPS mgt not working in Chrome
(2) Key web mgt menu options/displays not working in any browser (Chrome, Safari and Firefox), with the result being to 400 error or just the spinning wheel.
Reverting back to HTTPS, Chrome fails with no option to bypass and proceed to browse anyway (as you get with Safari). This was the case in the past with Chrome but not anymore. I just get this with Chrome:
The web page at https://192.168.1.1/ might be temporarily down or it may have moved permanently to a new web address.
ERR_SSL_KEY_USAGE_INCOMPATIBLENetgear need to resolve their certificate issues or give the option to download a self-signed into your local system/browser.The Safari browser on the iPad gives the same result with some display menu pages blank or 400 error.It does look like the lack of menu display is the router itself screwing up its mgt server/interface and maybe the factory reset without the restore will fix but this would mean a torturous setup from scratch. I may try restoring an older backup I have and see what that does in case the issue is my last backup being corrupted.🙂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.
