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 RBR50
I am using an RBR50 and an RBS50 (connected with wired backhaul) firmware is V2.7.2.104 on both devices. My ISP is Spectrum, I pay for a 200/20 connection that is consistently connected at 234/23. Mo...
i waited a few days for some response but none came, i did a hard reset and things work now.
Sometimes a reset is needed. It's a valid troubleshooting step of all other troubleshotting steps have been exhausted.
https://www.snbforums.com/threads/faq-nvram-and-factory-default-reset.22822/
Also users need to remember and keep on hand backup configuration files. Saves loads of time if a reset is needed.
https://kb.netgear.com/000062080/How-do-I-back-up-the-configuration-settings-on-my-Orbi-WiFi-System
And please don't use foul language. Tends to get one banned. We all understand everyones frustrations when it comes to there networking problems.
Lexx wrote:It's not really solved, however. Requiring a factory reset to fix an inability to update setting or firmware because of a sloppy Netgear implementation is not a solution. Netgear, step up.
I have this issue as well. Occurs with every browser on multiple devices including mobile browsers that never accessed the RBR50 web interface before. So it's not a cache, cookie, or stuck session problem as many other threads tried to theorize. Occur on multiple RBR50 firmware versions, at least 2.6.1.40 and up. It's clear from the forum this issue has existed for at least 2 years worth of firmware versions.
I am not going back to factory settings, it's way too much work in my setup. If I have to do that, I am dumping Orbi and starting over with either ZenWifi or Ubiquity -- that will be the same amount of work and don't have to deal with Netgear neglect afterwards. Again, Netgear, step the f&*$ up.
P.S. The reason I need to touch the setup at all is becuase 2.7.2.104 broke RBR50 basic device "home" and "attached devices" view. The page just spins forever (tested over hours) and the app, while "works", is highly inaccurate relative to reality. The "spin forever" may well be a related issue to this 400 Bad Request. Netgear, STEP THE F&*$ UP.
(Hint at) foul language is perhaps the only way to get noticed. And it's not like getting banned is going to have any further detrimental effect on my system's stability or ability to get anything solved on this forum or with Netgear in general. Usual fanboi comments notwithstanding, this isn't a "networking problem", this (and almost every other issue ever reported and unsolved on this forum) is a Netgear software competence and quality problem.
FYI, NG development doesn't monitor these forums. And with all the posts thats generated, would be hard to keep tabs no everything. Users have the option to contact support directly which is encouraged aswell as contact NG forum moderators too. Let them know directly vs indirectly. Forums can only do so much.
Good Luck.
Yes, I know they don't monitor. Their solution to everything is same as yours, restore factory settings. I did swear off Netgear once before but there isn't much choice in multi-satellite high-bandwidth wireless backhaul meshes. Initially, Orbi worked ok and so I stuck with it -- clearly should have instead stuck to my prior Netgear ban. I don't need luck, I and the world needs competent software for a change.
:smileywink: