26.7 upgrade failure - openssl35-3.5.7 conflicts with openssl-3.0.21,1

[ubu]

Trying to upgrade opnsense to 26.7 but it fails. Here's the pastebin link
Can someone help me finish the update?

[newsense]

You cannot upgrade with the FreeBSD repos active.

[ubu]

can you explain what i need to do in order to upgrade please?

[Patrick M. Hausen]

Disable the FreeBSD repository/repositories. For this do the opposite of what you did to enable them. OPNsense never does this on its own.

Check /etc/pkg and /usr/local/etc/pkg/repos directories.

[ubu]

Disable the FreeBSD repository/repositories. For this do the opposite of what you did to enable them. OPNsense never does this on its own.

Check /etc/pkg and /usr/local/etc/pkg/repos directories.

i never enabled them. i've only ever done what I could right through the web gui. it appears they were added when I choose to install some plugins maybe? I just asked google and it said I have to disable them through the command line.

[Patrick M. Hausen]

Look in the directories I listed for files containing FreeBSD repositories set to "enabled". Change "enabled" to "disabled" with a text editor. If you are not familiar with the editor "vi" there is "ee", the "easy editor" as an alternative.

[franco]

Looks like a partial upgrade with base/kernel on 26.7 and packages still at 26.1.

Since FreeBSD renamed repositories they will pop up until the 26.7 core is installed.


Cheers,
Franco

[ubu]

i edited /etc/pkg/FreeBSD.conf, that was the only file in /etc/pkg/, i disabled the repository. Went to the webgui and did another update. I was staring at this screen
https://pastebin.com/41hUyBL3
and the Updates tab in System:Firmware had a spinning circle progress bar. I let it do that for about 10 minutes. then I hit refresh in my browser. Now when i go to System Firmware Status, its completely blank.. I don't know what to do. Can someone help please?
so

[dseven]

Others may have different opinions, but for me... if your system is broken and you don't know what caused it to get into that state, I wouldn't trust it going forward (you don't know the extent of the brokenness). I'd take a backup of your config, then do a fresh install of 26.7 and import the config from the backup.

[nero355]

I don't know what to do. Can someone help please?

Run the Health Check if possible and post the output here :)

[ubu]

all is working after I disabled the FreeBSD repo but my question would be why was it enabled in the first place and do I need to re-enable it now that 26.7.1 is installed and working?

[Patrick M. Hausen]

do I need to re-enable it

No. You should not have any third party repos enabled unless you know exactly what you are doing. And expect major upgrades to fail and manual intervention to be necessary if you do use them.

E.g. Zenarmor or AdGuard Home need extra repos. The best advice then is to postpone the OPNsense upgrade until the third party repos are updated, too.

The FreeBSD repo should never be active.

[ubu]

do I need to re-enable it

No. You should not have any third party repos enabled unless you know exactly what you are doing. And expect major upgrades to fail and manual intervention to be necessary if you do use them.

E.g. Zenarmor or AdGuard Home need extra repos. The best advice then is to postpone the OPNsense upgrade until the third party repos are updated, too.

The FreeBSD repo should never be active.

i wonder why it was active to begin with. I never enabled it. It must have enabled itself after installing some addons i'm guessing? My only question is now that i'm upgraded, will whatever package that enabled that repo become stagnant without a repo to keep it updated. below are the only plugings i have installed.

Code Select Expand

os-acme-client (installed)    4.16_1    821KiB    3    OPNsense    ACME Client   
os-cpu-microcode-amd (installed)    1.1_1    872B    3    OPNsense    AMD CPU microcode updates   
os-git-backup (installed)    1.1_3    14.8KiB    2    OPNsense    Track config changes using git   
os-isc-dhcp (installed)    1.0_6    284KiB    2    OPNsense    ISC DHCPv4/v6 server   
os-nut (installed)    1.9_1    55.4KiB    3    OPNsense    Network UPS Tools   
os-realtek-re (installed)    1.0    409B    3    OPNsense    Realtek re(4) vendor driver   
os-theme-rebellion (installed)    1.9.5    5.23MiB    3    OPNsense    A suitably dark theme   
os-upnp (installed)

[vplanida]

Hello. I'm here to one up the problem.
I have a really old install of a system. 4-5 years old opnsense install updated to a current (previous) release with all the plugins and firewall rules from way back when.

Tried to upgrade my system from 26.1.11_10 to 26.7 or 26.7.2 but nothing came back in 30 minutes after reboot. Went on and did the physical reboot.
Against all odds, the system booted up again and let me in the dashboard. In the dashboard it is said to be version 26.1.11_10.

Checking for updates in the dashboard does nothing. Updater told me that "pkg: Repository OPNsense has a wrong packagesite".
Google told me to "opnsense-update -p -A 26.7", which I did and came to an error brought up by this post.

Deleting the realtek 1.0 plugin moved things forward.
At some point console updater command saw horrors beyond human comprehention.

Code Select Expand

root@opn:~ # opnsense-update -p -A 26.7
Updating FreeBSD-ports repository catalogue...
FreeBSD-ports repository is up to date.
Updating FreeBSD-ports-kmods repository catalogue...
FreeBSD-ports-kmods repository is up to date.
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Updating FreeBSD-ports repository catalogue...
FreeBSD-ports repository is up to date.
Updating FreeBSD-ports-kmods repository catalogue...
FreeBSD-ports-kmods repository is up to date.
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date

After repeating the console command I managed to pull through with a dashboard update. 
But updater still was unable to do miracles. So I am doing what it said and came here to report on it.

https://pastebin.com/8rm6jLr2

At this point I'm probably going to do a clean reinstall when I get back to it. I just felt that I had to report on possible causes.