Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Errors when checking for package updates.

    Scheduled Pinned Locked Moved General pfSense Questions
    updates
    42 Posts 10 Posters 11.6k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • stephenw10S
      stephenw10 Netgate Administrator
      last edited by

      Hmm, when you see it does running pfSense-upgrade -c resolve it?

      1 Reply Last reply Reply Quote 0
      • GiaNNG
        GiaNN
        last edited by GiaNN

        I'm having also the same problem on PFsense+.
        I tried pkg update and it gives me this:

        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-pkg01.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-pkg01.atx.netgate.com/pfSense_plus-v23_05_amd64-pfSense_plus_v23_05/packagesite.pkg: Bad Request
pkg: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_05_amd64-pfSense_plus_v23_05/packagesite.txz: Bad Request
Unable to update repository pfSense
Error updating repositories!

        pfSense-upgrade -c doesn't solve it, idk what to do.

        doing pfSense-upgrade -dc gives me this:

        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-pkg01.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-pkg01.atx.netgate.com/pfSense_plus-v23_05_amd64-pfSense_plus_v23_05/packagesite.pkg: Bad Request
pkg-static: https://pfsense-plus-pkg01.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

        My DNS works, if i ping google.com it gives a correct IPv6 and pings it

        GiaNNG 1 Reply Last reply Reply Quote 0
        • GiaNNG
          GiaNN @GiaNN
          last edited by GiaNN

          @GiaNN I solved it, idk why the repo was 23.05, while i had 23.01 telling me was up to date.
          I went to updates -> previous branch 23.01 instead of current stable version 23.05

          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            Hmm, odd. It should still have been able to pull a valid cert for 23.05, the cert is the same. Were you using 23.05-beta/RC at any time? That could have introduced an invalid signature file. Possibly.

            GiaNNG 1 Reply Last reply Reply Quote 0
            • GiaNNG
              GiaNN @stephenw10
              last edited by

              @stephenw10 no, never used beta. I had some cert problems when i switched from CE to plus version and had to contact the support which in 1 min manually solved it, if it can help.

              1 Reply Last reply Reply Quote 0
              • stephenw10S
                stephenw10 Netgate Administrator
                last edited by

                Hmm, weird. Well, reach out if you have any issues upgrading to 23.05.

                GiaNNG 1 Reply Last reply Reply Quote 0
                • GiaNNG
                  GiaNN @stephenw10
                  last edited by

                  @stephenw10 consider that i didn't know of the update... My dashboard always told me it's up to date.
                  45a4ff76-1b43-4ef6-a5e5-5e6ee2d9ff1b-immagine.png

                  S 1 Reply Last reply Reply Quote 0
                  • S
                    SteveITS Galactic Empire @GiaNN
                    last edited by

                    @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.

                    Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                    When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
                    Upvote 👍 helpful posts!

                    GiaNNG 1 Reply Last reply Reply Quote 0
                    • GiaNNG
                      GiaNN @SteveITS
                      last edited by

                      @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.

                      S 1 Reply Last reply Reply Quote 0
                      • stephenw10S
                        stephenw10 Netgate Administrator
                        last edited by

                        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

                        1 Reply Last reply Reply Quote 0
                        • S
                          SteveITS Galactic Empire @GiaNN
                          last edited by

                          @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.

                          Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                          When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
                          Upvote 👍 helpful posts!

                          1 Reply Last reply Reply Quote 0
                          • stephenw10S
                            stephenw10 Netgate Administrator
                            last edited by

                            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.

                            S johnpozJ 2 Replies Last reply Reply Quote 0
                            • S
                              scuderia09 @stephenw10
                              last edited by

                              @stephenw10

                              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
                              S 1 Reply Last reply Reply Quote 0
                              • S
                                scuderia09 @scuderia09
                                last edited by

                                @scuderia09

                                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.

                                1 Reply Last reply Reply Quote 1
                                • johnpozJ
                                  johnpoz LAYER 8 Global Moderator @stephenw10
                                  last edited by

                                  @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.

                                  An intelligent man is sometimes forced to be drunk to spend time with his fools
                                  If you get confused: Listen to the Music Play
                                  Please don't Chat/PM me for help, unless mod related
                                  SG-4860 24.11 | Lab VMs 2.8, 24.11

                                  1 Reply Last reply Reply Quote 0
                                  • stephenw10S
                                    stephenw10 Netgate Administrator
                                    last edited by

                                    Hmm, that is odd if it was already on 23.05. Same 'Bad Request' error?

                                    johnpozJ 1 Reply Last reply Reply Quote 0
                                    • johnpozJ
                                      johnpoz LAYER 8 Global Moderator @stephenw10
                                      last edited by johnpoz

                                      @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:

                                      An intelligent man is sometimes forced to be drunk to spend time with his fools
                                      If you get confused: Listen to the Music Play
                                      Please don't Chat/PM me for help, unless mod related
                                      SG-4860 24.11 | Lab VMs 2.8, 24.11

                                      1 Reply Last reply Reply Quote 0
                                      • S
                                        SwissSteph
                                        last edited by SwissSteph

                                        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?_=1687174518657

                                        By income since, I hope that it is indeed solved definitively

                                        I started with two "no-name" pfsense, one for use at home and the other as a backup in case of problems (which can happen when you're new to pfsense).
                                        ... And now I'm living with a Netgate 8200
                                        ... And sorry for my bad English...

                                        1 Reply Last reply Reply Quote 0
                                        • stephenw10S
                                          stephenw10 Netgate Administrator
                                          last edited by

                                          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 -c to do that.

                                          1 Reply Last reply Reply Quote 0
                                          • S
                                            SwissSteph
                                            last edited by

                                            @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 :-)

                                            I started with two "no-name" pfsense, one for use at home and the other as a backup in case of problems (which can happen when you're new to pfsense).
                                            ... And now I'm living with a Netgate 8200
                                            ... And sorry for my bad English...

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.