"The release type "opnsense" is not available on this repository" on fresh 25.7

[LGDL]

For some reason on a fresh 25.7 I need to request a check for upgrades twice before it proceeds.

After installing version 25.7 on Velocloud 510, I attempted upgrading to 25.7.8.

I got this message in a popup:

Code Select Expand

Firmware status :
The release type "opnsense" is not available on this repository.
In the background, the output showed:

Code Select Expand

***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 25.7 (amd64) at Sun Nov 30 09:51:32 EST 2025
Fetching changelog information, please wait... done
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: .......... done
Processing entries: .......... done
OPNsense repository update completed. 911 packages processed.
All repositories are up to date.
Updating database digests format: .......... done
New version of pkg detected; it needs to be installed first.
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
pkg: 1.19.2_5 -> 2.3.1_1

Number of packages to be upgraded: 1

The process will require 9 MiB more space.
6 MiB to be downloaded.
[1/1] Fetching pkg-2.3.1_1.pkg: .......... done
Checking integrity... done (0 conflicting)
[1/1] Upgrading pkg from 1.19.2_5 to 2.3.1_1...
[1/1] Extracting pkg-2.3.1_1: .......... done
pkg: Repository OPNsense cannot be opened. 'pkg update' required
Checking integrity... done (0 conflicting)
Your packages are up to date.
self: No packages available to install matching 'opnsense'
***DONE***
I am not sure why this happened but I requested a new check for upgrades and the check then proceeded normally, showing the changelog and proposing the upgrade.

[Patrick M. Hausen]

The system needed to upgrade the pkg tool first before it could use that to upgrade the rest of the system.

[LGDL]

The system needed to upgrade the pkg tool first before it could use that to upgrade the rest of the system.

Well, yes, I can read that. Just not sure why this update would not be included in the installer.

[franco]

Because the installer predates the update?

It's a known issue since the package manager made a huge jump forward for different reasons and it wasn't fully compatible with the code anymore.

https://github.com/opnsense/changelog/blob/fc3bf62b7a67c598f14a122d6662fdb974b0d00e/community/25.7/25.7.6#L9-L14



Cheers,
Franco

[Maurice]

Just not sure why this update would not be included in the installer.

The installer images get updated twice a year and don't contain any changes made since the last major release. That's a little different to other software where you can typically download an installer for the latest version.

If you need to install the latest version directly, you'd have to build your own image (or use opnsense-bootstrap).

Cheers
Maurice