I have a GL-MT3000 router that was working perfectly. I temporarily used it for an event and reset it to factory settings to configure it for specific needs. I forgot to back up the current configuration, but I had an older backup from months ago (dated October 3, 2024). I believe I updated the router to a newer firmware version in the meantime.
After the event, I restored the old backup via LuCI on the latest firmware, and the GL.iNet UI stopped loading—accessing the router’s IP now redirects directly to the LuCI interface. All settings from the backup seem to work, but the GL.iNet UI is inaccessible.
I checked the backup date, downloaded the corresponding firmware version from https://dl.gl-inet.com/router/mt3000, reflashed it manually via LuCI without keeping settings, and restored the backup again. The issue persists: the router functions as configured, but only the LuCI interface loads.
Additionally, after resetting to factory settings, I accessed the GL.iNet UI normally on the default IP range (192.168.8.1). I changed the IP range back to my previous one (192.168.200.1) without modifying other settings. Now, when accessing the new IP (192.168.200.1), I receive a "403 Forbidden" error.
The GL.iNet UI still doesn’t load. What could be causing this, and how can I restore the GL.iNet interface? Any help is appreciated!
Backup files created via Luci are typically only compatible with the firmware version they were created under, so please avoid using them across different versions.
Regarding the “403 Forbidden” error displayed after modifying the IP address, could you share any videos or screenshots with us to help us better understand what happened?
I checked the backup date (October 3, 2024) and rolled back to the firmware version available that day from https://dl.gl-inet.com/router/mt3000, as mentioned. Reflashed via LuCI without keeping settings and restored the backup—still, the GL.iNet UI doesn't load.
From the backup file (which I can extract fully), is there a way to read which exact firmware version was in use when it was created?
The default backup file should not contain version-related information.
Therefore, the version may be unknown, and the router may need to be reconfigured.
In the future, you may consider adding the /etc/glversion file under Luci - Backup / Flash Firmware - Configuration to include firmware version information in the backup file.
Please Sir!Can you share a pcvr guide on youtube or a list of settings to make pcvr this stutterless nowaday as yours?Its non sense that I have to become some kind of quantum radio operator and play optimisation simulatior just to play a bit with a performance what your nervsystem bears during you know it could be better just maybe they willingly sabotage wireless vr performance.Ive seen a video of yours,I have same flint 2 quest 3 and 4090 laptop.Even after finetuning 12 months after giving up airllink which was a stuttery mess,now I finetune steamlink staamvr but i still have some last stutters what no setting lowering can fix etc.Its like a weapon.Do you have any ideas how to fix it?I have vd too but on automatic spacewarp I have vr multiframegen manifested.I got to a point where vr optimisation is serious health risk for me.It crazes me.
