white http error screen after upgrade error - leave alone?

Started by geoff, March 09, 2026, 08:47:09 AM

Previous topic - Next topic
Hi,

Yesterday I tried upgrading to latest 26.1 point release (already done the 26.1 major upgrade) on a box that's been incrementally upgraded over a couple of years.

Normally my upgrades are completely bulletproof so I didn't note down any details I'm sorry.

This minor update gave me an "error" popup saying in the UI saying upgrade failed, and after that, refreshing the page gave me a white HTTP error code screen. SSH to the box didn't work, so I gave up and rebooted after a minute or so which resulted in boot failure and corrupt filesystem. Fixing the FS errors didn't help because some critical files had been removed and in the end I had no option but to re-flash.

Not sure if this is more of a warning then a question, but probably I should have left the device alone for half an hour or so before attempting the reboot? Not sure it the box was really toasted or not. If anyone knows I'd be very interested to hear.

Thanks for OPNSense, its great
Geoff

ZFS or UFS ?

If on ZFS depending on how many logs and/or snapshots you have the disk may have run out of space during the update process.

If that's the case recovery will require a fresh install, importing the configuration and checking again for updates until both updates and plugins have been installed.


If on UFS there's still a chance to fix things if you can get to a terminal or console, make sure there's some free space available and then try to update again from there


It was UFS since very basic hardware. I got as far as single user mode with the filesystem mounted but didn't think to try re-running an upgrade. Thanks that's good idea if this happens again.


While it's too late now, yes, you should have given it more time. I learnt the hard way as well: :) this always happens when the base packages are upgraded: the GUI becomes unresponsive and SSH fails but if you're logged in already you can use the existing session (but you likely cannot escalate, so best become root beforehand).

I think so too - whoops! Next time I will be more patient ;-)