Clearing (only) GUI IP access restrictions from CLI

[spaceharrier]

I recently enabled WAN GUI access with a handful of specified IPs. Not exactly sure what went on behind the scenes, but now can't access the GUI at all from LAN or WAN.

I'm wondering if this might be some confusion about port assignment. The GUI was set to serve on port 80 but I have a forwarding rule to forward port 80 on the WAN side to an internal web server. (Note that there is no such rule on the LAN side, and the GUI had been working fine there until I made this change, and now works from nowhere.)

Accessing via the LAN throws up what's reported on the client as a network error -- not clear if that's an error from the HTTP server or some lower layer.

Logging in over SSH I can see httpd running, something listening on port 80 (via netstat) and IP Tables rules to allow access to port 80 on the LAN. Restarting httpd makes no difference.

Are there some handy nvram parameters I can reset to try to back out this change via the CLI?

 

[TBag]

You may try this, no guarantee though that it would work.

 

[RMerlin]

You could try temporarily running httpd on a different port.

1) Kill the running instance:

killall httpd

2) Enter the web content directory:

cd /www

3) Run httpd on a specific port:

httpd -p 8888

The webui should be accessible on port 8888 then (until you apply any change that will cause it to restart)