krbvroc1
New Around Here
Settings have been updated... Locked out... [SOLVED]
I recently updated to the lastest 374.33 merlin firmware and am constantly getting this stupid message that locks me out of the router. Something is not behaving correctly.
My router is configured with HTTP OFF, HTTPS ON, using a custom port.
This is because there are temporary occasions that I pass through port 80 to an internal server and that interferes with the router port 80 for http. I access the router using https://192.168.x.1:8888
1) This message happens when doing something that restarts the router, such as changing a firewall rule and hitting Apply.
2) I am unable to determine what 'clears this'. Is there some cookie set/missing? Something specific in the cache? I tried looking with firebug and didn't see anything. I would like to know a specific solution, not something drastic like clear the entire firefox cache.
3) Opening a 'New Private Window' under firefox lets me in.
Code:
Settings have been updated. Web page will now refresh.
Changes have been made to the IP address or port number. You will now be disconnected from RT-N66U.
To access the settings of RT-N66U, reconnect to the wireless network and use the updated IP address and port number.
I recently updated to the lastest 374.33 merlin firmware and am constantly getting this stupid message that locks me out of the router. Something is not behaving correctly.
My router is configured with HTTP OFF, HTTPS ON, using a custom port.
This is because there are temporary occasions that I pass through port 80 to an internal server and that interferes with the router port 80 for http. I access the router using https://192.168.x.1:8888
1) This message happens when doing something that restarts the router, such as changing a firewall rule and hitting Apply.
2) I am unable to determine what 'clears this'. Is there some cookie set/missing? Something specific in the cache? I tried looking with firebug and didn't see anything. I would like to know a specific solution, not something drastic like clear the entire firefox cache.
3) Opening a 'New Private Window' under firefox lets me in.
Last edited: