I have a Xiaomi Router 3G running openwrt 18.06. I configured it using Luci, and this worked fine. However, after a few days, Luci is not available anymore. SSH works and the router does its job, I just cannot access Luci (tried on multiple browsers, PC, etc.). Chrome gives me an error "ERR_CONNECTION_RESET" or "ERR_CONNECTION_REFUSED"
I have reset the router completely and now it happened again after some days of usage. How can I reactive Luci? I tried rebooting the router, reinstalling Luci, but none of those things work.
Any commands I can use via SSH to get Luci to work again?
I don't have anything custom installed (i did have some packages the first time I've set up the router, but I didn't install them the second time since I thought those might be the culprit).
The network is set up as follows:
Cable modem --> Xiaomi 3G OpenWRT router which has one 5G and one 2.4G network (with the same name). a second Xiaomi 3G OpenWRT router is connected to this one and acts like a dumb AP (with IP 192.168.1.2). This second router is still available on Luci.
Confirm that you're not running out of resources that is causing uhttpd to hang or crash. CPU or memory would be the first to look at if your logs aren't giving you a clue.
netstat -anl will also show if there is a listener present.
thank you @vgaetera, this worked for me, at least with this i could access to Luci, BUT the root password didn't work anymore, not eaven changing ir from ssh with "passwd".
Finally did a firstboot and configured all again, but why could this happen?? i wasnt eaven at home, just arrived and no internet.
Yes, /dev/root being 100% full is normal (it's the read-only squashfs part). There have been two bugs haunting predominantly NAND based devices (like yours) with kernel 4.14, affecting ubi and overlayfs. These bugs should be fixed in the master snapshots, but they didn't make it for 18.06.1.
You default go Google on ipv6 means your ipv6 talked to Google dns I which is on ipv6
My client faced similar issue 3 month back
As far as I remember it was due to ipv6 only
Just disable ipv6 where ever you had left it enabled
Disable wan6 intergace too if
Make uhttpd listen on ipv4 only
Try this and let me know . I ll get back on this in evening
If you intentionally enabled ipv6 or have it's requirements then also tell here