I have been a happy user of OPNsense for years (on a small commercial box from Deciso).
Today, when I tried updating, I got the error "The release type 'opnsense' is not available on this repository."
As recommended, I ran a health audit, and revealed some missing dependencies and package version mismatches (full log below).
The troubleshooting section on opnsense.org briefly mentions that "When mismatches are reported, you can reinstall affected packages in the Packages section of the firmware screen.", but there is no further elaboration. It's unclear to me how and why "reinstalling" the package would resolve a version mismatch, and also the missing dependency is not in the list of packages, so I don't know how to "reinstall" that.
I did not find a troubleshooting section going into further detail.
How should I proceed?
Health audit output:
***GOT REQUEST TO AUDIT HEALTH***
Currently running OPNsense 25.7.5 (amd64) at Sun Oct 26 19:09:18 CET 2025
>>> Root file system: /dev/ufs/OPNsense
>>> Check installed kernel version
Version 25.7.5 is correct.
>>> Check for missing or altered kernel files
No problems detected.
>>> Check installed base version
Version 25.7.5 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
py37-markupsafe has a missing dependency: python37
py37-markupsafe has a missing dependency: py37-setuptools
py37-markupsafe is missing a required shared library: libpython3.7m.so.1.0
>>> Check for missing or altered package files
Checking all packages: .......... done
>>> Check for core packages consistency
Core package "opnsense" at 25.7.5 has 67 dependencies to check.
Checking packages: .....................
openssh-portable-10.0.p1_2,1 version mismatch, expected 10.2.p1,1
Checking packages: ..
opnsense-25.7.5 version mismatch, expected 25.7.6
Checking packages: ...
opnsense-update-25.7.5 version mismatch, expected 25.7.5_1
Checking packages: ..............................
py311-sqlite3-3.11.13_11 version mismatch, expected 3.11.14_11
Checking packages: ........
suricata-7.0.12 version mismatch, expected 8.0.1
Checking packages: .
syslog-ng-4.8.2_4 version mismatch, expected 4.10.2
Checking packages: ..
wpa_supplicant-2.11_5 version mismatch, expected 2.11_7
Checking packages: . done
***DONE***
You can safely delete py37-markupsafe. It's a relic from a previous version that was not properly removed. Python 3.7 is EOL.
What Patrick says.
pkg delete py37-markupsafe
And the outdated packages are from OPNsense 25.7.5. They should get updated along with the OPNsense 25.7.6 update.
Cheers
Maurice
Quote from: Maurice on October 26, 2025, 09:21:02 PMWhat Patrick says.
pkg delete py37-markupsafe
How do I do that in WebUI? Can I open a console somewhere in there?
Quote from: Maurice on October 26, 2025, 09:21:02 PMAnd the outdated packages are from OPNsense 25.7.5. They should get updated along with the OPNsense 25.7.6 update.
And as I said....update isn't working (see first error message in OP). The actual question is how to get that running, but I though starting with fixing the health audit issues is the way to start.
Quote from: Asperamanca on October 27, 2025, 07:45:05 AMHow do I do that in WebUI? Can I open a console somewhere in there?
SSH it is. No UI console.
> Today, when I tried updating, I got the error "The release type 'opnsense' is not available on this repository."
You mean this?
https://github.com/opnsense/changelog/blob/903b8699008e4e983060dc70de221a4718e95ca7/community/25.7/25.7.6#L9-L14
Cheers,
Franco
That seems to be spot on, but how does one upgrade the package manager first?
It seems I somehow managed to solve it "by accident". I chose "reinstall" for package "pkg". It became a little scary when the WebGui apparently crashed (no longer reachable), but hey, it's almost Halloween. WebGui was fixed by a hard reboot, after which I also made sure I had SSH access as a backup if necessary (should have done that first, but alas, we learn by trial, but mostly by error).
Strangely, after that episode the WebGUI reported "no packages to update", and the health audit no longer complained about conflicting packages. I'm a bit sceptical if the newest update is really installed (when? how?), and it also looks a bit weird that the health audit reports "running 25.7.6" but also kernel version "25.7.5"
Not saying I understand what happened, but it seems to work.
Thanks for your pointers. They were a bit cryptic for someone not doing network admin work regularly, but they helped me onto the right track.
Kernel 25.7.5 is correct. Not every OPNsense update includes a base / kernel update.