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

    No available packages

    General pfSense Questions
    14
    64
    16.5k
    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.
    • T
      tedquade @G.Hammer
      last edited by

      @g-hammer Yes, Yes and Yes (I'm a person of few words).

      Ted Quade

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

        @flatsphere said in No available packages:

        rm: /usr/local/share/pfSense/pkg/repos/pfSense-repo-custom.*: No such file or directory
        Still no packages.

        Did you also resave the update repo settings?

        Are you also seeing the 'Bad Request' error from pkg -d update?
        There are other reasons you might not see packages. Bug #14137 only applies to recent upgrades from CE.

        F 1 Reply Last reply Reply Quote 1
        • F
          flatsphere @stephenw10
          last edited by

          @stephenw10 said in No available packages:

          pkg -d update

          Hi Stephen,

          Yes, saved but I've no selections in update other than "Latest Stable Version (23.01)" . Saved and rebooted. Also tried "Disable the Dashboard auto-update check", saved and rebooted.
          Yes, getting "bad request" from pkg -d update.
          I did recently upgrade from latest version of CE.

          Cheers!
          R

          T 1 Reply Last reply Reply Quote 1
          • T
            tedquade @flatsphere
            last edited by

            @flatsphere

            From the Dashboard go to:
            System > Update > Update Settings then "Save"

            Then Diagnostics > Command Prompt > Execute Shell Command then in Command enter the following:
            rm /usr/local/share/pfSense/pkg/repos/pfSense-repo-custom.*

            Then select Execute.

            That is the sequence I followed and it worked for me.

            Ted Quade

            F 1 Reply Last reply Reply Quote 0
            • F
              flatsphere @tedquade
              last edited by

              @tedquade said in No available packages:

              rm /usr/local/share/pfSense/pkg/repos/pfSense-repo-custom.*

              I did that and received the "No such file or directory" message.
              😕
              Thanks!
              R

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

                Send me your NDI and the output pkg -d update in chat and I'll check it.

                P 1 Reply Last reply Reply Quote 0
                • P
                  p1erre @stephenw10
                  last edited by

                  @stephenw10 said in No available packages:

                  Send me your NDI and the output pkg -d update in chat and I'll check it.

                  Hi Stephen

                  I get the same error on my Netgate 6100 without upgrading from a CE

                  Error messages posted on https://redmine.pfsense.org/issues/14137

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

                    Did you resave the stable repo settings?

                    1 Reply Last reply Reply Quote 0
                    • P
                      p1erre
                      last edited by

                      @stephenw10 said in No available packages:

                      Did you resave the stable repo settings?

                      Yes I did. It also shows me the latest stable version 23.01

                      Current Base System23.01
                      Latest Base System23.01
                      StatusUp to date.

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

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

                        That error means it's trying to authenticate the repo using the wrong cert. Resaving the repo should set the correct line in the config file so it then uses the correct cert.

                        Steve

                        1 Reply Last reply Reply Quote 0
                        • T
                          tedquade @p1erre
                          last edited by

                          @p1erre You need to do the following in order to save as instructed by Steve:

                          System > Update > Update Settings > Save

                          This is what worked for me when I had similar issues to yours.

                          Ted Quade

                          P 1 Reply Last reply Reply Quote 1
                          • P
                            p1erre @tedquade
                            last edited by

                            @tedquade Thanks Ted, but I already did it. Issue still there. I also did

                            mkdir /root/backup && cp -r /usr/local/etc/pfSense/pkg/repos /root/backup/ && rm -rf /usr/local/etc/pfSense/pkg/repos && pfSense-upgrade -c -d

                            as suggested in another thread. Still getting

                            pfSense-upgrade -c -d
......ERROR: It was not possible to determine pkg remote version
>>> Updating repositories metadata...
Updating pfSense-core repository catalogue...
Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/OU=pfSense Plus/CN=pfsense-plus-pkg00.atx.netgate.com
34942701568:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921:
Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/OU=pfSense Plus/CN=pfsense-plus-pkg00.atx.netgate.com
...
34942701568:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921:
Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/OU=pfSense Plus/CN=pfsense-plus-pkg00.atx.netgate.com
34942701568:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921:
pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01/packagesite.txz: Authentication error
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
                            1 Reply Last reply Reply Quote 0
                            • P p1erre referenced this topic on
                            • P p1erre referenced this topic on
                            • T
                              tsrats
                              last edited by

                              I too am unable to see any packages. I believe I switched to pfSense+ but cannot remember. I have followed all the steps in this thread and the bug report and no progress. I also see the following, even though I have registered (and now reregistered) it with pfSense+

                              Your device has not been registered for pfSense+. Please purchase a pfSense+ subscription at the <a href="https://shop.netgate.com/products/pfsense-software-subscription" target="_blank" rel="noopener noreferrer">Netgate store</a> to receive future updates.                                                              
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
                              1 Reply Last reply Reply Quote 0
                              • stephenw10S
                                stephenw10 Netgate Administrator
                                last edited by

                                Most likely your NDI changed since you first registered it. Send it to me in chat and I can check.

                                1 Reply Last reply Reply Quote 0
                                • P p1erre referenced this topic on
                                • P p1erre referenced this topic on
                                • D
                                  DominikHoffmann
                                  last edited by

                                  I was sent here by @p1erre (Thanks!) from an original thread I had posted: No available packages. My hardware is a Netgate 2100 that had never been on the CE of pfSense. About three weeks ago I updated it from 22.05 to 23.01 using the

                                  run usbrecovery

                                  method, when I had experienced a couple of catastrophic update failures with other pfSense installations I manage.

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

                                    What do you see if you run pkg -d update at the command line?

                                    Steve

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

                                      @stephenw10: This is the output

                                      [23.01-RELEASE][admin@***.***]/root: pkg -d update
DBG(1)[80971]> pkg initialized
Updating pfSense-core repository catalogue...
DBG(1)[80971]> PkgRepo: verifying update for pfSense-core
DBG(1)[80971]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense-core.sqlite'
DBG(1)[80971]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_01_aarch64-core/meta.conf
DBG(1)[80971]> opening libfetch fetcher
DBG(1)[80971]> Fetch > libfetch: connecting
DBG(1)[80971]> Fetch: fetching from: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_aarch64-core/meta.conf with opts "i"
DBG(1)[80971]> Fetch: fetcher chosen: https
DBG(1)[80971]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_01_aarch64-core/packagesite.pkg
DBG(1)[80971]> opening libfetch fetcher
DBG(1)[80971]> Fetch > libfetch: connecting
DBG(1)[80971]> Fetch: fetching from: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_aarch64-core/packagesite.pkg with opts "i"
DBG(1)[80971]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_01_aarch64-core/packagesite.txz
DBG(1)[80971]> opening libfetch fetcher
DBG(1)[80971]> Fetch > libfetch: connecting
DBG(1)[80971]> Fetch: fetching from: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_aarch64-core/packagesite.txz with opts "i"
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
DBG(1)[80971]> PkgRepo: verifying update for pfSense
DBG(1)[80971]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense.sqlite'
DBG(1)[80971]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_01_aarch64-pfSense_plus_v23_01/meta.conf
DBG(1)[80971]> opening libfetch fetcher
DBG(1)[80971]> Fetch > libfetch: connecting
DBG(1)[80971]> Fetch: fetching from: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_aarch64-pfSense_plus_v23_01/meta.conf with opts "i"
DBG(1)[80971]> Fetch: fetcher chosen: https
DBG(1)[80971]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_01_aarch64-pfSense_plus_v23_01/packagesite.pkg
DBG(1)[80971]> opening libfetch fetcher
DBG(1)[80971]> Fetch > libfetch: connecting
DBG(1)[80971]> Fetch: fetching from: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_aarch64-pfSense_plus_v23_01/packagesite.pkg with opts "i"
DBG(1)[80971]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_01_aarch64-pfSense_plus_v23_01/packagesite.txz
DBG(1)[80971]> opening libfetch fetcher
DBG(1)[80971]> Fetch > libfetch: connecting
DBG(1)[80971]> Fetch: fetching from: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_aarch64-pfSense_plus_v23_01/packagesite.txz with opts "i"
pfSense repository is up to date.
All repositories are up to date.

                                      Doesn’t that contradict the fact that the Avahi package is not on the latest version?
                                      Screenshot 2023-04-05 at 10.59.51 AM.png

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

                                        Hmm, that fact it can see it's not on the latest version means it's able to see the pkg repo. That output all looks good so I'd expect a firmware update to also be fine.

                                        What do you see from pfSense-upgrade-dc?

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

                                          @stephenw10

                                          [23.01-RELEASE][admin@smiley.ahs.selfip.net]/root: pfSense-upgrade-dc
pfSense-upgrade-dc: Command not found.
                                          1 Reply Last reply Reply Quote 0
                                          • stephenw10S
                                            stephenw10 Netgate Administrator
                                            last edited by

                                            Sorry typo'd. Try: pfSense-upgrade -dc

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