26.1.4 Update Took Everything Out

Started by Disperser5395, March 15, 2026, 04:10:50 AM

Previous topic - Next topic
I was attempting to install the acme community plugin. I've been running OPNSense for about three years with no problems. I saw that I needed an update to install the plugin. Updated to 26.1.4.
Upon reboot I had nothing. No connection to the internet. No WAN gateway. None of my firewall rules working.
Before shutting down and using a commercial wifi router I have lying around, I did notice something about new firewall rules. Seems strange that would take down my entire network, though.
At this point I'll need to start fresh. Is there a guide that encompasses whatever seemingly major changes have been made lately? I'm not an OPNSense expert, obviously, but I was using it to do everything I needed with Suricata and Mullvad working just fine. At this point I would be installing OPNSense from the beginning and going through setup. The installers I'm seeing appear to go back a few months.   that makes me think a fresh install will put me back in the same position as soon as I update. Again, is there a guide that includes whatever changes were made to the system so that I can start from there? Thanks everyone!


You mean the release notes?

https://docs.opnsense.org/releases/CE_26.1.html

The Firewall: Rules (new) interface does not change anything unless you actively migrate your rules and start to use it instead if the legacy one. Not a plausible cause of your disruption.
Deciso DEC750
People who think they know everything are a great annoyance to those of us who do. (Isaac Asimov)

From what did you update? I notice you mentioned reboot, which does not happen in a 26.1.3 to 26.1.4 upgrade unless you do it yourself or have it set as an automatic action.
Deciso DEC697

There's a recent post on these forums where a similar upgrade took out someone's WAN gateway and other posters concurred that the same happened to them. When the system rebooted, my WAN gateway was gone too. I tried to recreate it but no change.

I ran the system update from Dashboard. It didn't seem like a major upgrade - from 26.1.1 to 26.1.4. I do remember upgrading from 26.1.1 to either x.1.2 or x.1.3 back in January and having the same result. At that time I simply restored my old config and at least had internet access again.  This upgrade gave me a message that a reboot would occur after the update.

As I say I'm going to start fresh, following OPNSense docs as I did when I first set it up a couple of years ago. Hopefully in that process I might see something I missed along the way?


March 18, 2026, 10:57:50 AM #4 Last Edit: March 18, 2026, 11:04:49 AM by TomS2
Hi Disperser5395,

the Update to 26.1.4 seems to have problems on some installations. The problems I got range from Danger/Error-Messages (seemingly without consequences) to broken systems after the update and segfaults.

I just updated a fresh delivered DEC2687 and got a "Danger, unexpected error, check log for details" message while updating. Couldn't find any consequences or further information in the logs.

Yesterday I updated an other DEC-System from 26.1.1 to 26.1.4 and after the update the firewall system was broken (hardware was ok, only the system wasn't able to boot anymore). The update seems to have deleted necessary BSD-Files, so the system couldn't start anymore. Luckily there are some threads in this forum how to resolve this problem (booting in single user mode, repairing login files, creating repository file, updating manual, downgradeing pkg-programm...). It took some time, but finally the opnsense was running normal again, all health-checks where ok, config wasn't lost.
Didn't need to reinstall the opnsense or restore the previous config-backup.

Couldn't figure what is causing the Danger-Messages (seems like lots of people get them) or the broken system yesterday (I'm at least not the only one who got this - so I was able to use the tips on this forum to repair it).
I have to add: I'm using zenarmor on most opnsens. So maybe that's connected with my problem with the broken system after the update. But there is no direct indication (like log message) for be the cause.