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.
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_INCOMPATIBLE
Netgear 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.
I may be mistaken, but my memory is that the choice is:
- Allow either http OR https web access, vs.
- Allow ONLY https web access.
CrimpOn wrote:
I may be mistaken, but my memory is that the choice is:
- Allow either http OR https web access, vs.
- Allow ONLY https web access.
That's certainly what I see.
Do that and you may break things. It seems to be intended for remote access into a router. Turning that on for local access has reduced people to gibbering wrecks until they turn up here and someone puts them out of their misery and they turn off that switch.
If you are connecting locally, then insisting on https is essentially paranoia. This is a local connection to our equipment. If you can trust friends and family – and have a decent password for the router – there isn't much chance that the Kremlin will break into your network. There are too many hurdles in the way.
Router users have happily managed with an http connection for years. The demand for https seems to have come from people who don't understand how network security works.
Then there is the increasing paranoia in browser builders. They try to protect people and do things like blocking http, requiring users to jump through various hoops to reach their own equipment.
Just another user with time on their hands.
And, to make matters even less clear, this enable/disable option appears on a web page titled
YEARS ago, Orbi routers had an option to allow access to the web interface from the internet (through the WAN port).This was restricted to https and this second option was to force local access to be restricted to https as well.
When the Orbi 'app' came out, Netgear removed the ability to access the web interface from the internet, but left this option. Personally, I loved the ability to enable/disable access from the internet.
