New - RBR850 / RBS850 Firmware Version 4.6.14.3 Released

I don't have a solution, but I do feel your pain. I spent the same amount of time that you probably did meticulously testing and documenting, three times.

The first time the solution was access to the beta firmware program, the second time there was actually a solution involving TFTP magic and the third time it was seemingly bricked forever. Someone from Netgear reached out here to offer a solution, but after I replied with all the requested details (multiple times) all I have heard is silence.

I know this is severely off-topic, it is just so frustrating. I don't think I have had this many seemingly randomish issues with any technology since I had to deal with a printer that randomly fell off the network in 1997, or perhaps that TiBook that would kernel panic for no good reason every two weeks in 2002.

https://community.netgear.com/t5/Orbi-Wi-Fi-5-AC-and-Orbi-with/Massive-packet-loss-over-Ethernet-backhaul/m-p/1704702

https://community.netgear.com/t5/Orbi-Wi-Fi-5-AC-and-Orbi-with/RBR50-power-LED-blinking-green-now-appears-hung-or-dead/m-p/1968708

https://community.netgear.com/t5/Orbi-Wi-Fi-5-AC-and-Orbi-with/RBR50-bricked-again-during-update-to-2-7-3-22-power-LED-only/m-p/2126093

So what is the exact http URL your using when attempting to access the RBS web pages when this error appears? 

You mentioned  https://ap1.example.com < is this the exact url or just some sample for forum posting review? 

To confirm same URL is working in v.4.6.9.11?

---

kotfu wrote:

re RBS firmware updates: when I originally did the firmware upgrade, I did the RBS units one at a time, using their own web interface. After the first RBS has the new firmware and had restared and synced with the RBR, I went to the next RBS and repeated the procedure. After all RBS firmware was upgrade, I did the RBR firmware upgrade for the first time.

 

I followed the procedure you suggested:

- disconnect my RBR from my wired network and set it to router mode

- factory reset using the software tool in Admin/Backup

- configure RBR and RBS from scratch while all disconnected from my wired network

- I was successfully able to login to the web interface of the RBR using https://orbilogin.net

- reapplied the 4.6.14.3 firmware update to the RBR

- still can log in using https://orbilogin.net

- change configuration of RBR to access point mode using a different known unused static IP address (10.10.10.251)

- unplug power to RBR. While it sits for 1 minute, I connect RBR to my wired ethernet network using a cable

- plug power in to RBR and wait for it to boot

- verify I can ping the RBR new IP address 10.10.10.251

- update my internal DNS to point ap1.example.com to 10.10.10.251

- try to load https://ap1.example.com, get HTTP 500 Internal Server Error

- try to load https://10.10.10.251, which works fine.

 

Now I'm pissed off, and I'm determined to track down this problem. First I unplug power to all by RBS satellites and leave them unplugged to remove complexity in the target configuration. I disconnect the RBR from my wired network and do a factory reset. Reconfigure it from scratch using the procedure outlined above, same result.

 

Then I downgrade the firmware on the RBR to 4.6.9.11, do a factory reset, and set it to AP mode with a static IP 10.10.10.251. Everything works fine, no HTTP 500 Internal Server Error. So I do another factory reset, and configure AP mode with a dynamic IP instead of a static one. It works fine that way too. My hypothesis is now that it's a problem with the firmware 4.6.14.3. So I install 4.6.14.3 on the RBR, configure AP mode with a dynamic IP address, and the HTTP 500 Internal Server Error is back. After more experimentation and exploration with more sophisticated command line tools (nmap, dig, curl), here's what I know.

 

The error is observed:

- using firmware 4.6.14.3 on an RBR850, but not using firmware 4.6.9.11

