Rut956, firmware RUT9M_R_00.07.12.3
Sadly at least 2 of my remote routers reachable via ZeroTier con only rejects login claiming “failed to login due to unexpected error”. Both are reachable and able to login via SSH CLI, but is impossible via web UI.
Factory reset is not an option! Go there means USD 1000 to connect a cable, reboot (via ssh) didn’t help
Suggestions?
@rodrigobarrera Hello,
Could you please access your device via CLI/SSH and run the following command:
logread -f
While this command is running, try logging into the WebUI using your browser. Do you see a successful login in the logs?
If the login is successful but the WebUI is still not working, try running this command and then attempt to access the WebUI again:
rm /usr/share/vuci/menu.d/menu.json
Let me know if this helps.
Kind Regards,
Hi, thanks you for the answer, I’m running the first command, user admin successfully authenticated. As the Web UI still have the error I’m proceeding now with the second command
Second command made the UI load! Thank you A LOT!
I’ll save the procedure for future issues. Going to fix the second router now 
Adding son information, the command didn’t work in RUT9M_R_00.07.13 after similar failure, but let me tell the UI failed for second time and what I show is the second attempt. So does it need a reboot?
Rm: can’t remove ‘/usr/share/vuci/menu.d/menu.json’: no such file or directory
Note: Web UI now tells “The device is unreachable. Please check the connection and try again” but indeed the device is fully reachable by SSH and by Web Ui before to put credentials
The results on it:
root@Biomasse01:~# logread -f
507 Tue Mar 4 13:22:15 2025 kern.notice User “admin” successfully authenticated on HTTP from 172.27.254.254 to 172.27.2.1
508 Tue Mar 4 13:22:15 2025 daemon.err uhttpd[2162]: vuci: accepted login for admin from 172.27.254.254
509 Tue Mar 4 13:22:16 2025 daemon.err uhttpd[2162]: bad argument #1 to ‘parse’ (string expected, got table)
510 Tue Mar 4 13:22:16 2025 daemon.err uhttpd[2162]: stack traceback:
511 Tue Mar 4 13:22:16 2025 daemon.err uhttpd[2162]: ?: in function <?:82>
512 Tue Mar 4 13:22:16 2025 daemon.err uhttpd[2162]: (tail call): ?
513 Tue Mar 4 13:22:16 2025 daemon.err uhttpd[2162]: ?: in function ‘execute_request’
514 Tue Mar 4 13:22:16 2025 daemon.err uhttpd[2162]: ?: in function ‘handle_request’
515 Tue Mar 4 13:22:16 2025 daemon.err uhttpd[2162]: ?: in function <?:30>
516 Tue Mar 4 13:22:16 2025 kern.err /usr/lib/lua/api/system/ui:bad argument #1 to ‘parse’ (string expected, got table)
@rodrigobarrera Hello,
This seems to be a different issue.
Could you try running the following command and see if it helps?
/etc/init.d/uhttpd restart
Did the issue start after upgrading the device to v07.13? If so, was the upgrade done with the “keep settings” option enabled?
Also, how are you accessing the device? Are you connecting via VPN?
Kind Regards,
Yes, the issue started after upgrade. Indeed I successfully entered the router (zerotier VPN connected) to upgrade, then I applied upgrade successfully. After some time with no need to go to the router at the following day (yesterday) I tried to login into the router and got the message I had on the other routers I mentioned first. So I applied the procedure recommended and got the second issue…
Note I applied the command you suggested now and still have the same message on Web UI when I try to login: “the device is unreachable. Please check the connection and try again”
Note during web UI login failure the router itself never disconnected, checked by ssh CLI and Pinging to another device on VPN
Hello,
It’s likely that the device will need to be reset. Do you have any way to access it afterward, such as via SMS or RMS?
However, before proceeding with the reset, there are a few things I’d like to check first. I will send you a form to fill out. Once completed, we can continue the discussion privately. Please use the ID “12579” when submitting the form.
Kind Regards,
I have great news. Just detected you released RUT9M_R_00.07.13.1, so I moved the .bin file via SCP, then performed an upgrade via SSH CLI and now… it works! 
So will keep an eye on all of them, the family is growing and I can assume 12.3 has the ui login failure that gets worst on 13 but apparently is fixed by 13.1
@rodrigobarrera Hello,
Thank you for letting us know. If the WebUI access issue happens again on version 7.13.1, please let us know.
Kind Regards,