23.09.1 → 24.11: GUI Selects 24.11 but Active Repo Remains 23.09.1

DobbsRx

Documented Problem, testing results, and repairs completed:

pfSense Plus 23.09.1 on generic amd64 hardware.

EWS/repoc now successfully returns both 24.11 and 23.09.1 repository definitions.

The GUI allows selecting Previous Stable Version 24.11 and config.xml stores system/pkg_repo_conf_path as /usr/local/etc/pfSense/pkg/repos/pfSense-repo-24_11.conf, but that file does not exist.

pfSense-repoc generates numbered files instead: pfSense-repo-0000.conf is 24.11 and pfSense-repo-0001.conf is 23.09.1.

0001 has .default=1.

/usr/local/etc/pkg/repos/pfSense.conf is repeatedly regenerated pointing to pfSense-repo-0001.conf, so pkg-static -vv continues using 23.09.1 repositories and pfSense-upgrade -d -c reports the system is up to date.

I have already ran Netgate's documented package repair and now have the newer pfSense-repo/pfSense-repoc tooling installed on the 23.09.1 base.

Question:
What is the supported method to repair this repository mapping so the 24.11 repo becomes active before attempting the upgrade?

DobbsRx

Further update: The repository mapping subsequently corrected itself without any manual repository changes. At 18:32 /usr/local/etc/pkg/repos/pfSense.conf changed to point to /usr/local/etc/pfSense/pkg/repos/pfSense-repo-24_11.conf, and pkg-static -vv now confirms both active repositories are 24.11. The GUI consequently reports Current Base System 23.09.1 / Latest Base System 24.11 and offers the upgrade.

However, immediately afterward:

pfSense-upgrade -d -c

still fails with:

pfSense-repoc-static: failed to fetch the repo data

failed to read the repo data.

failed to update the repository settings!!!

So repo activation succeeded at least once, but pfSense-repoc-static remains intermittently unable to fetch repository data. I have not manually modified any repository files or symlinks.

patient0

@DobbsRx, is your license is a "Home or Lab Evaluation" license? If yes, check:

https://forum.netgate.com/topic/201172/the-2022-limited-time-pfsense-plus-promotion

DobbsRx

@patient0

Ah that’s disappointing, thanks for the information though.

patient0

@DobbsRx Sorry, I was not focused enough and wasn't writing it well: if you got a "Home or Lab Evaluation", you are good. If your license is a Home or Lab and your device shows as not registered, then send your NDI in a chat to @stephenw10. There was an issue with some of them where they show up falsely as unregistered.

On the other hand if you got a 2022 Limited Time pfSense+ license, that ran out.

DobbsRx

@patient0

Yes...pfSense Plus 23.09.1 installation originally obtained through the 2022 promotional CE→Plus entitlement. I have now purchased/activated a current pfSense Plus subscription. System → Update now correctly offers 24.11.

GUI upgrade initially reports “Another instance of pfSense-upgrade is running” despite no pfSense-upgrade/pkg/repoc processes, including immediately after reboot. Console option 13 proceeds further, successfully updates both package repository catalogs, then fails at:

pfSense-repoc-static: failed to fetch the repo data
failed to read the repo data.
failed to update the repository settings!!!

patient0

@DobbsRx posting more of the output you get may help. Otherwise go through the Netgate Troubleshoot again.

Does the system show your new registration infos in the GUI (System / Register), like the text "Your device does not require registration ..."?

stephenw10

Yup send me your NDI in chat and I'll check it.

DobbsRx

@patient0

My dashboard says:

Contract Type pfSense TAC Lite Zero to ping only

Support Start 2026-09-24
Support End 2027-09-24

Support Renewed N/A

Support Status ACTIVE

And System > Register says:

"Thank you for choosing Netgate pfSense Plus

Your device does not require registration, we recognize it already. You may have already registered, or it may be a pre-registered Netgate appliance."

stephenw10

That device has a current subscription, you should be able to upgrade. You're still seeing an error?

stephenw10

Try running: pfSense-repoc -D

What error is shown?

DobbsRx

@stephenw10 said in 23.09.1 → 24.11: GUI Selects 24.11 but Active Repo Remains 23.09.1:

pfSense-repoc -D

