Actually, I didn't break anything - just saving a completely working config, never did any changes in LuCI or similar and restoring that from 4.6.2. to 4.6.4.
Anyway, following your advice - nginx couldn't bind, the ports were in use by uhttpd. No clue how to proceed here and if it's worth to fix it on console ...
Stopping uhttpd and starting ngnix leads to a 502.
No, I didn't. It's a rather plain config, I'd say. Just MAC based Wireguard is on. Not much added to this.
I did a fallback to 4.6.2 now after trying a few different approaches to import my config with 4.6.4. Interestingly, the online upgrade from 4.6.2 to 4.6.4 fails again. That was my motivation to do a factory reset.
Backup is from 4.6.2.
I tried all combinations of import. Last try was clean uboot flash of 4.6.4, the GL GUI was obviously available but after import it was gone again.
After that I decided for a fallback with uboot. Import of 4.6.2 config into 4.6.2 worked fine.
Would you be fine with sending the backup file via PM to me?
Please beware that there might be personal details in it - which I would be able to see then.
Hello, good morning. Something similar happened to me. Being in version 4.6.2 I made a backup of the configuration. I upgraded to version 4.6.4 without keeping the configuration, restored the backup and the Gl-iNet interface disappeared. I went back to 4.6.2 and restored the backup. Then I upgraded to 4.6.4 and kept the settings and everything came back including the Gl-iNet GUI.
Regards
Had any of you mounted a usb or storage device to /overlay ?
Especially with ext4 styled partitions you can get into issues quick because it litterly overlays the current partition.
With other words, when you upgrade it doesn't upgrade the packages on the overlayed part but on the nand chip.
But when it boots, it still mounts the old overlay from the external device, thus causing to load incompatible drivers with the mismatched kernel version and then get stuck on boot loop.
this might not be the cause of packages, but maybe the fstab got rolled back wrongly?
If the firmware upgrading with keep settings and to the newer version is no problem, that is ok.
In different versions, there are probably some new/old/removed features changes that using backup export/import may break the GL GUI.
(As similar situations also occur with different customized versions of OpenWRT.)
The GL firmware upgrades with keep settings, it will optimize the configuration for compatibility after the upgrade. If backup export/import in the Luci, there is no this kind of optimization.