[Solved by reboot] 26.7 Update-> "failed, signature invalid"

[Cableguy_]

Try another mirror

That led me into this in the first place (changing & testing mirrors via browser GUI). How to change mirrors in console, and which one should work?

[newsense]

If vi doesn't scare you you can edit /usr/local/etc/pkg/repos/OPNsense.conf and use pkg.opnsense.org

Changes there are not permanent but it should suffice to download the 3 files needed for the major upgrade.

Once you edited the file type exit and 12 to retry the 26.7 upgrade

[franco]

Might be more of an LTE, IPv6 or otherwise unstable connection.

# curl -o packages-26.7-amd64.tar https://pkg.opnsense.org/FreeBSD:14:amd64/26.1/sets/packages-26.7-amd64.tar
# curl -o packages-26.7-amd64.tar.sig https://pkg.opnsense.org/FreeBSD:14:amd64/26.1/sets/packages-26.7-amd64.tar.sig
# opnsense-update -upr 26.7 -l .
(reboot)

If curl also fails I have no way to help you.


Cheers,
Franco

[Cableguy_]

Might be more of an LTE, IPv6 or otherwise unstable connection.

# curl -o packages-26.7-amd64.tar https://pkg.opnsense.org/FreeBSD:14:amd64/26.1/sets/packages-26.7-amd64.tar
# curl -o packages-26.7-amd64.tar.sig https://pkg.opnsense.org/FreeBSD:14:amd64/26.1/sets/packages-26.7-amd64.tar.sig
# opnsense-update -upr 26.7 -l .
(reboot)

If curl also fails I have no way to help you.


Cheers,
Franco

Thanks, I'll try this later today. Fresh install is also an option in case this doesn't fix this error.
Let's hope there won't be many more of these cases around.

[Cableguy_]

Might be more of an LTE, IPv6 or otherwise unstable connection.

# curl -o packages-26.7-amd64.tar https://pkg.opnsense.org/FreeBSD:14:amd64/26.1/sets/packages-26.7-amd64.tar
# curl -o packages-26.7-amd64.tar.sig https://pkg.opnsense.org/FreeBSD:14:amd64/26.1/sets/packages-26.7-amd64.tar.sig
# opnsense-update -upr 26.7 -l .
(reboot)

If curl also fails I have no way to help you.


Cheers,
Franco

Hey, Cheers, and many thanks, now it seems this corrected the whole situation! Thanks for your help.
It seems to be ok also from audit -> health check.

***GOT REQUEST TO AUDIT HEALTH***
Currently running OPNsense 26.7 (amd64) at Thu Jul 16 20:16:36 EEST 2026
>>> Root file system: zroot/ROOT/default
>>> Check installed kernel version
Version 26.7 is correct.
>>> Check for missing or altered kernel files
No problems detected.
>>> Check installed base version
Version 26.7 is correct.
>>> Check for missing or altered base files
No problems detected.
>>> Check installed repositories
OPNsense (Priority: 11)
SunnyValley (Priority: 7)
>>> Check installed plugins
os-cpu-microcode-intel 1.1
os-ddclient 1.31_1
os-dmidecode 1.2
os-hw-probe 1.0_1
os-isc-dhcp 1.0_6
os-sensei 2.6.1
os-sensei-updater 2.0
os-smart 2.4
os-sunnyvalley 1.5_2
os-vnstat 1.4
>>> 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 has 68 dependencies to check.
Checking packages: ..................................................................... done
***DONE***

[franco]

Looks good indeed. I may add a curl compatibility download mode to opnsense-update for overcoming such problems if I have a bit of free time.


Cheers,
Franco

[Sport]

Looks good, but missing the packages:

# opnsense-update -upr 26.7 -a FreeBSD:15:amd64/26.7
(reboot)


Cheers,
Franco

Glad I found this post, as I was having the exact same issue following an upgrade attempt that hung, the above command was successful at finishing the upgrade to 26.7 and a clean health check following.

[knowHoff]

had the exact error messages

Code Select Expand

Version 26.7 is incorrect, expected: 26.1.11

curl + install + reboot = no boot

the machine did not come back again, had to cold reset.

After cold reset, again:

Code Select Expand

Version 26.7 is incorrect, expected: 26.1.11

did not have the time to narrow down the fault,

so did a fresh install with successful config restore.

[franco]

Keep in mind the instructions are for this specific issue. It's not a full upgrade sequence using curl.


Cheers,
Franco

[knowHoff]

I assume I had the same issue, at least the health check log looked the same like health check log

Interestingly I have two almost exact same systems.

The other system updated fine from the webGUI.

Thank you for taking care of us!

Cheers