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 9.4k 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.
    • gnitingG
      gniting
      last edited by

      From time to time I run into the following errors when trying to update the packages on my pfsense box. If, after the errors stop, I run the same command again, it works just fine.

      Any hints? I am running pfsense version: 23.01-RELEASE (amd64)

      ❯ pkg update ; pkg upgrade
Updating pfSense-core repository catalogue...
repository pfSense-core has no meta file, using default settings
pkg: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_amd64-core/meta.txz: Bad Request
pkg: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_amd64-core/packagesite.pkg: 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-core/packagesite.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/meta.txz: Bad Request
pkg: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01/packagesite.pkg: Bad Request
Unable to update repository pfSense
Error updating repositories!
pkg: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01/packagesite.txz: Bad Request
Updating pfSense-core repository catalogue...
repository pfSense-core has no meta file, using default settings
pkg: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_amd64-core/meta.txz: Bad Request
pkg: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_amd64-core/packagesite.pkg: 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-core/packagesite.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/meta.txz: Bad Request
pkg: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01/packagesite.pkg: Bad Request
Unable to update repository pfSense
Error updating repositories!
pkg: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01/packagesite.txz: Bad Request
      1 Reply Last reply Reply Quote 0
      • gnitingG
        gniting
        last edited by

        Here is the output of the same command, run a few seconds later:

        ❯ pkg update ; pkg upgrade
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.
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.
Checking for upgrades (0 candidates): 100%
Processing candidates (0 candidates): 100%
Checking integrity... done (0 conflicting)
Your packages are up to date.
        1 Reply Last reply Reply Quote 0
        • stephenw10S
          stephenw10 Netgate Administrator
          last edited by

          The bad request error implies the client cert has expired. If you're only connecting from the command line try running pfSense-upgrade -c first. That will pull a new cert.
          Otherwise thge update check on the dashboard when you first connect will also update it.

          gnitingG 1 Reply Last reply Reply Quote 0
          • gnitingG
            gniting @stephenw10
            last edited by gniting

            @stephenw10 said in Errors when checking for package updates.:

            The bad request error implies the client cert has expired. If you're only connecting from the command line try running pfSense-upgrade -c first. That will pull a new cert.
            Otherwise thge update check on the dashboard when you first connect will also update it.

            @stephenw10 Thanks for the hint. Tried it, here's what I saw:

            ❯ pfSense-upgrade -c
ERROR: It was not possible to determine pkg remote version
>>> Updating repositories metadata... done.
Your system is up to date
❯ pfSense-upgrade -c
>>> Updating repositories metadata... done.
Your system is up to date
❯

            I will let this be for another day or so and try the command line version for the update again. Maybe now, after trying your suggestion, the potential cert related issue is fixed in the background.

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

              Ok, that output looks good, as expected.

              You can also run pfSense-upgrade -dc to get more diagnostic output there if it does start failing again.

              Steve

              J 1 Reply Last reply Reply Quote 0
              • J
                johnwcahill @stephenw10
                last edited by johnwcahill

                @stephenw10

                I am having a similar problem today, I upgraded from 2.6.0 to pfsense+, upgrade went well and today when I went to look at packages nothing there. shell shows the same as the OP, however running pfSense-upgrade -dc is not pulling any cert that I can tell.

                If I use a browser to test, the certificate looks to be signed by you guys, however the browser also shows "
                400 Bad Request
                No required SSL certificate was sent

                "

                 pfSense-upgrade -dc
ERROR: It was not possible to determine pkg remote version
>>> Updating repositories metadata...
Updating pfSense-core repository catalogue...
pkg-static: 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-static: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_amd64-core/packagesite.pkg: Bad Request
pkg-static: 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-static: https://pfsense-plus-pkg00.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-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01/packagesite.pkg: Bad Request
pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01/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

                John

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

                  Please send me your NDI in chat and I'll check it.

                  1 Reply Last reply Reply Quote 0
                  • gnitingG
                    gniting
                    last edited by

                    @stephenw10 unfortunately, my problem is back. Ran the same old update command today and the errors are back.

                    Updating pfSense-core repository catalogue...
repository pfSense-core has no meta file, using default settings
pkg: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_amd64-core/meta.txz: Bad Request
pkg: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_amd64-core/packagesite.pkg: 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-core/packagesite.txz: Bad Request
repository pfSense has no meta file, using default settings
pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01/meta.txz: Bad Request
pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01/packagesite.pkg: Bad Request
Unable to update repository pfSense
Error updating repositories!
pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01/packagesite.txz: Bad Request
Updating pfSense-core repository catalogue...
repository pfSense-core has no meta file, using default settings
pkg: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_amd64-core/meta.txz: Bad Request
pkg: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_amd64-core/packagesite.pkg: 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-core/packagesite.txz: Bad Request
repository pfSense has no meta file, using default settings
pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01/meta.txz: Bad Request
pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01/packagesite.pkg: Bad Request
Unable to update repository pfSense
Error updating repositories!
pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01/packagesite.txz: Bad Request

                    I then ran pfSense-upgrade -dc, which resulted in the following:

                    ERROR: It was not possible to determine pkg remote version
>>> Updating repositories metadata...
Updating pfSense-core repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: . done
Processing entries: .. done
pfSense-core repository update completed. 15 packages processed.
Updating pfSense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: .......... done
Processing entries: .......... done
pfSense repository update completed. 537 packages processed.
All repositories are up to date.
Your system is up to date

                    I then ran pkg update ; pkg upgrade again, and everything worked as expected.

                    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.
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.
Checking for upgrades (0 candidates): 100%
Processing candidates (0 candidates): 100%
Checking integrity... done (0 conflicting)
Your packages are up to date.
                    1 Reply Last reply Reply Quote 0
                    • stephenw10S
                      stephenw10 Netgate Administrator
                      last edited by

                      That's expected if you have not visited the gui in some time. The access cert has expired and visiting the gui or running pfSense-upgrade will pull a new one restoring access.
                      In 23.05 that process is included in the pkg update so you shouldn't see an issue.

                      Steve

                      gnitingG 1 Reply Last reply Reply Quote 1
                      • gnitingG
                        gniting @stephenw10
                        last edited by

                        @stephenw10 said in Errors when checking for package updates.:

                        That's expected if you have not visited the gui in some time. The access cert has expired and visiting the gui or running pfSense-upgrade will pull a new one restoring access.
                        In 23.05 that process is included in the pkg update so you shouldn't see an issue.

                        Steve

                        @stephenw10 coming back to this one after upgrading to 23.05, the issue still persists. Using pkg update results in the following:

                        Updating pfSense-core repository catalogue...
repository pfSense-core has no meta file, using default settings
pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_amd64-core/meta.txz: Bad Request
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...
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/meta.txz: Bad Request
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!
Updating pfSense-core repository catalogue...
repository pfSense-core has no meta file, using default settings
pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_amd64-core/meta.txz: Bad Request
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...
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/meta.txz: Bad Request
pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_amd64-pfSense_plus_v23_05/packagesite.pkg: Bad Request
Unable to update repository pfSense
Error updating repositories!
pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_amd64-pfSense_plus_v23_05/packagesite.txz: Bad Request

                        I use the GUI often, so it can't be the case that this is happening because of lack of GUI use.

                        1 Reply Last reply Reply Quote 0
                        • 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
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.