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

    Unable to check for updates from dashboard

    Scheduled Pinned Locked Moved General pfSense Questions
    51 Posts 7 Posters 12.8k 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.
    • N
      Nibblet @Nibblet
      last edited by

      OK, that wasn't the case either - deciding that pkg was broken I renamed it then symlinked pkg-static to /usr/sbin/pkg and still get the same behaviour.
      If I were to try to look through the sources of this widget, would anyone know where to start? (I.e - is it a separate package maybe? or is it part of the core build..?)

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

        Does it upgrade to 2.7 as expected if you just run pfSense-upgrade -d ?

        N 1 Reply Last reply Reply Quote 0
        • N
          Nibblet @stephenw10
          last edited by

          @stephenw10 I can confirm that running the pfSense-upgrade -d from the CLI does indeed work :-)
          To be fair, this is probably good enough for me - as I have other methods that do work to let me know there is a new version pending

          N 1 Reply Last reply Reply Quote 0
          • N
            Nibblet @Nibblet
            last edited by

            Also to add - version 2.7.0 also seems to have the same problem - package management works, CLI package stuff works, but the update widget immediately fails with no indication as to why.

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

              And also on the System > Update page?

              N 1 Reply Last reply Reply Quote 0
              • N
                Nibblet @stephenw10
                last edited by

                @stephenw10 That is correct, post upgrade neither the dashboard or system -> updates completes an update check and shows the same error message.

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

                  Check the version of repoc you have:

                  pkg info -x pfsense
                  N C 2 Replies Last reply Reply Quote 0
                  • N
                    Nibblet @stephenw10
                    last edited by Nibblet

                    @stephenw10
                    [2.7.0-RELEASE][admin@pfSense]/root: pkg info -x pfsense
                    pfSense-2.7.0
                    pfSense-Status_Monitoring-php82-1.8_3
                    pfSense-base-2.7.0
                    pfSense-boot-2.7.0
                    pfSense-default-config-2.7.0
                    pfSense-kernel-pfSense-2.7.0
                    pfSense-pkg-API-1.6
                    pfSense-pkg-Open-VM-Tools-10.1.0_5,1
                    pfSense-pkg-openvpn-client-export-1.8
                    pfSense-pkg-pfBlockerNG-3.2.0_5
                    pfSense-pkg-squid-0.4.46
                    pfSense-rc-2.7.0
                    pfSense-repo-2.7.0_2
                    pfSense-repoc-20230616
                    pfSense-upgrade-1.0_33
                    php82-pfSense-module-0.95

                    (Sorry it took a while, work got busy)

                    1 Reply Last reply Reply Quote 0
                    • C
                      callinectes @stephenw10
                      last edited by callinectes

                      @stephenw10 I am having the same problem. Upgrade response was working fine a few weeks ago - before 2.7.0 came out. Now, if I run pkg info -x pfsense I get: ld-elf.so.1: Shared object "libssl.so.30" not found, required by "pkg"

                      If I run pkg-static info -x pfSense-upgrade I get: pkg-static: Warning: Major OS version upgrade detected. Running "pkg bootstrap -f" recommended
                      pfSense-upgrade-1.0_15

                      If I run pfSense-upgrade -d -c I get:

                      Updating repositories metadata...
                      pkg-static: Warning: Major OS version upgrade detected. Running "pkg bootstrap -f" recommended
                      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!
                      Upgrading pkg...
                      pkg-static: Warning: Major OS version upgrade detected. Running "pkg bootstrap -f" recommended
                      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!

                      Any ideas? This is happening on two separate systems - one running 2.6.0 and one running 2.7.0-devel.

                      GertjanG S 2 Replies Last reply Reply Quote 0
                      • GertjanG
                        Gertjan @callinectes
                        last edited by

                        @callinectes said in Unable to check for updates from dashboard:

                        If I run pfSense-upgrade -d -c I get:

                        Updating repositories metadata...
                        pkg-static: Warning: Major OS version upgrade detected. Running "pkg bootstrap -f" recommended

                        Can you tell us what happens when you executed the recommend action ?

                        No "help me" PM's please. Use the forum, the community will thank you.
                        Edit : and where are the logs ??

                        C 1 Reply Last reply Reply Quote 0
                        • C
                          callinectes @Gertjan
                          last edited by

                          @Gertjan Thanks for the response. I assume you mean running "pkg bootstrap -f"? I cannot do that right now but will attempt later and post back.

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

                            @callinectes said in Unable to check for updates from dashboard:

                            Shared object "libssl.so.30" not found, required by "pkg"

                            That error often means you have tried to install or update a package with the update branch set to a later pfSense version. (it defaults to Current) That tries to update any required libraries.

                            https://redmine.pfsense.org/issues/10464

                            There are a couple suggestions in that redmine but otherwise one can reinstall and restore from backup.

                            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

                              Seeing that lib error usually only means the version of pkg has been updated. That's normal as it checks for a new version every time it looks for pfSense updates.
                              It shouldn't be a problem since the pfSense pkg commands all use pkg-static.

                              @callinectes said in Unable to check for updates from dashboard:

                              Updating repositories metadata...
                              pkg-static: Warning: Major OS version upgrade detected. Running "pkg bootstrap -f" recommended
                              Updating pfSense-core repository catalogue...
                              pkg-static: An error occured while fetching package

                              Seeing that I would try running pkg-static -d update to see what error is shown there.

                              C 1 Reply Last reply Reply Quote 0
                              • C
                                callinectes @stephenw10
                                last edited by

                                @stephenw10 Thanks for the suggestion. I received a lot of the following (too many similar entries to paste in but happy to if it would help:

                                • Hostname pkg00-atx.netgate.com was found in DNS cache

                                • Trying 208.123.73.207:443...

                                • Connected to pkg00-atx.netgate.com (208.123.73.207) port 443 (#9)

                                • ALPN: offers http/1.1

                                • CAfile: none

                                • CApath: /etc/ssl/certs/

                                • SSL certificate problem: self-signed certificate in certificate chain

                                • Closing connection 9
                                  DBG(1)[86277]> CURL> attempting to fetch from , left retry 2

                                • Hostname pkg01-atx.netgate.com was found in DNS cache

                                • Trying 208.123.73.209:443...

                                • Connected to pkg01-atx.netgate.com (208.123.73.209) port 443 (#10)

                                • ALPN: offers http/1.1

                                • CAfile: none

                                • CApath: /etc/ssl/certs/

                                • SSL certificate problem: self-signed certificate in certificate chain

                                • Closing connection 10
                                  DBG(1)[86277]> CURL> attempting to fetch from , left retry 1

                                • Hostname pkg00-atx.netgate.com was found in DNS cache

                                • Trying 208.123.73.207:443...

                                • Connected to pkg00-atx.netgate.com (208.123.73.207) port 443 (#11)

                                • ALPN: offers http/1.1

                                • CAfile: none

                                • CApath: /etc/ssl/certs/

                                • SSL certificate problem: self-signed certificate in certificate chain

                                • Closing connection 11
                                  pkg-static: An error occured while fetching package
                                  Unable to update repository pfSense
                                  Error updating repositories!

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

                                  Ah, what pfSense version are you running? That output is from the new development pkg version.

                                  C 1 Reply Last reply Reply Quote 0
                                  • C
                                    callinectes @stephenw10
                                    last edited by

                                    @stephenw10 Per the dashboard "Version 2.6.0-RELEASE (amd64)"

                                    But it was set to watch the 2.7.0 devel versions

                                    GertjanG 1 Reply Last reply Reply Quote 0
                                    • GertjanG
                                      Gertjan @callinectes
                                      last edited by

                                      @callinectes said in Unable to check for updates from dashboard:

                                      watch the 2.7.0 devel versions

                                      Strange.
                                      That version doesn't exist any more since the end of June, as 'dev' became 'Release'.
                                      On the other hand, if it can't update any more, it also can't update the list with available versions.

                                      What about the the easy way out :
                                      Get an USB drive, goto pfsense download - download your version 2.7.0.
                                      Build teh USB drive.
                                      Export the current config.
                                      Boot the pfSEnse device from USB, install pfSense, 'all clean'.
                                      When it reboot ... check that it shows a 'future version' (or ancient 2.6.0)
                                      Check that the available package list populates.
                                      Now, import your config.
                                      Reboot.
                                      Be very patient, as packages get installed in the background.
                                      When you are sure it's done, do a reboot for good manners.
                                      After reboot : test and check most needed and important system functionalities.

                                      Make a post-it, and paste it on the pfSense box : "stay away from bleeding edge technology".

                                      No "help me" PM's please. Use the forum, the community will thank you.
                                      Edit : and where are the logs ??

                                      1 Reply Last reply Reply Quote 0
                                      • GertjanG Gertjan referenced this topic on
                                      • stephenw10S
                                        stephenw10 Netgate Administrator
                                        last edited by

                                        It is possible to recover from there but it requires some command line shenanigans.

                                        What update branches do you see offered in System > Update?

                                        C 1 Reply Last reply Reply Quote 0
                                        • C
                                          callinectes @stephenw10
                                          last edited by

                                          @stephenw10 It appears the way I would assume it would if 2.7.0 was installed. The drop down shows:

                                          • Latest stable version (v2.7.0)
                                          • DEVEL version (devel)
                                          • PREVIOUS version (v2.6.0)
                                          1 Reply Last reply Reply Quote 0
                                          • stephenw10S
                                            stephenw10 Netgate Administrator
                                            last edited by

                                            OK, that's good, it has the correct repo pkg. Make sure the branch is set to 'Latest stable version (v2.7.0)'.

                                            Check what version of pkg you have:

                                            pkg-static info pkg

                                            Then check for older cached versions:

                                            ls /var/cache/pkg/pkg*

                                            You will probably have version 1.20.4 installed and hopefully have an older version available.

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