Errors when checking for package updates.
-
@stephenw10 consider that i didn't know of the update... My dashboard always told me it's up to date.
-
@GiaNN said in Errors when checking for package updates.:
@stephenw10 consider that i didn't know of the update... My dashboard always told me it's up to date.
It seems like there's a path there somehow where it's not succeeding the update check but not showing an error. I posted in another thread but the first time I tried updating from 23.01 to 23.05 on my 2100 at home it showed a cert error. I backed off because it was release day. The next night it showed 23.01 was current. I went to Update Settings which was still set to Current branch, saved it without changing anything, after which the update to 23.05 was then detected and installed fine. I believe I've seen a few similar posts.
-
@SteveITS i don't know, now i just updated, i had to change the repo from 23.01 to 23.05 and back a couple of times, then it said that there was an update available and i updated.
-
Yes, showing it's up to date when it should show 'Unable to check for updates' seems like a regression. It was solved previously: https://redmine.pfsense.org/issues/8870
-
@GiaNN Yes that's the recommended solution for upgrade not offered. I am not sure why I just saved without changing it, but I did. :) That may be a clue though since it also worked.
-
Part of that is a known bug we're working on. The stored repo path in the config becomes invalid but it's not obvious because the gui only shows the current valid repos with the default selected when that happens. Switching repos or saving the current repo updates the config with a currently valid setting.
-
Same issue here with a 23.01 stuck upgrade on a 6100. Flipping around the stable/prev channels in the GUI don't make a difference.
[23.01-RELEASE][x@pfsense]/: pfSense-upgrade -cd Messages: Your Netgate device has pfSense+ as part of your device purchase. ERROR: It was not possible to determine pkg remote version >>> Updating repositories metadata... Updating pfSense-core repository catalogue... pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_amd64-core/meta.txz: Bad Request repository pfSense-core has no meta file, using default settings pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_amd64-core/packagesite.pkg: Bad Request pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_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_amd64-pfSense_plus_v23_05/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_amd64-pfSense_plus_v23_05/packagesite.pkg: Bad Request pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_amd64-pfSense_plus_v23_05/packagesite.txz: Bad Request Unable to update repository pfSense Error updating repositories! 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 -
actually... giving up and letting it sit overnight after setting to 23.05 channel finally presented an upgrade option in GUI and that worked out.
-
@stephenw10 said in Errors when checking for package updates.:
Part of that is a known bug we're working on.
I ran into this yesterday, I just went in and hit save on the update page selecting 23.05 which I am on.. And then it worked.. I have been on 23.05 for a while now.. It was odd.
-
Hmm, that is odd if it was already on 23.05. Same 'Bad Request' error?
-
@stephenw10 said in Errors when checking for package updates.:
Same 'Bad Request' error?
yup
here it was still in my ssh history, just had to scroll up
[23.05-RELEASE][admin@sg4860.local.lan]/root: pkg update Updating pfSense-core repository catalogue... pkg: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_05_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_05_amd64-core/packagesite.pkg: Bad Request pkg: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_05_amd64-core/packagesite.txz: Bad Request Unable to update repository pfSense-core Updating pfSense repository catalogue... pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_amd64-pfSense_plus_v23_05/meta.txz: Bad Request repository pfSense has no meta file, using default settings pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_amd64-pfSense_plus_v23_05/packagesite.pkg: Bad Request pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_amd64-pfSense_plus_v23_05/packagesite.txz: Bad Request Unable to update repository pfSense Error updating repositories! [23.05-RELEASE][admin@sg4860.local.lan]/root: pkg update Updating pfSense-core repository catalogue... pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_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-v23_05_amd64-core/packagesite.pkg: Bad Request pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_amd64-core/packagesite.txz: Bad Request Unable to update repository pfSense-core Updating pfSense repository catalogue... pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_amd64-pfSense_plus_v23_05/meta.txz: Bad Request repository pfSense has no meta file, using default settings pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_amd64-pfSense_plus_v23_05/packagesite.pkg: Bad Request pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_amd64-pfSense_plus_v23_05/packagesite.txz: Bad Request Unable to update repository pfSense Error updating repositories! [23.05-RELEASE][admin@sg4860.local.lan]/root:Then you can see where I logged into the gui, did the update save thing.. and then it worked
[23.05-RELEASE][admin@sg4860.local.lan]/root: Message from syslogd@sg4860 at Jun 17 16:40:31 ... php-fpm[433]: /index.php: Successful login for user 'admin' from: 192.168.9.100 (Local Database) https://pfsense-plus-pkg00.atx.netgate.croot: pkg update 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. [23.05-RELEASE][admin@sg4860.local.lan]/root: -
Same problem two days ago on my 8200 and Netgate support asked me to do "pfSense-upgrade -d -c" which solved the problem.
https://forum.netgate.com/topic/180888/solved-help-sudo-pkg-upgrade-in-netgate-8200-bad-request?_=1687174518657By income since, I hope that it is indeed solved definitively
-
Ah yes, if you are just checking directly at the CLI it's probably just that the user cert has expired. When you check in the gui it automatically pulls a new cert before checking. At the CLI you can
pfSense-upgrade -cto do that. -
@stephenw10 said in Errors when checking for package updates.:
pfSense-upgrade -c
It's amazing, because I got the same error messages again and by running "pfSense-upgrade -c" (from the GUI) I fixed the problem again -> no more error message.
Would it be possible to give me an explanation of "why this phenomenon comes back" and how to prevent it?
I'd like to understand where I'm going wrong.
Thanks for your comments :-)
-
In order to access the pkg repos clients must have a valid client cert. To get the cert clients reach out to the backend system, are validated and given a cert with a short lifetime.
If you login to the cli and try to access the pkg system directly it will fail with the 'bad request' if the client cert has expired. Usually you will not see that via the gui because any of the pkg functions accessed that way renew the cert before hand.
At the CLI you can run pfSense-upgrade or pfSense-repoc to update the cert.
Steve
-
Hello Steve,
Thank you for your reply. My English is not at all OK, can you just tell me what the abbrevatioon "CLI" means?
Sorry for the stupid question, then I'll be able to understand your answer much better :-)
Steph -
Sorry it's Command Line Interface. So when working at the command line directly.
-
Thanks for the clarification ;-)
I usually type the command "pkg update or pkg upgrade" in the GUI to see if there is anything to update.
And if the answer shows it, indiquand to press "Y", as I can't do it in the GUI (I don't know how it's possible) I launch an SSh and then answer with "Y" once "pkg upgrade" is launched.
That's why I saw (in the GUI) these error messages, then ran "pfSense-upgrade -c" and then "pkg upgrade" to check that I no longer had the error message.
In the end, what's the best method, because in the GUI I get the error message, but if I run the same command from SSh, will I also get these errors? That's what I'm having trouble understanding.
-
The best method to check for updates from the gui?
Just refresh the system widget on the dashboard.
-
Thanks for the tip ;-)
My "problem" is that I put the script that is suggested in https://forum.netgate.com/topic/179402/pfblockerng-3-2-0_4/10?_=1681407650676 and I no longer receive mail if my pfsense is in error as mentioned here.
So I'm going to have to deal with this "problem" and have my script work only once in a while.
Thanks again for your help and advice!
