Package update fails

vcr58

I have a notification that says

Upgrade
check_upgrade: "Updating repositories metadata" returned error code 1 @ 2026-08-12 22:49:54

There were 2 packages available to upgrade (acme and Backup) but the upgrade failed on both of them. For acme this was the result

>>> Upgrading pfSense-pkg-acme...
Updating pfSense-core repository catalogue...
repository pfSense-core has no meta file, using default settings
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
repository pfSense has no meta file, using default settings
Unable to update repository pfSense
Error updating repositories!
Failed

I uninstalled the Backup package succesfully but when I tried to re-install it failed. The acme package is at 1.2 and wants to upgrade to 1.3. Obviously, I will not try to uninstall and re-install acme.

pfsense version is...

26.03.1-RELEASE (amd64)
built on Wed May 20 10:19:00 CDT 2026
FreeBSD 16.0-CURRENT

System Register inicates that everything is fine and my device is recognized. Hardware is unchanged.

Please help :)

patient0

@vcr58 maybe the same issue as other:

https://forum.netgate.com/topic/201113/pfsense-update-issues/
https://forum.netgate.com/topic/201115/pfsense-warning-your-device-has-not-registred-for-pfsense/
https://forum.netgate.com/topic/201114/pfsense-plus-invalidated-subscription

There is a backend issue where devices with a homelab plus license show up as not registered. Should be fixed soon.

vcr58

@patient0 Thanks for the reply! I'll check tomorrow.

Gradius

Can confirm.

Getting those errors too:

[26.03.1-RELEASE][admin@pfSense.home.arpa]/: pkg update -f
Updating pfSense-core repository catalogue...
pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v26_03_1_amd64-core/meta.txz: Bad Request
repository pfSense-core has no meta file, using default settings
pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v26_03_1_amd64-core/data.pkg: Bad Request
pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v26_03_1_amd64-core/data.tzst: Bad Request
pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v26_03_1_amd64-core/packagesite.pkg: Bad Request
pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v26_03_1_amd64-core/packagesite.tzst: Bad Request
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v26_03_1_amd64-pfSense_plus_v26_03_1/meta.txz: Bad Request
repository pfSense has no meta file, using default settings
pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v26_03_1_amd64-pfSense_plus_v26_03_1/data.pkg: Bad Request
pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v26_03_1_amd64-pfSense_plus_v26_03_1/data.tzst: Bad Request
pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v26_03_1_amd64-pfSense_plus_v26_03_1/packagesite.pkg: Bad Request
pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v26_03_1_amd64-pfSense_plus_v26_03_1/packagesite.tzst: Bad Request
Unable to update repository pfSense
Error updating repositories!

Waiting for the fix.

stephenw10

Yup if you have an install that was upgraded to Plus on a Home/Lab license it will be unable to access the repos temporarily. Should be restored later today.

Gradius

@stephenw10 Sadly, it was still not fixed:

check_upgrade: "Updating repositories metadata" returned error code 1 @ 2026-08-18 06:03:10

Gertjan

@Gradius said in Package update fails:

Getting those errors too:

[26.03.1-RELEASE][admin@pfSense.home.arpa]/: pkg update -f
Updating pfSense-core repository catalogue...
pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v26_03_1_amd64-core/meta.txz: Bad Request
repository pfSense-core has no meta file, using default settings
pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v26_03_1_amd64-core/data.pkg: Bad Request
pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v26_03_1_amd64-core/data.tzst: Bad Request

#metoo : a simple "pkg update" yields the same results.
edit : using 26.07.

@stephenw10 said in Package update fails:

if you have an install that was upgraded to Plus on a Home/Lab license it will

For me : it's a 4100, never had anything else as Plus on it, 26.03.1 before, and since a week 26.07.

That said, the GUI part works fine, both the packet manager and system updater. No issues are shown.

I will check later on.

stephenw10

Bad request like that usually implies the client cert is expired or missing. That implies that repoc has not run recently. It is run by the backend when you open the GUI so that's likely why it works.

From 26.03.1 though at the gui run: pfSense-repoc -N then check pkg -d update

If it sill shows errors send me the NDI in chat and I'll check it. A 4100 should always have access though.