- configured in AP mode (doesn't matter whether you use a static IP or dynamic IP)

- access web interface using a hostname, not an IP address (obvs in AP mode the hostname has to be provided by something besides the RBR because in AP mode the RBR DNS server is off)

- when accessing either http://ap1.example.com or https://ap1.example.com ie the error occurs independent of whether the web connection is encrypted with TLS

- before the authentication prompt, ie the HTTP 500 Internal Server Error occurs before the RBR prompts for the administration credentials

- regardless of browser used. I have replicated the error using using Safari, Chrome, Firefox, and curl.

- whether there are RBS satellites connected or not

 

The error is not observed:

- in the Orbi app for iOS. The app seems to work fine in all configurations and firmware levels.

 

There are two workarounds:

 

1. access the web admin tools using the IP address, ie https://10.10.10.251 (or whatever the IP address you've given to your RBR, either statically or dynamically when enabling AP mode)

2. downgrade the firmware to 4.6.9.11.

 

My guess is that firmware version 4.6.14.3 for the RBR introduced an error in the web server configuration.

 

Thanks for your suggestions FURRYe38 , but unless you can whisper in someone's ear and have them create a new version of the firmware, I don't think there is any way to fix this problem.

---

> So what is the exact http URL your using when attempting to access the RBS web pages when this error appears? 

> You mentioned  https://ap1.example.com < is this the exact url or just some sample for forum posting review? 

I run my own dns resolver, with an authoritative zone for my internal network. The URL I actually use is https://ap1.kotfu.net.

> To confirm same URL is working in v.4.6.9.11?

Correct. https://ap1.kotfu.net works fine on firmware v4.6.9.11 on the RBR.

MoooseAppreciate the solidarity. Reviewing your issues, I feel lucky. I have an easy work around for mine. Unexplained intermittent packet loss..../me knocks on wood.

Ok, I would open a support ticket regarding this if you can. 

Will pass this on to NG for review as well. 

Blanca_O KevinLiT 

---

kotfu wrote:

> So what is the exact http URL your using when attempting to access the RBS web pages when this error appears? 

> You mentioned  https://ap1.example.com < is this the exact url or just some sample for forum posting review? 

 

I run my own dns resolver, with an authoritative zone for my internal network. The URL I actually use is https://ap1.kotfu.net.

 

> To confirm same URL is working in v.4.6.9.11?

 

Correct. https://ap1.kotfu.net works fine on firmware v4.6.9.11 on the RBR.

---

Unfortunately the 90 day period of complimentary technical support for my devices expired many months ago. I have no interest in paying for a support contract in order to open a support ticket for this issue.

Will continue to monitor future firmware releases to see if this gets resolved.

Thanks again FURRYe38 for your assistance.

I guess keep what works for now. 

I have the exact same problem with firmware V4.6.14.3: RBR850`s web interface is working only in LAN (https://192.168.X.X or http://192.168.X.X)... the web interface cannot be accessed from WAN (ex: external ip https://202.X.X.X or DNS https://X.com). I had to downgrade the firmware to V4.6.9.11 in order to fix this issue.

Be aware that WAN access or REMOTE Management (WAN) was removed for security reasons by NG. Only Orbi app and Anywhere Access thru Orbi app is supported from the WAN side. 

https://kb.netgear.com/000062097/Remote-Management-is-now-Anywhere-Access-in-the-Nighthawk-and-Orbi-apps

---

George63 wrote:

I have the exact same problem with firmware V4.6.14.3: RBR850`s web interface is working only in LAN (https://192.168.X.X or http://192.168.X.X)... the web interface cannot be accessed from WAN (ex: external ip https://202.X.X.X or DNS https://X.com). I had to downgrade the firmware to V4.6.9.11 in order to fix this issue.

---

This is old news (Last Updated:08/10/2020 | Article ID: 000062097)  Remote Management is now Anywhere Access ..

In this article is not mentioned that the router`s web interface access from WAN was removed.

Clearly, the new firmware V4.6.14.3 has issues and the router`s web page can only be accessed from LAN.

---

George63 wrote:

 I had to downgrade the firmware to V4.6.9.11 in order to fix this issue.

---

Do I understand correctly that firmware v4.6.9.11 on the Orbi 850 allows customers to reach the web interface from the internet?

(i.e. using the public IP address or a Dynamic DNS name)

I have the original RBR50 Orbi and remain frustrated and disappointed that Netgear removed Remote Management from the router Advanced Settings, claiming that the Orbi app Anywhere Access was sufficient.  (Which it definitely is not.)  My understanding all this time has been that the "AX" Orbi systems have not had Remote Management included in any of the v4 firmware versions.

If you setup OpenVPN on your router, there is no difficulty to still access the console (and the full set of options not available through the app such as port forwarding) after connecting in VPN to your LAN.

Have you submitted the request for the invited beta FW opportunity? 

---

kotfu wrote:

Unfortunately the 90 day period of complimentary technical support for my devices expired many months ago. I have no interest in paying for a support contract in order to open a support ticket for this issue.

 

Will continue to monitor future firmware releases to see if this gets resolved.

 

 

---

Was this resolved in v7 FW if you updated to it or is this problem still present in v7 FW? 

---

kotfu wrote:

re RBS firmware updates: when I originally did the firmware upgrade, I did the RBS units one at a time, using their own web interface. After the first RBS has the new firmware and had restared and synced with the RBR, I went to the next RBS and repeated the procedure. After all RBS firmware was upgrade, I did the RBR firmware upgrade for the first time.

 

I followed the procedure you suggested:

- disconnect my RBR from my wired network and set it to router mode

- factory reset using the software tool in Admin/Backup

- configure RBR and RBS from scratch while all disconnected from my wired network

- I was successfully able to login to the web interface of the RBR using https://orbilogin.net

- reapplied the 4.6.14.3 firmware update to the RBR

- still can log in using https://orbilogin.net

- change configuration of RBR to access point mode using a different known unused static IP address (10.10.10.251)

- unplug power to RBR. While it sits for 1 minute, I connect RBR to my wired ethernet network using a cable

- plug power in to RBR and wait for it to boot

- verify I can ping the RBR new IP address 10.10.10.251

- update my internal DNS to point ap1.example.com to 10.10.10.251

- try to load https://ap1.example.com, get HTTP 500 Internal Server Error

- try to load https://10.10.10.251, which works fine.

 

Now I'm pissed off, and I'm determined to track down this problem. First I unplug power to all by RBS satellites and leave them unplugged to remove complexity in the target configuration. I disconnect the RBR from my wired network and do a factory reset. Reconfigure it from scratch using the procedure outlined above, same result.

 

Then I downgrade the firmware on the RBR to 4.6.9.11, do a factory reset, and set it to AP mode with a static IP 10.10.10.251. Everything works fine, no HTTP 500 Internal Server Error. So I do another factory reset, and configure AP mode with a dynamic IP instead of a static one. It works fine that way too. My hypothesis is now that it's a problem with the firmware 4.6.14.3. So I install 4.6.14.3 on the RBR, configure AP mode with a dynamic IP address, and the HTTP 500 Internal Server Error is back. After more experimentation and exploration with more sophisticated command line tools (nmap, dig, curl), here's what I know.

 

The error is observed:

- using firmware 4.6.14.3 on an RBR850, but not using firmware 4.6.9.11

- configured in AP mode (doesn't matter whether you use a static IP or dynamic IP)

- access web interface using a hostname, not an IP address (obvs in AP mode the hostname has to be provided by something besides the RBR because in AP mode the RBR DNS server is off)

- when accessing either http://ap1.example.com or https://ap1.example.com ie the error occurs independent of whether the web connection is encrypted with TLS

- before the authentication prompt, ie the HTTP 500 Internal Server Error occurs before the RBR prompts for the administration credentials

- regardless of browser used. I have replicated the error using using Safari, Chrome, Firefox, and curl.

- whether there are RBS satellites connected or not

 

The error is not observed:

- in the Orbi app for iOS. The app seems to work fine in all configurations and firmware levels.

 

There are two workarounds:

 

1. access the web admin tools using the IP address, ie https://10.10.10.251 (or whatever the IP address you've given to your RBR, either statically or dynamically when enabling AP mode)

2. downgrade the firmware to 4.6.9.11.

 

My guess is that firmware version 4.6.14.3 for the RBR introduced an error in the web server configuration.

 

Thanks for your suggestions FURRYe38 , but unless you can whisper in someone's ear and have them create a new version of the firmware, I don't think there is any way to fix this problem.

---

I upgraded to V7.2.6.21_5.0.20 last evening, and I still have the HTTP error 500 Internal Server Error when accessing the web ui via the hostname. It continues to work fine when accessing via the IP address.

If your not using the WAN port, possible reason why your seeing that 500 Internal error. If your not using the WAN port, you should be. As seen here: https://kb.netgear.com/31218/How-do-I-configure-my-Orbi-router-to-act-as-an-access-point

Just checking to see if this may have been resolved. Updating the bug with updated information if possible.