[23.09.1-RELEASE][root@pfSense.dobbs.arpa]/root: pfSense-repoc -D
OS: FreeBSD
OS Version: 14.0-CURRENT
Platform: amd64
Product: Netgate pfSense Plus
Version: 23.09.1-RELEASE
FS type: zfs
Language: en_US
Model: unknown hardware
NDI: ##################
Package prefix: pfSense-pkg-
Serial: (null)
Repo path: /usr/local/etc/pfSense
Request query: {"platform":"unknown hardware","os":"FreeBSD","osver":"14.0-CURRENT","prod":"Netgate pfSense Plus","ver":"23.09.1-RELEASE","ed":"Plus","fstype":"zfs","pkgs":"[{\"name\":\"acme\",\"ver\":\"0.8_1\"},{\"name\":\"ntopng\",\"ver\":\"0.8.13_10\"},{\"name\":\"WireGuard\",\"ver\":\"0.2.1\"},{\"name\":\"pfBlockerNG-devel\",\"ver\":\"3.2.0_8\"},{\"name\":\"ipsec-profile-wizard\",\"ver\":\"1.2\"},{\"name\":\"openvpn-client-export\",\"ver\":\"1.9.2\"}]"}
POST data: uid=###############&language=en_US&serial=&version=%7B%22platform%22%3A%22unknown+hardware%22%2C%22os%22%3A%22FreeBSD%22%2C%22osver%22%3A%2214.0-CURRENT%22%2C%22prod%22%3A%22Netgate+pfSense+Plus%22%2C%22ver%22%3A%2223.09.1-RELEASE%22%2C%22ed%22%3A%22Plus%22%2C%22fstype%22%3A%22zfs%22%2C%22pkgs%22%3A%22%5B%7B%5C%22name%5C%22%3A%5C%22acme%5C%22%2C%5C%22ver%5C%22%3A%5C%220.8_1%5C%22%7D%2C%7B%5C%22name%5C%22%3A%5C%22ntopng%5C%22%2C%5C%22ver%5C%22%3A%5C%220.8.13_10%5C%22%7D%2C%7B%5C%22name%5C%22%3A%5C%22WireGuard%5C%22%2C%5C%22ver%5C%22%3A%5C%220.2.1%5C%22%7D%2C%7B%5C%22name%5C%22%3A%5C%22pfBlockerNG-devel%5C%22%2C%5C%22ver%5C%22%3A%5C%223.2.0_8%5C%22%7D%2C%7B%5C%22name%5C%22%3A%5C%22ipsec-profile-wizard%5C%22%2C%5C%22ver%5C%22%3A%5C%221.2%5C%22%7D%2C%7B%5C%22name%5C%22%3A%5C%22openvpn-client-export%5C%22%2C%5C%22ver%5C%22%3A%5C%221.9.2%5C%22%7D%5D%22%7D&arch=amd64
pfSense-repoc: failed to fetch the repo data
failed to read the repo data.

DobbsRx

@stephenw10

I went back through the troubleshooting steps

pkg-static clean -ay
pkg-static install -fy pkg
pkg-static install -xfy pfSense-repo pfSense-upgrade

then rebooted, and the update screen still shows that I am up to date with no update available and pfsense repoc -D continues to show failed to fetch and read the repo data

stephenw10

Hmm, those pkg commands completed without error though?

DobbsRx

@stephenw10

correct no errors.

[23.09.1-RELEASE][root@pfSense.dobbs.arpa]/root: pkg-static clean -ay
The following package files will be deleted:
        /var/cache/pkg/pfSense-repoc-20241121.pkg
        /var/cache/pkg/pfSense-repo-24.11.pkg
        /var/cache/pkg/pkg-1.21.3_4.pkg
        /var/cache/pkg/libucl-0.9.2_1~57dcb4b376.pkg
        /var/cache/pkg/pfSense-repoc-20241121~ed8e24c0f3.pkg
        /var/cache/pkg/uclcmd-0.2.20211204.pkg
        /var/cache/pkg/pfSense-upgrade-1.2.2_1~671d6278ee.pkg
        /var/cache/pkg/pkg-1.21.3_4~6f8d20d904.pkg
        /var/cache/pkg/pfSense-repo-24.11~3471504e31.pkg
        /var/cache/pkg/pfSense-upgrade-1.2.31.pkg
        /var/cache/pkg/uclcmd-0.2.20211204~9eaf3e37ef.pkg
        /var/cache/pkg/pfSense-upgrade-1.2.31~f60de66752.pkg
        /var/cache/pkg/libucl-0.9.2_1.pkg
        /var/cache/pkg/pfSense-upgrade-1.2.2_1.pkg
The cleanup will free 18 MiB
Deleting files: 100%
[23.09.1-RELEASE][root@pfSense.dobbs.arpa]/root: pkg-static install -fy pkg
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be REINSTALLED:
        pkg-1.21.3_4 [pfSense]

