None of the buttons, check-boxes or icon-links work in the GUIs of either of my IPFires. I can navigate through the menus and drop-down lists appear, but clicking on buttons, etc., only causes the page to reload with no effect on the settings. I tried rebooting each from the CLI, but that did not fix the issue.
I’m still digging through the Forum here, but I’ll throw this out in case there’s a fix I haven’t come across yet.
I have two IPFires in a site-to-site over Wireguard. They’re each also hosting VMs running AdGuardAtHome. One of the two firewall VMs also hosts my Domain Name. Both were updated to Core 201 about two months ago. It was late and I put off making post-update backups for another day - and forgot about it until yesterday. I notice that Core 202 is out, as well.
I can’t do anything from the GUI except look at what’s already configured.
I’d be willing to try updating to Core 202 in hopes that it fixes the issue. Is there a way to initiate the update from the CLI?
Otherwise, what can I look at? Nothing shows up in /var/log/httpd/error_log.
One thing that may or may not have affected these is, they both experienced an 8-hr power outage last week (currently, both sites are at the same physical location on different ISPs). If I had known it was going to last 8-hrs, I would have shut them down while still on their UPSs.
Upgrading an unstable machine without a backup is not recommended.
1 - If you have console access, you can start a backup using the command /usr/local/bin/backupctrl include. You can retrieve the backup with logs from /var/ipfire/backup/YYYY-MM-DD-HHMN.ipf.
2 - Try accessing your machines using their IP address rather than their FQDN (e.g., https://192.168.10.1:444 instead of https://ipfire.localdomain:444).
Or try using elinks from the console.
Using the IP addresses made no difference. I was able to generate backups and update one of the two via Pakfire using elinks. Haven’t tried the other yet because… day job.
However, I still do not have the ability to make any changes via the WUI.
I found a post here where someone what having issues with specific WUI interfaces and it turned out to be a ownership issue with the settings files. I checked mine and they appear to be correct (“nobody:nobody”), but some of their parent directories in /var/ipfire have “root:root” ownership. I tried setting them all to “nobody:nobody” but that didn’t change anything.
Don’t the “.pl” files need the execute permission?
It is correct that some of them are root:root and some nobody:nobody. I would not advise randomly change ownerships, it is likely to break something.
No.
As this happened after a power outage, I would suggest doing a fresh install followed by a restore from a previous backup that you have made and that was previously downloaded from the IPFire system.
I would not do a restore from the backup that you just created because the system was in non-working mode and the backup may just reproduce that system.
I would not do a restore from the backup that you just created because the system was in non-working mode and the backup may just reproduce that system.
I wasn’t planning on doing that. I keep an entire archive of backups since install for both firewalls.
I was really hoping the update to 202 would fix the issue. I really wanted to avoid dealing with the VMs on each. I guess I should just move those VM functions to a real PC..
I don’t know that anything would show up in your browser log since you said that the pages were refreshing, but you might want to check and see if anything shows up there. I use Firefox and access the browser console with F12. Not sure on other browsers.
Just to add that if there is an issue with file permissions, from my experience, it will show up in the error_log. Since you’ve got nothing in error_log, I would think it unlikely that you’re having file permissions issues.
Regards,
Stephen
Edit: Another thought - have you tried accessing the Web GUI from another browser or PC? Maybe something is going on with the client PC you’re accessing the Web GUI from. I add that because it seems a little strange that two different IPFire machines would develop the exact same problem from a power outage…
Edit: Another thought - have you tried accessing the Web GUI from another browser or PC? Maybe something is going on with the client PC you’re accessing the Web GUI from.
Would you believe… I use Waterfox for “personal” browsing from my work PC. Everything works as expected if I use Firefox.
I was about to suggest opening a browser window in Private/Incognito mode and try it there. There might be some cookie or cache issue. Glad you found the solution.
