23.05.1 - Cannot update packages or repositories - "Old pfSense Plus version detected." and pkg-static "Bad Request"

doxthefox

Hey Folks,

Like a few other posts on here and reddit, I've upgraded to 23.05.1 a while ago and while I did have some issues with the update, I was able to fix them by the toggling the UI Update branch from the previous version to 23.05.01, and I was able to update successfully after that.

Yesterday I swapped a NIC card, and following a similar thread (and an accompanying post on reddit) I requested a new Lab/Home token and installed it, hoping this would resolve my issue.

No matter what I do, when I try to upgrade my package repo I get the following error:

pkg-static clean -ay ; pkg-static install -fy pkg pfSense-repo pfSense-upgrade
pkg-static: Repository pfSense-core missing. 'pkg update' required
pkg-static: No package database installed.  Nothing to do!
Updating pfSense-core repository catalogue...
pkg-static: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_05_1_amd64-core/meta.txz: Bad Request
repository pfSense-core has no meta file, using default settings
pkg-static: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_05_1_amd64-core/packagesite.pkg: Bad Request
pkg-static: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_05_1_amd64-core/packagesite.txz: Bad Request
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_1_amd64-pfSense_plus_v23_05_1/meta.txz: Bad Request
repository pfSense has no meta file, using default settings
pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_1_amd64-pfSense_plus_v23_05_1/packagesite.pkg: Bad Request
pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_1_amd64-pfSense_plus_v23_05_1/packagesite.txz: Bad Request
Unable to update repository pfSense
Error updating repositories!

[23.05.1-RELEASE][admin@<redacted>]/root: pfSense-upgrade -c                                                    
Old pfSense Plus version detected.
Exiting without fetching the dynamic repo settings.
ERROR: It was not possible to determine pkg remote version
>>> Updating repositories metadata... failed.
ERROR: It was not possible to determine pfSense remote version
ERROR: It was not possible to determine pfSense-base remote version
ERROR: It was not possible to determine pfSense-kernel-pfSense remote version
Your system is up to date

Things I've done so far:

Togging via UI from the previous stable branch to the current 23.05.1.
Requested and installed new token after the NIC swap
Tried to clean the repos, delete any custom repo files (they did not exist), and request new a new repo cert/update.

Any advice on what I try next? I'd like to be able to upgrade and/or install new packages. All other areas of PFSense functionality seem to fine.

I'm posting in this category as I believe this is related to my upgrade to 23.05.1, based on the output of "Old pfSense Plus version detected." when I try to run a repo cert update via "pfSense-upgrade -c". Please feel free to move this if this would be better suited for another categoy.

planedrop

My first thing to try would be to reboot several times, this solved it on a unit that I was having basically the same issues with (see here, not my thread but I commented near the bottom: https://forum.netgate.com/topic/178822/no-available-packages/59?_=1690606591968)

This resolved the problem for me after a hardware change (not NIC but CPIC card being added) since the NDI had changed.

doxthefox

@planedrop Thanks for the tips, I've tried a few times and still not seeing anything different.

When I try to update a package that is already installed, I also see this:

WARNING: Current pkg repository has a new PHP major
         version. pfSense should be upgraded before
         installing any new package.

Hoping this doesn't lead to a rebuild, but I may try that later today.

doxthefox

Just to close the loop on this, I suspect there was something related to my flaky upgrade that cause this.

I ended up doing a rebuild / fresh install and ported my config.xml over and this has resolved the issue.

planedrop

@doxthefox Glad it's working now, sometimes just doing a reinstall and restore from config is the easiest solution lol.