Messages

Reinstalled yesterday. Ran the update. Everything worked fine. I ran the update on a backup server. Everything worked fine. The only detail that might be of any use is the last thing that appeared before the crash was the refresh.sh script. That's where the system appeared to hang and never came back. I even waited about ten minutes thinking that something complicated might be going on.

Things appear to be back to normal.

I was able to connect to the machine via Meshcommander, and I could see that the boot just fails. A few lines flash by too fast to read, then it hangs. Using  the same workaround that nero355 suggested, get a fresh copy of the software and reinstalled it on the machine.

The remaining question is why the update failed so catastrophically and if this has happened to anyone else. Otherwise, I might've been some kind of weird local corruption that finally bit back.

I just applied the latest update through the gui. The router appears to have crashed and won't restart. I'd reinstall, but I need access to the internet for that. Suggestions?

Are the lingering update candidates is just some kind of random artifact? I'm curious because, the number is different on each identically configured machine.

Health audit follows:

***GOT REQUEST TO AUDIT HEALTH***
Currently running OPNsense 26.7.5 (amd64) at Thu Oct  1 11:24:40 EDT 2026
>>> Root file system: zroot/ROOT/default
>>> Check installed kernel version
Version 26.7.4 is correct.
>>> Check for missing or altered kernel files
No problems detected.
>>> Check installed base version
Version 26.7.4 is correct.
>>> Check for missing or altered base files
No problems detected.
>>> Check installed repositories
OPNsense (Priority: 11)
>>> Check installed plugins
No plugins found.
>>> Check locked packages
No locks found.
>>> Check for missing package dependencies
Checking all packages: .......... done
>>> Check for missing or altered package files
Checking all packages: .......... done
>>> Check for core packages consistency
Core package "opnsense" at 26.7.5 has 69 dependencies to check.
Checking packages: ...................................................................... done
***DONE***

I just updated to 26.7.5, and the discrepancy returned:

***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 26.7.5 (amd64) at Wed Sep 30 09:55:28 EDT 2026
Fetching changelog information, please wait... done
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching data: .......... done
Processing entries: .......... done
OPNsense repository update completed. 946 packages processed.
All repositories are up to date.
Checking for upgrades (161 candidates): .......... done
Processing candidates (161 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.
***DONE***

I ran this command from the shell:

opnsense-update -fp

That seemed to clear everything up. Both machines are current and now show zero candidates.

On my network I have a live OPNsense machine and an identically configured backup. This is not HA. It's just a backup machine dangling on the network by its WAN port so I can keep it updated and swap it in if the main router fails. It doesn't route anything because the LAN port isn't connected. The setup has been fine for ages.

I noticed recently when I check for updates, the output doesn't look right. I have not changed anything in either configuration for a long time. I just apply updates as they become available. Does anyone have any theories?

MAIN MACHINE

***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 26.7.4_1 (amd64) at Fri Sep 25 09:59:47 EDT 2026
Fetching changelog information, please wait... done
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching data.pkg: .......... done
Processing entries: .......... done
OPNsense repository update completed. 931 packages processed.
All repositories are up to date.
Checking for upgrades (1 candidates): . done
Processing candidates (1 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.
***DONE***

BACKUP MACHINE
***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 26.7.4_1 (amd64) at Fri Sep 25 10:00:22 EDT 2026
Fetching changelog information, please wait... done
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching data.pkg: .......... done
Processing entries: .......... done
OPNsense repository update completed. 931 packages processed.
All repositories are up to date.
Checking for upgrades (86 candidates): .......... done
Processing candidates (86 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.
***DONE***

Thank you both. I typed before thinking. The answer was self-evident. Worked perfectly.

Thank you! How do I apply this? Or should I just wait for the next release?

It appears to have fixed itself.

I just applied the 25.1.6 update, and the announcement widget not longer appears to work. It displays the message "Unable to contact information feed."

I just applied the 25.1.6 update, and the option to see Kea DHCPv4 leases seems to have disappeared.

Speaker is fine. This is a replacement machine, too. In the previous one, I replaced the speaker, and still no sound. I replaced the whole machine with an identical one (for different reasons), and moved the disk/network card over, so it's essentially the same system as before. Still no sound.

I know the speaker's good because it works during BIOS updates. I'm betting this is one of those mysteries that will have me slapping my forehead later, but I've gone through all the troubleshooting steps I can think of. Since it's now a completely new machine but the same software image, I'm suspecting some kind of corruption? A fresh install might do the trick, but I'd like to avoid that complication.

t's not a critical function, but I like that the machine lets you know what it's up to during startup and shutdown.

Haha. No.

But I checked anyway.

No.