Number of packages to be reinstalled: 1

12 MiB to be downloaded.
[1/1] Fetching pkg-1.21.3_4.pkg: 100%   12 MiB  12.1MB/s    00:01    
Checking integrity... done (0 conflicting)
[1/1] Reinstalling pkg-1.21.3_4...
[1/1] Extracting pkg-1.21.3_4: 100%
Scanning /usr/share/certs/untrusted for certificates...
Scanning /usr/share/certs/trusted for certificates...
Skipping untrusted certificate /usr/share/certs/trusted/Cybertrust_Global_Root.pem (/etc/ssl/untrusted/76cb8f92.0)
Skipping untrusted certificate /usr/share/certs/trusted/DST_Root_CA_X3.pem (/etc/ssl/untrusted/2e5ac55d.0)
Skipping untrusted certificate /usr/share/certs/trusted/GlobalSign_Root_CA_-_R2.pem (/etc/ssl/untrusted/4a6481c9.0)
Skipping untrusted certificate /usr/share/certs/trusted/Hellenic_Academic_and_Research_Institutions_RootCA_2011.pem (/etc/ssl/untrusted/1636090b.0)
Skipping untrusted certificate /usr/share/certs/trusted/Network_Solutions_Certificate_Authority.pem (/etc/ssl/untrusted/4304c5e5.0)
Skipping untrusted certificate /usr/share/certs/trusted/Staat_der_Nederlanden_EV_Root_CA.pem (/etc/ssl/untrusted/03179a64.0)
Skipping untrusted certificate /usr/share/certs/trusted/TrustCor_ECA-1.pem (/etc/ssl/untrusted/7aaf71c0.0)
Skipping untrusted certificate /usr/share/certs/trusted/TrustCor_RootCert_CA-1.pem (/etc/ssl/untrusted/5d3033c5.0)
Skipping untrusted certificate /usr/share/certs/trusted/TrustCor_RootCert_CA-2.pem (/etc/ssl/untrusted/3e44d2f7.0)
Scanning /usr/local/share/certs for certificates...
You may need to manually remove /usr/local/etc/pkg.conf if it is no longer needed.
[23.09.1-RELEASE][root@pfSense.dobbs.arpa]/root: pkg-static install -xfy pfSense-repo pfSense-upgrade
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
The following 3 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
        pfSense-upgrade: 1.2.2_1 -> 1.2.31 [pfSense]

Installed packages to be REINSTALLED:
        pfSense-repo-24.11 [pfSense]
        pfSense-repoc-20241121 [pfSense]

Number of packages to be upgraded: 1
Number of packages to be reinstalled: 2

6 MiB to be downloaded.
[1/3] Fetching pfSense-repo-24.11.pkg: 100%    6 KiB   6.0kB/s    00:01    
[2/3] Fetching pfSense-upgrade-1.2.31.pkg: 100%   27 KiB  28.1kB/s    00:01    
[3/3] Fetching pfSense-repoc-20241121.pkg: 100%    6 MiB   6.5MB/s    00:01    
Checking integrity... done (0 conflicting)
[1/3] Reinstalling pfSense-repoc-20241121...
[1/3] Extracting pfSense-repoc-20241121: 100%
[2/3] Reinstalling pfSense-repo-24.11...
[2/3] Extracting pfSense-repo-24.11: 100%
[3/3] Upgrading pfSense-upgrade from 1.2.2_1 to 1.2.31...
[3/3] Extracting pfSense-upgrade-1.2.31: 100%

stephenw10

Hmm, so it appears to have the 24.11 repo configured already. I assume pfSense-upgrade -d still fails with errors?

stephenw10

24.11 is still ancient you could just reinstall to 26.07 directly. Your NDI will be valid in the installer.

DobbsRx

@stephenw10

Thanks. Since this is currently 23.09.1 on ZFS, are you recommending a clean install of 26.07 using the installer's Configuration Restore to recover the existing config from disk? And is a direct restore of the complete 23.09.1 config to 26.07 supported/recommended in this case?

stephenw10

Yes I would do that. Though I would also be sure to have a local backup too!

Yes the config from 23.09.1 will import directly into 26.07 either during the install or after.

It should be pretty seamless.

DobbsRx

@stephenw10

Done and done thanks for the help. Successfully updated to 26.07 with everything imported appropriately! Only issue was figuring out why dpinger was unhappy and not wanting to work and finding a stale VIP causing the issue.

edit: and this hint.acpi_spmc.0.disabled=1 kernel panic I just fixed as well lol