Unable to update repository pfsense
-
Hello,
Since updating to the 23.01 release, when I attempt to update the package repository via SSH, I receive the series of messages below:
Updating pfSense-core repository catalogue... pkg: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_amd64-core/meta.txz: Bad Request repository pfSense-core has no meta file, using default settings pkg: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_amd64-core/packagesite.pkg: Bad Request pkg: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_amd64-core/packagesite.txz: Bad Request Unable to update repository pfSense-core Updating pfSense repository catalogue... pkg: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01/meta.txz: Bad Request repository pfSense has no meta file, using default settings pkg: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01/packagesite.pkg: Bad Request pkg: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01/packagesite.txz: Bad Request Unable to update repository pfSense Error updating repositories!This is not an issue I have had with any earlier releases of pfSense (e.g., 22.05) with the same config, and all other functions from the router and the network behind it work as expected. One additional behavior that may mean something is that if, after receiving the error above, I login to the web UI where the dashboard does an update check, suddenly doing a pkg update via SSH then completes normally. Issuing the command continues working normally after logging out of the web UI, at least until some undetermined event or time passes until it begins producing an error again.
Not a massive obstacle, but an annoying one. Any help is appreciated. Thanks!
-
@mixleplix Take a look at https://forum.netgate.com/topic/177882/package-list-empty
-
@steveits Thanks for the pointer. I just now tried the command, pfSense-upgrade -c. Since then, the error I was getting has not returned. Of course, the error would temporarily go away previously, but hopefully this will solve it permanently. Fingers crossed.