Unknown error occured when logging in

GL-MT6000

Today the power cut off at home and after the router booted back up that I began receiving this error

Unknown error occurred. Please check the network environment or reboot the device.

Rebooting doesn't work. Well, the whole thing started after a reboot anyway.

What I can say, is that yesterday I was playing with the openwrt backend, trying to find good Traffic statistics packages. I installed vnstat, nlbwmon, and luci-app-statistics. (Sadly none of them do a good job, and I suspect it's because of network acceleration being on.)

In any case, I still have access to the backend.
Can I restore the fancy frontend without losing all my settings? Flash the default image? I don't mind losing the installed packages (they suck so far anyway).

Can web ui still go in?

ssh  192.168.8.1
cat /var/log/nginx/error.log
2024/09/20 04:40:57 [crit] 5995#0: *6 connect() to unix:/var/run/ngx-ubus-proxy.sock failed (2: No such file or directory), client: 192.168.0.2, server: , request: "POST /rpc HTTP/1.1", host: "192.168.0.1", referrer: "http://192.168.0.1/"
2024/09/20 04:40:57 [error] 5995#0: *6 lua entry thread aborted: runtime error: /usr/share/gl-ngx/oui-rpc.lua:61: attempt to index local 'res' (a nil value)
stack traceback:
coroutine 0:
        /usr/share/gl-ngx/oui-rpc.lua:61: in function '?'
        /usr/share/gl-ngx/oui-rpc.lua:160: in function </usr/share/gl-ngx/oui-rpc.lua:1>, client: 192.168.0.2, server: , request: "POST /rpc HTTP/1.1", host: "192.168.0.1", referrer: "http://192.168.0.1/"

I can login to luci, but not the vendor UI.

Edit: Shit. I think that's my fault. I also updated some packages while I was installing things.
I remember lua-eco something.

If I remove them, will that fix things?
(I don't know what I updated, so I don't know what to remove tho. Also, wouldn't it break things IMMEDIATELY? The vendor UI was working yesterday even after the update. Or does it take a reboot for things to break?)

Which version of the firmware?

the latest
4.6.4

Yes, it is due to the update of lua-eco
This upgrade package will be deleted later
It's a little tricky. I need to test it
The fastest way to do this right now is to restore factory Settings

Damn it. OpenWrt wiki even had a warning against updating packages willy-nilly. Except I didn't see the warning before doing it.

Is it possible to export then restore my settings? The frontend UI included? Like all my VPN private keys? (That'll be a pain if I have to recreate for all devices.)

And then restore to factory?

The router is working as configured, mind you, so I'm in no rush.

I need to test it
See if there's any way

1 Like

You can export your config using luci.

The concern was - is it safe to export, factory reset, then import?

Mostly yes. Upgrading the packages does not upgrade the config.

But if you have concerns, wait for ywps reply.

1 Like

opkg list-installed|grep lua-eco
Can you execute this command and let me know the result?

lua-eco - 2024-1-16-c07b86b1-1
lua-eco-base64 - 2024-1-16-c07b86b1-1
lua-eco-dns - 2024-1-16-c07b86b1-1
lua-eco-http - 2024-1-16-c07b86b1-1
lua-eco-ip - 2024-1-16-c07b86b1-1
lua-eco-log - 2024-1-16-c07b86b1-1
lua-eco-md5 - 2024-1-16-c07b86b1-1
lua-eco-mqtt - 2024-1-16-c07b86b1-1
lua-eco-netlink - 2024-1-16-c07b86b1-1
lua-eco-nl80211 - 2024-1-16-c07b86b1-1
lua-eco-socket - 2024-1-16-c07b86b1-1
lua-eco-ssl - 2024-1-16-c07b86b1-1
lua-eco-ubus - 2024-1-16-c07b86b1-1

You upgraded all packages related to lua-eco?

lua-eco-ubus_3.6.0-1_aarch64_cortex-a53.zip (9.1 KB)

1.Use winscp to upload the decompressed ipk file to the tmp directory
2. ssh  192.168.8.1
3. opkg --force-reinstall install  /tmp/lua-eco-ubus_3.6.0-1_aarch64_cortex-a53.ipk

Reinstalling the ipk should fix the problem
But I'm not sure there's anything else
Because you seem to have upgraded all the packages

1 Like

That allowed me to log back in. Thanks.

Yea. I could still just factory reset from luci (that part was never broken), then import my config backup.
That would probably accomplish the same goal without breaking anything.

Anyway, thanks for the help. Great support.

Hello,
I was having the same problem.
Fixed with the ipk provided in answer #16.
I had to reboot the device in order to get my login into GL.iNet interface back.

PS : I tried to use scp command on my mac, but it failed...
As I still had ssh access, I use curl command and unzip to get the ipk.