Update from core 157 to 158 - WUI grief

[gh4light (Gary Hedquist)]

Used Pakfire to Update two similar PCs from core 157 to core 158.
After the update, I could NOT connect via the WUI to either PC ?

Nuked both PCs and did a new install of core 158 on one PC and a new install of core 156 on the other.
After the install, I could connect via the WUI to both PCs.

Used Pakfire to Update the PC /w core 156 to core 158.
After the update, I could connect via the WUI to both PCs.
Why the core 157 to 158 update caused the WUI problem is a mystery to me.

[jon]

Hi Gary!

There are two other threads concerning this issue. One is here:

No access to WebGUI and more after update from Core 156 to 157

Hi there, I started the update from Core 156 to Core 157 on one of my remote IPFires using an APU1D hardware. (I had connection through an OpenVPN tunnel through the Internet.) While updating and before reboot, I lost the connection to the WebGUI: I got the error message “internal server error”. Therefore I tried to connect via SSH, which worked. I just initiated a reboot, which worked as well. Following the reboot, I could not reestablish an OpenVPN tunnel anymore. I had lost complete contro…

and I see it is closed.

And one it here:

Trouble when upgrading from core 157 to core 158

Today I did (try) an upgrade from core 157 to core 158. The upgrade partially worked. I still have internet connection However, I cannot log into the WebUI https://<ipfire_ip>:444 at the green or blue interface anymore. In Firefox I get the error message: Beim Verbinden mit <ipfire_ip>:444 trat ein Fehler auf. PR_CONNECT_RESET_ERROR When I reboot with a connected null modem cable, I get an error that avahi failed. > > Loading Sensor Modules: …

I believe the problem was permissions issue related to the tar command.

I suggest adding your comments to the second thread:
https://community.ipfire.org/t/trouble-when-upgrading-from-core-157-to-core-158/5842?u=jon

I will close this thread so we don’t have duplicates.

Jon