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

    PFsense unable to check for update n Unable to retrieve package information

    Scheduled Pinned Locked Moved General pfSense Questions
    29 Posts 8 Posters 16.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.
    • D
      DaveP 0 @stephenw10
      last edited by

      @stephenw10 said in PFsense unable to check for update n Unable to retrieve package information:

      pkg-static -d update

      Rather a long log output so I've pasted it into a txt file. Noticed some cert errors.

      I've already installed three times with no difference and when I go to update it tells me it is on the latest so doesn't offer the upgrade button.

      return.txt

      Screenshot from 2024-07-02 13-50-41.png

      I do have IPv6 enabled and tried to disable it to test if that was it and got this

      Shell Output - pfSense-upgrade -4

      ERROR: It was not possible to determine pkg remote version

      Updating repositories metadata...
      Updating pfSense-core repository catalogue...
      pkg-static: An error occured while fetching package
      pkg-static: An error occured while fetching package
      repository pfSense-core has no meta file, using default settings
      pkg-static: An error occured while fetching package
      pkg-static: An error occured while fetching package
      Unable to update repository pfSense-core
      Updating pfSense repository catalogue...
      pkg-static: An error occured while fetching package
      pkg-static: An error occured while fetching package
      repository pfSense has no meta file, using default settings
      pkg-static: An error occured while fetching package
      pkg-static: An error occured while fetching package
      Unable to update repository pfSense
      Error updating repositories!
      ERROR: It was not possible to determine pfSense-upgrade remote version
      ERROR: It was not possible to determine pfSense-upgrade remote version
      Upgrading pfSense-upgrade... failed.

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

        Ok run certctl rehash then recheck.

        D 1 Reply Last reply Reply Quote 0
        • D
          DaveP 0 @stephenw10
          last edited by

          @stephenw10 OK. Tried that. I got this which didn't say much.

          Shell Output - certctl rehash

          Scanning /usr/share/certs/untrusted for certificates...
          Scanning /usr/share/certs/trusted for certificates...
          Scanning /usr/local/share/certs for certificates...

          I waited a few mins in case it was doing something in the background. I then tried the package list again and the same error.

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

            OK so pkg-static -d update shows the same output?

            D 1 Reply Last reply Reply Quote 0
            • D
              DaveP 0 @stephenw10
              last edited by

              @stephenw10 No. There is a lot more data returned from
              pkg-static -d update

              return2.txt

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

                OK that's working correctly now you should be able to upgrade.

                You won't see packages until after you upgrade or switch the repo back to 2.7.0. The 2.7.2 packages it's seeing now are not compatible with 2.7.0.

                D 1 Reply Last reply Reply Quote 0
                • D
                  DaveP 0 @stephenw10
                  last edited by

                  @stephenw10 OK that makes sense Thanks for sorting that out. It is looking for incompatible packages. The error message was a bit ambiguous though.

                  What am I upgrading to? It says I am up to date and the buttons to upgrade are gone.

                  How do I switch the repo back to 2.7.0. and what are the implications? I think I'd leave it on the standard path if I can get the packages working.

                  I'll look at the repo system now. Never really looked at it properly because until 2.7.0 everything just worked.

                  D 1 Reply Last reply Reply Quote 0
                  • D
                    DaveP 0 @DaveP 0
                    last edited by

                    @stephenw10 Ignore that previous post. I stupidly didn't look at the upgrade page where it quite clearly said upgrade to 2.7.2. Sorry, you have enough to do without idiots wasting your time.

                    Anyway clicked the button and upgraded. When it rebooted I then went to the package manager and it downloaded a list of packages successfully.

                    Thank you very much.

                    btw: I did install a few times from scratch so clearly there is something there that isn't right in the core 2.7.0.

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

                      The cert hashing issue is a known bug in 2.7.0. It's fixed in 2.7.1 and later:

                      https://docs.netgate.com/pfsense/en/latest/releases/2-7-1.html#troubleshooting

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