Hi,
Currently I'm using OPNsense Community Edition (24.7_5) and I'm trying to upgrade to the Business Edition - I'm getting this error message:
The matching OPNsense 24.10 series does not yet exist. Images are available to switch this installation to the latest business edition.
Well, yes. You can't upgrade to 24.10 yet because it will be released in October. Not sure if you just set up the installation or you came from 24.1.x...
You need to reinstall with a 24.4 image, but I would recommend using a backup of your last 24.1.x configuration.
Cheers,
Franco
Hello Jimp, Hello Franco,
coming from OPNsense 24.7.4_1-amd64, i got the same Message, while trying to switch to business.
Is it possible to stay at the current version and wait until October and then trying to switch?
Best Regards
Wolfgang
I am a business licensee as well.
I moved to the latest community version twice so far.
when openssl was on the unsupported version. and now when freebsd is unsupported. I will move back to business in October as Franco states.
the process is so easy. just backup your configuration before hand. and have a known usb drive with a working version of opnsense just in case
Hi Wolfgang,
> Is it possible to stay at the current version and wait until October and then trying to switch?
Yes, that works too.
Cheers,
Franco
It's October now, I'm on 24.10_1 business..
The matching OPNsense 24.10 series does not yet exist. Images are available to switch this installation to the latest business edition.
Can you provide more context like the check for updates log? Obviously 24.10 exists also because you already have it...
Cheers,
Franco
Thank you, here's the update log..
***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 24.10_1 at Wed Oct 30 14:17:37 UTC 2024
Fetching subscription information, please wait... done
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. 856 packages processed.
Updating repo-mihak repository catalogue...
No CRL was provided for /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=repo.mihak.link
No CRL was provided for /C=US/O=DigiCert Inc/CN=DigiCert TLS RSA SHA256 2020 CA1
No CRL was provided for /C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert Global Root CA
Fetching meta.conf: . done
No CRL was provided for /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=repo.mihak.link
No CRL was provided for /C=US/O=DigiCert Inc/CN=DigiCert TLS RSA SHA256 2020 CA1
No CRL was provided for /C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert Global Root CA
Fetching packagesite.pkg: ... done
Processing entries:
pkg: wrong architecture: FreeBSD:13:amd64 instead of FreeBSD:14:amd64
pkg: repository repo-mihak contains packages with wrong ABI: FreeBSD:13:amd64
Processing entries... done
Unable to update repository repo-mihak
Error updating repositories!
Checking integrity... done (0 conflicting)
Your packages are up to date.
***DONE***
Congratulations, here is your issue:
pkg: wrong architecture: FreeBSD:13:amd64 instead of FreeBSD:14:amd64
pkg: repository repo-mihak contains packages with wrong ABI: FreeBSD:13:amd64
It's an ill-maintained third party repository.
Cheers,
Franco
@franco: ok, it's an ill-maintained third-party repository. And so what? I've got the same problem than mahagen. As a result, I can't install new plugins, for example. I've got a 3-year business edition. How do I fix this issue? Thank you.
Quote from: fpeyram on March 14, 2025, 09:33:51 PM@franco: ok, it's an ill-maintained third-party repository. And so what? I've got the same problem than mahagen. As a result, I can't install new plugins, for example. I've got a 3-year business edition. How do I fix this issue? Thank you.
If you have added a third-party repo (https://repo.mihak.link/ was the one mentioned ) then best remove it and run the update check again. And let the maintainer of that repo know that you like updated packages.
Quote from: fpeyram on March 14, 2025, 09:33:51 PM@franco: ok, it's an ill-maintained third-party repository. And so what?
Keeping it will break your OPNsense, BE or CE.
Removing the repo will not suffice. The damage is already done.
You can try chasing down and removing all the non-OPNsense packages, but the only sane option is to install fresh and import the config - without that repo added.
> And so what?
We're making sure upgrades work, but this does not extend to third party repositories, because we do not offer them to anyone. I hope this is clear now.
Cheers,
Franco