What's new

RT-AX86U WebUI login timeouts

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Neurogenesis

Occasional Visitor
I've had this issue prop up since going to 388.2. I am currently on 388.2_2.

Long story short I put in the IP for the router into a browser, doesn't matter which one, and the login times out. I have tried multiple devices and issue persists. The only way to get in is to reboot the router. I haven't isolated if it happens <24 hours apart, but it occurs at least a day apart if I try logging in a day later.

Thoughts on how to isolate whats causing it?
 
I recently installed my RT-AX86U Pro and still on stock (current) firmware (waiting to see what the next Merlin firmware has for this model) and have experienced the same thing, slow or downright unresponsive web UI. Same network setup using my old RT-AC68U was super fast. Not sure what's causing it. Hoping a firmware update fixes it down the road.
 
I've had this issue prop up since going to 388.2. I am currently on 388.2_2.

Long story short I put in the IP for the router into a browser, doesn't matter which one, and the login times out. I have tried multiple devices and issue persists. The only way to get in is to reboot the router. I haven't isolated if it happens <24 hours apart, but it occurs at least a day apart if I try logging in a day later.

Thoughts on how to isolate whats causing it?

I've discovered that if I click on the "view list" on the main page (index.asp) it will sometimes throw the http daemon into some sort of hung state, which then triggers the watchdog to try to restart it, which fails, and ends up in a never-ending fail loop.

You can check this yourself by SSH'ing into the router and running the command cat /tmp/syslog.log.

The only way I've found other than a reboot is to kill the watchdog (command: kill [watchdog PID]) and then issue a service restart_httpd. The watchdog error message will actually give you the PID (e.g., Aug 5 22:05:09 rc_service: watchdog 360:notify_rc start_httpd), where the 360 (in this example, yours will vary) is the PID you want to kill.

If kill doesn't work, you could try one of the "sig____" commands too. IIRC on a couple of occasions I had to issue a couple of kills on the watchdog (to catch it when it was active). And you don't need to restart the watchdog, it has a "watchdog" of it's own that will check and restart it automatically.

(Might be easier just to reboot, eh.)
 
I've discovered that if I click on the "view list" on the main page (index.asp) it will sometimes throw the http daemon into some sort of hung state, which then triggers the watchdog to try to restart it, which fails, and ends up in a never-ending fail loop.

You can check this yourself by SSH'ing into the router and running the command cat /tmp/syslog.log.

The only way I've found other than a reboot is to kill the watchdog (command: kill [watchdog PID]) and then issue a service restart_httpd. The watchdog error message will actually give you the PID (e.g., Aug 5 22:05:09 rc_service: watchdog 360:notify_rc start_httpd), where the 360 (in this example, yours will vary) is the PID you want to kill.

If kill doesn't work, you could try one of the "sig____" commands too. IIRC on a couple of occasions I had to issue a couple of kills on the watchdog (to catch it when it was active). And you don't need to restart the watchdog, it has a "watchdog" of it's own that will check and restart it automatically.

(Might be easier just to reboot, eh.)
ill try doing this. havnt really done anything at all with SSHing into the router though. Know of any good tutorials though?
 
ill try doing this. havnt really done anything at all with SSHing into the router though. Know of any good tutorials though?
It's a little intimidating the first time, but once you get the hang of it you'll wonder how you ever operated without it. Particularly using amtm (Diversion, Skynet, etc).

There's information in the wiki: https://github.com/RMerl/asuswrt-merlin.ng/wiki/SSHD

And here's a thread that has some basic info and a few more links: https://www.snbforums.com/threads/i...n-rt-ac68u-running-merlin-384-19-fixed.66650/
 

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top