Open the browser console and look for Javascript errors when you try to reboot.Yes... and i tried many times
Open the browser console and look for Javascript errors when you try to reboot.Yes... and i tried many times
Uncaught DOMException: Permission denied to access property "setTimeout" on cross-origin objectOpen the browser console and look for Javascript errors when you try to reboot.
For some reason your browser is refusing to allow the reboot command from being executed.Uncaught DOMException: Permission denied to access property "setTimeout" on cross-origin object
reboot https://10.0.0.1:7733/state.js:2222
<anonymous> javascript:reboot();:1
state.js:2222
ok... what i can do?For some reason your browser is refusing to allow the reboot command from being executed.
Thanks for pointing me in the right direction. The problem was with the addon "ServerIP" ( https://webextension.org/listing/country-flags.html?from=server-ip ). Everything works perfectly now.For some reason your browser is refusing to allow the reboot command from being executed.
The web server crashed, but it's impossible to tell from that what caused it to crash. What page were you on?Do you know what that means ? I've never experienced this kind of mistake before. If it could be solved, that would be great.
Thanks for your quick reply. Just when the web server went down, I was exactly here :The web server crashed, but it's impossible to tell from that what caused it to crash. What page were you on?
Did you maybe try to upload some unsupported image format/size?Thanks for your quick reply. Just when the web server went down, I was exactly here :
I wanted to change the name and image of my device.
Do you think this problem can be solved in a future version ?
I don't know. I would first need to be able to reproduce the problem, and so far I can't.Do you think this problem can be solved in a future version ?
Each time, I chose only the original images supplied in the firmware.Did you maybe try to upload some unsupported image format/size?
Works for me just fine...
Or try to do it from the LAN-DHCP Server page, if it acts the same.
Did you also maybe try to use some French accented letters??Each time, I chose only the original images supplied in the firmware.
And I've always changed the images in the "network map" tab on the home page, as my screenshot shows..
One thing's for sure, there's a problem. I've never had this problem with Merlin firmware. Which also explains why my customer list crashed the other day.
Double bug since installation of version 3004.388.6_2.
The logs speak for themselves.
I hope this problem will be corrected soon.
Did you also maybe try to use some French accented letters??
I once accidentally wrote a name in Cyrillic letters - he did not like that!![]()
Thanks in any case for researching this bug.I don't know. I would first need to be able to reproduce the problem, and so far I can't.
The syslog should tell you why dnsmasq fails to start. Save the log on your next upgrade attempt. In the meantime, check for any dnsmasq.conf.add or dnsmasq.postconf files that maybe in conflict with the newer version (e.g. dns-forward-max).Then I saw the posts that are saying that diversion is causing dnsmask to crash, so I disable diversion but the problem remains.
A lot of instability on this latest version...On my home GT-AX6000 the same thing happen with (3004.388.6_2 nand), some wireless clients (android phones on the guest network) couldn't obtain IP address, some other clients were connected (PC laptops on the main network) but with no internet access.
I have double flash , reboot, disabling and re enabling Wi-Fi and guest network and didn't solve the issue.
Then I saw the posts that are saying that diversion is causing dnsmask to crash, so I disable diversion but the problem remains.
I had no other choice so I rolled back to (3004.388.6_0 nand) and everything is working normal again.
The fanny thing is that on my office RT-AX88U that has the same settings and add-ons none of the above is happening, everything seams to work fine for two days now.
Any way I will wait for a fix / solution for the problem 3004.388.6_0 is working fine, my only concerns are the CVE 2023-50868 and CVE 2023-50387 that the update resolves.

Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!