Hi
I've just upgraded to 25.1.12 today.
I was presented with a major upgrade release of 25.7 on the console updater.
However doing this results in:
Fetching packages-25.7-amd64.tar: ..[fetch https://pkg.opnsense.org/FreeBSD:14:amd64/25.1/sets/packages-25.7-amd64.tar.sig: Not found] Failed, no signature found
This seems like a reasonable message given the URL isn't valid - notice the 25.1 in the URL.
Is this expected behaviour at the moment?
If so I'll just remain on 25.1.12 for now.
Thanks.
It could be because 25.7 will be released tomorrow. :)
Cheers,
Franco
Just too excited and can't wait I guess :)
Thanks for confirming.
Trying to upgrade from 25.1.12 and it says that it's all up to date. Unable to upgrade to 25.7.1
Same, and I'm not using a mirror...
If you don't want me to verify the upgrade before setting it live we can do that next time. Why are we always having these types of posts not even an hour into the release? :)
Cheers,
Franco
I guess because I saw on X "OPNSense 27.5 released..." and assumed it would be there? :)
I thought the release post means that the upgrade was live. That's all, that doesn't appear to be the case here.
Quote from: franco on July 23, 2025, 02:04:48 PMIf you don't want me to verify the upgrade before setting it live we can do that next time. Why are we always having these types of posts not even an hour into the release? :)
Cheers,
Franco
I vote for verifying the upgrade. Maybe it's just me.
I would hope so too. Meanwhile the upgrade from 25.1.12 is live.
Cheers,
Franco
Upgraded my spare R86S router, with basic config, with no issues.
Entire process was smooth.
Will start upgrading the other 4 in least important order :)
It appears the upgrade path from 25.1.12 to 25.7 isn't complete yet.
***GOT REQUEST TO UPGRADE***
Currently running OPNsense 25.1.12 (amd64) at Wed Jul 23 07:17:10 CDT 2025
Fetching packages-25.7-amd64.tar: ........................................................................... done
Fetching base-25.7-amd64.txz: ........................ done
Fetching kernel-25.7-amd64.txz: ........... done
Extracting packages-25.7-amd64.tar... done
Extracting base-25.7-amd64.txz... done
Extracting kernel-25.7-amd64.txz... done
Please reboot.
>>> Invoking upgrade script 'sanity.sh'
Passed all upgrade tests.
>>> Invoking upgrade script 'gdrive-plugin.php'
Google Drive backup is not active. Not installing replacement plugin.
>>> Invoking upgrade script 'openvpn-plugin.php'
OpenVPN client/server legacy features are not active. Not installing replacement plugin.
>>> Invoking upgrade script 'strongswan-plugin.php'
IPsec legacy tunnels are not active. Not installing replacement plugin.
>>> Invoking upgrade script 'cleanup.sh'
find: /usr/local/lib/libicuio.qo: No such file or directory
find: /usr/local/share/man/man3/SSL_CTX_set_default_verify_dir,3ossl.gz: No such file or directory
>>> Error in upgrade script '90-cleanup.sh'
The upgrade was aborted due to an error.
***DONE***
Quote from: psilovybin on July 23, 2025, 02:37:56 PMfind: /usr/local/lib/libicuio.qo: No such file or directory
find: /usr/local/share/man/man3/SSL_CTX_set_default_verify_dir,3ossl.gz: No such file or directory
That looks like typos in the script. "libicuio.qo" should be "libicuio.so", and "SSL_CTX_set_default_verify_dir,3ossl.gz" should be "SSL_CTX_set_default_verify_dir.3ossl.gz".
Quote from: beneix on July 23, 2025, 02:57:07 PMQuote from: psilovybin on July 23, 2025, 02:37:56 PMfind: /usr/local/lib/libicuio.qo: No such file or directory
find: /usr/local/share/man/man3/SSL_CTX_set_default_verify_dir,3ossl.gz: No such file or directory
That looks like typos in the script. "libicuio.qo" should be "libicuio.so", and "SSL_CTX_set_default_verify_dir,3ossl.gz" should be "SSL_CTX_set_default_verify_dir.3ossl.gz".
I'm running an audit now.. showing some inconsistency.. not sure why, i don't dig into the guts of opnsense.
*EDIT* After running Audit, still has the same error
I was able to upgrade by dropping to shell and typing
opnsense-update -ur 25.7 -a 25.7
Upgraded via WebUI, everything seems fine so far.
I've had a few issues.
First, I needed to change UEFI settings to legacy in BIOS, otherwise the router hung on reboot (25.1.12 was booting fine).
Now, after a reboot the machine hangs right after the microcode is reinstalled with "Reloading firmware configuration." I can force a reboot but am in an intermediate state (kernel 14.3, but still Opnsense 25.1.12)
Quote from: psilovybin on July 23, 2025, 03:25:14 PMI was able to upgrade by dropping to shell and typing
opnsense-update -ur 25.7 -a 25.7
If the file system is showing errors pre-upgrade for valid reasons I highly recommend not forcing it to upgrade without a disaster plan.
Cheers,
Franco
Quote from: franco on July 23, 2025, 04:24:43 PMQuote from: psilovybin on July 23, 2025, 03:25:14 PMI was able to upgrade by dropping to shell and typing
opnsense-update -ur 25.7 -a 25.7
If the file system is showing errors pre-upgrade for valid reasons I highly recommend not forcing it to upgrade without a disaster plan.
Cheers,
Franco
I understand, however, just me and my mom on this router. worse comes to worse, i'll spool up the backup VM. There was nothing I could do. An audit fixed some stuff, but there was no upgrade path moving forward and i had to force an upgrade. it did work without a hitch.
Quote from: JailYard on July 23, 2025, 04:22:18 PMI've had a few issues.
First, I needed to change UEFI settings to legacy in BIOS, otherwise the router hung on reboot (25.1.12 was booting fine).
Now, after a reboot the machine hangs right after the microcode is reinstalled with "Reloading firmware configuration." I can force a reboot but am in an intermediate state (kernel 14.3, but still Opnsense 25.1.12)
Uninstall microcode, upgrade, reinstall microcode. Had the same issue. (Intel)
Quote from: CP-Geek on July 23, 2025, 06:34:20 PMUninstall microcode, upgrade, reinstall microcode. Had the same issue. (Intel)
That did it, thanks!
Quote from: JailYard on July 23, 2025, 04:22:18 PMI've had a few issues.
First, I needed to change UEFI settings to legacy in BIOS, otherwise the router hung on reboot (25.1.12 was booting fine).
Same issue here except my box doesn't have legacy boot capability.
Guess I am stuck on 25.1.12 until I'm ready to do a fresh install.. not sure why this update isn't UEFI compatible
Quote from: JailYard on July 23, 2025, 07:32:49 PMQuote from: CP-Geek on July 23, 2025, 06:34:20 PMUninstall microcode, upgrade, reinstall microcode. Had the same issue. (Intel)
That did it, thanks!
Same here as well.