RBR750 Internal server error

What is the brand and model# of the host router? 

How is the RBR connected to the host router? Yellow WAN port on the RBR is required for AP Mode. 

RBS is wireless or ethernet connected to the RBR? 

How is the RBR configured for AP mode? Dynamic or Static configuration? 

Did the front LED on the RBR turn on PINK or blink WHITE? 

Power cycle the host router as well?

What FW version was last seen on the RBR and RBS?

What is the brand and model# of the host router? 

The RBR750 is in AP mode - so not acting as a router. The router itself is a pi5 running openWRT - but that setup hasn't changed for years 

How is the RBR connected to the host router? Yellow WAN port on the RBR is required for AP Mode. 

Yep, think that is the case (hasn't changed for ages) 

RBS is wireless or ethernet connected to the RBR? 

Wireless - from trial and error, when the RBS is on a wired connection, everything stopped working 

How is the RBR configured for AP mode? Dynamic or Static configuration? 

I can't recall - but neither can I get to it as the page returns an error code 500. Some functionality still works - devices can still connect to it, but not the satellite device 

Did the front LED on the RBR turn on PINK or blink WHITE? 

Can't tell - it failed whilst I was (am) away. 

A power cycle hasn't helped (I tried that remotely) 

I may replace them with 2 "dumb" openWRT wired access points. Less fancy to be sure, but also less to go wrong! 

Ah I should clarify - when I say remote - I am actually technically local - I am port forwarding in over SSH 

Both the RBS and the RBR get IPs over DHCP 

But the RBR gives a 500 if I try to load the main web page 

The RBS asks for a login, but then loads an empty page when the correct credentials are entered 

I guess one take-away from this is to turn off auto firmware updates (I don't know that was the problem, but seems likely as nothing else has changed recently....) 

Actually the RBS is up 

But not functional  and can't, apparently, see the RBR 

Could you try the debug page, i.e. <IP of the router> slash debug.htm

Is there another web browser on the Pi?

Can you "clear cache" on the browser?

How do you do a power cycle remotely?

No luck with debug mode. Some pages though do still respond: 

ben@pi5:~ $ curl -s http://192.168.1.15/ajax/qos_link_check.php --data-raw check_bw=check
speedtest stcurl -s http://192.168.1.15/ajax/qos_result_check.cgi --data-raw check_bw=check -X POST -H 'Content-Length: 0'tent-Length: 0'
speedtest is running

Some time later....

ben@pi5:~ $ curl -s http://192.168.1.15/ajax/qos_result_check.cgi --data-raw check_bw=check -X POST -H 'Content-Length: 0'
99.99 Mbps;964.73 Mbps;2025-07-19 22:33:49ben@pi5:~ $

So the unit is there and functional - to some extent. 

I power cycle remotely using a PoE managed switch - since both the RBS and RBR run from 12v PoE splitters (and have done for years) 

I've tried various browsers, incognito modes, and chache clearances unfortunately 

As a last ditch attempt (turns out to be a bad idea) I updated the RBS firmware to the latest using the file from netgear support pages. 

Now the RBS gives me a 404 

Feels like this is a problem that may be best solved by using different hardware :-) 

dbrb2 wrote:

Was there some new f/w pushed out by any chance?

The current firmware is v7.2.7.15  It was created Feb 28, 2025.  The satellite clearly has v7.2.6.31.

p.s. (totally off subject....)  Do you have a link to those ajax examples (and perhaps 'more') ?

Yep - you're right about the firmware. So the RBS problem was not caused by an auto firmware update. RBR maybe was - but I can't check that :-) 

However, in my attempts to fix this evening I downloaded RBS 7.2.7.15 and uploaded that to the RBS - and that made things worse (404 error on the RBS now) 

Those are the only ajax examples / URLs I have I'm afraid - though I have used them for ages to periodically check my speeds 

RBS came up on its own overnight. 

RBR seems now to be working - albeit without a web interface 

Seems like maybe the Orbi firmware is just a bit fragile! For now it is working though (I realise this same thing happened last December, then....became OK again for unknown reasons!)