RT-AC3100 won't restart with Asuswrt-Merlin 382.1

[ryandesign]

Hi, I'm new here so I hope I'm correct to post this here. I'm also new to ASUS routers. I've previously been using DD-WRT on other routers. Thanks to RMerlin for maintaining the Asuswrt-Merlin fork!

I recently bought a used RT-AC3100 which had Asuswrt-Merlin 380.x on it. I reset the NVRAM and upgraded it to 382.1. Within a couple hours of turning it on, and having not done much configuration yet, I began having problems, specifically the router would not restart when told to do so, for example:

• Pressing the "Reboot" button in the web interface caused the "Applying settings" overlay to appear, but after it went away, the router had not rebooted. The router's lights never did the reboot dance, and the uptime showed that a reboot didn't happen.
• The "Restore" factory default button in the web interface didn't work either. Again, "Applying settings" appeared, but nothing was reset.
• Pressing the router's hardware reset button for a few seconds caused the power light to start blinking. Releasing the button caused the power light to go out. The router did not restart, and, other than the power light being off now, continued working as if I hadn't pressed the reset button.

If I physically powered off the router and powered it back on, the above behaviors were immediately repeatable again.

I managed to use the CFE miniWeb Server interface to reset the NVRAM and re-upload the 382.1 firmware, which didn't fix the problem. I can't remember if the problems were gone immediately afterward, but do remember that within a couple hours the problems were back.

I've now downgraded to 380.68_4 and reset NVRAM again, and it's working great without these problems.

I didn't see anything in the 382.1_1 changelog that would indicate this problem has already been fixed. If this is not already a known problem, is there any other information I can provide to help debug it?

There are a lot of other threads and posts around here... If I've missed someone else talking about this problem elsewhere, my apologies; please let me know.

Thanks.

 

[Razor237]

I have a 3100 running 382.1 just fine , i was also running the beta versions good as well. Did you try to flush your browsers cache, i did that when i upgraded initially cause it was stated there were lots of changes to the web ui so its possible that could be your issue. I would try to upgrade again and refresh your cache after the upgrade and see if that help, i would also give another browser a try

 

[aploch]

I realize this is an old post but I'm having the same problem with asuswrt-merlin 384.13 on my RT-AC3100. I haven't tried the Restore factory button yet, but I have attempted to reboot from the Web UI with no luck and I've also refreshed my browsers cache (as Razor suggested) with no luck. SSH'ing into the router and calling reboot DID work, however - but even after it rebooted, the web ui's reboot function still doesn't work.

 

[aploch]

Immediately after my previous post I decided to check the dev tools console and this is what I get when I click reboot. Interesting that it thinks it's a cross-domain call when it's pointing to the same base URL:

state.js:1679 Uncaught DOMException: Blocked a frame with origin "http://192.168.1.1" from accessing a cross-origin frame.
    at reboot (http://192.168.1.1/state.js:1679:33)
    at <anonymous>:1:1
reboot @ state.js:1679
(anonymous) @ VM6494:1

 

[dave14305]

Immediately after my previous post I decided to check the dev tools console and this is what I get when I click reboot. Interesting that it thinks it's a cross-domain call when it's pointing to the same base URL:

state.js:1679 Uncaught DOMException: Blocked a frame with origin "http://192.168.1.1" from accessing a cross-origin frame.
    at reboot (http://192.168.1.1/state.js:1679:33)
    at <anonymous>:1:1
reboot @ state.js:1679
(anonymous) @ VM6494:1

Do you have an adblocker that you should disable for the router’s URL?

 

[aploch]

Ugh you're right. Thank you. I actually did consider that and I was looking for the little number in my toolbar that indicates "how many" ads it blocked, and it didn't show anything. But as soon as I explicitly whitelisted *://192.168.1.1/* it worked fine. Duh. Thanks

Using AdBlock on Chrome (latest-ish build)