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

    Unable to check for updates (SOLVED)

    Scheduled Pinned Locked Moved General pfSense Questions
    104 Posts 31 Posters 99.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.
    • J
      Jare 0
      last edited by

      Still having trouble with this.

      I'm on a 6100 - running 22.01.

      When running "pkg -d update" I get different errors depending on the selected firmware branch. I get an invalid link error on the release branches and the dev branch gives me much more... few examples below. I can post the entire result if needed.

      "pkg: Repository pfSense-core has a wrong packagesite, need to re-create database"

      "DBG(1)[79952]> PkgRepo: need forced update of pfSense-core"

      "pkg: wrong architecture: FreeBSD:14:amd64 instead of FreeBSD:12:amd64"

      "pkg: repository pfSense-core contains packages with wrong ABI: FreeBSD:14:amd64"

      "Processing entries... done"

      "Unable to update repository pfSense-core"

      "Error updating repositories!"

      I've searched around and found some info on forced update of the database but thought I'd check in here first.

      Thank you.

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

        Looks like you may have pulled in a bad pfSense-upgrade at some point. What does pkg info pfSense-upgrade show?
        You may need to switch the repo back to 22.01 and force reinstall pfSense-upgrade from there.

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

          @stephenw10

          pfSense-upgrade-1.0_27
          Name : pfSense-upgrade
          Version : 1.0_27
          Installed on : Fri Sep 16 19:48:18 2022 EDT
          Origin : sysutils/pfSense-upgrade
          Architecture : FreeBSD:12:amd64
          Prefix : /usr/local
          Categories : sysutils
          Licenses : APACHE20
          Maintainer : coreteam@pfsense.org
          WWW : https://www.pfsense.org/
          Comment : pfSense upgrade script
          Annotations :
          FreeBSD_version: 1203506
          build_timestamp: 2022-09-08T00:05:44+0000
          built_by : poudriere-git-3.3.99.20220831
          port_checkout_unclean: no
          port_git_hash : 83c4d6dbf695
          ports_top_checkout_unclean: yes
          ports_top_git_hash: 8065fbca4d5a
          repo_type : binary
          repository : pfSense
          Flat size : 63.7KiB
          Description :
          pfSense upgrade script

          WWW: https://www.pfsense.org/

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

            Yeah, that's a much later version.

            Make sure the update branch is set to 22.01 then run:
            pkg upgrade -f pfSense-upgrade

            That should bring you back to the correct pkg for 22.01 and that should then allow you to upgrade to either 22.05 or 23.01b.

            J D 2 Replies Last reply Reply Quote 0
            • J
              Jare 0 @stephenw10
              last edited by

              @stephenw10

              Just gave that a shot and received the following;

              pkg: invalid url: /pfSense_plus-v22_01_amd64-core
              pkg: Cannot parse configuration file!

              I would obviously like a quick fix to this, but would doing a clean install of 22.05 and uploading my 22.01 config file clear up this issue? I've been toying with the idea of changing to ZFS anyway.

              I appreciate your time - thank you.

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

                @jare-0 said in Unable to check for updates (SOLVED):

                would doing a clean install of 22.05 and uploading my 22.01 config file clear up this issue?

                Yes. An that's also probably quickest if you have local access to the firewall.

                1 Reply Last reply Reply Quote 1
                • T
                  thwong @techpro2004
                  last edited by

                  @techpro2004 thanks for your fix.
                  I was running stable 22.05.14 and since then I couldn't update to any version.

                  With your fix, I can update mine to development version without any issues.

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

                    @stephenw10
                    I'm having a similar issue. Running pkg info pfSense-upgrade gives me the following:

                    pfSense-upgrade-1.0_27
                    Name           : pfSense-upgrade
                    Version        : 1.0_27
                    Installed on   : Fri Sep 16 19:30:36 2022 EDT
                    Origin         : sysutils/pfSense-upgrade
                    Architecture   : FreeBSD:12:armv7
                    Prefix         : /usr/local
                    Categories     : sysutils
                    Licenses       : APACHE20
                    Maintainer     : coreteam@pfsense.org
                    WWW            : https://www.pfsense.org/
                    Comment        : pfSense upgrade script
                    Annotations    :
                    	FreeBSD_version: 1203506
                    	build_timestamp: 2022-09-08T00:04:38+0000
                    	built_by       : poudriere-git-3.3.99.20220831
                    	port_checkout_unclean: no
                    	port_git_hash  : 83c4d6dbf695
                    	ports_top_checkout_unclean: yes
                    	ports_top_git_hash: 8065fbca4d5a
                    	repo_type      : binary
                    	repository     : pfSense
                    Flat size      : 63.7KiB
                    Description    :
                    pfSense upgrade script
                    

                    And running pkg-static update -f gives me the following output:

                    Updating pfSense-core repository catalogue...
                    pkg-static: Repository pfSense-core has a wrong packagesite, need to re-create database
                    Fetching meta.conf: . done
                    Fetching packagesite.pkg: . done
                    Processing entries:
                    pkg-static: wrong architecture: FreeBSD:12:amd64 instead of FreeBSD:12:armv7
                    pkg-static: repository pfSense-core contains packages with wrong ABI: FreeBSD:12:amd64
                    Processing entries... done
                    Unable to update repository pfSense-core
                    Updating pfSense repository catalogue...
                    pkg-static: Repository pfSense has a wrong packagesite, need to re-create database
                    Fetching meta.conf: . done
                    Fetching packagesite.pkg: .......... done
                    Processing entries:
                    pkg-static: wrong architecture: FreeBSD:12:amd64 instead of FreeBSD:12:armv7
                    pkg-static: repository pfSense contains packages with wrong ABI: FreeBSD:12:amd64
                    Processing entries... done
                    Unable to update repository pfSense
                    Error updating repositories!
                    

                    I have also tried the fix pinned at the top of this page. I do not have local access to the system. Running an SG-3100.

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

                      Ah, OK. That manual fix should not be required for any users any longer but also it would never have applied to the 3100 because it's an armv7 device not amd64. Hence the errors you see there. You need to revert that change did you keep a copy of the original file?

                      It should be:

                      FreeBSD: { enabled: no }
                      
                      pfSense-core: {
                        url: "pkg+https://firmware.netgate.com/pkg/pfSense_plus-v22_05_armv7-core",
                        mirror_type: "srv",
                        signature_type: "fingerprints",
                        fingerprints: "/usr/local/share/pfSense/keys/pkg",
                        enabled: yes
                      }
                      
                      pfSense: {
                        url: "pkg+https://firmware.netgate.com/pkg/pfSense_plus-v22_05_armv7-pfSense_plus_v22_05",
                        mirror_type: "srv",
                        signature_type: "fingerprints",
                        fingerprints: "/usr/local/share/pfSense/keys/pkg",
                        enabled: yes
                      }
                      

                      What error are you seeing trying to update with that file in place?

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

                        @stephenw10
                        That seems to have worked. Thanks!

                        1 Reply Last reply Reply Quote 1
                        • S
                          SHoover80
                          last edited by

                          Is it too much to ask for, to just release the installer for the latest version of pfsense plus. Here I am trying to resolve an issue with PFSense Plus 22.5 resulting in me having to do a fresh install. As other recovery methods aren't working, And in normal circumstances with my situation, The easiest method would be to just do a fresh install, and use my backup config to recover and go on with my day. But I cant simply install PFSense Plus, restore my backup. and get back to where I was and what I was working on. Instead I have to install an out outdated version of CE, upgrade that, Then upgrade that to PFSense Plus, 22.1 Then upgrade that again to 22.5. But for whatever reason, CE is having issues unable to check for updates. So, 5 fresh installs failed attempts later, multiple issues during one required update process or the next. An hour+ of my time wasted dealing with update issues trying to get an outdated version of CE to update Just so I can get to the point where I get PFSense Plus to install, so I can update that and Finally get to the current Non BETA version.

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

                            It should be possible to go from 2.6 to 23.01 directly once it's released. It will probably be possible to go from 2.7 but that is a moving target.
                            Other options are in development.

                            W 1 Reply Last reply Reply Quote 0
                            • W
                              wifi-will @stephenw10
                              last edited by

                              @stephenw10 im in the same boat where i have remote sites, and to backdate firmware, i have to travel to site, backup, and install firmware from USB. I think it should be as easy to roll back firmware as it is to update. PS Sense is constantly informing you that there is an update, only to update and them find out there are issues.

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

                                If you're running a ZFS install and update from 22.05 to 23.01 it will automatically create a snapshot before the update and you can roll back it simply by selecting it.

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

                                  @techpro2004 This just worked for me also. Was on 22.01-RELEASE and getting the "unable to check" error, 22.05 now shows as available.

                                  1 Reply Last reply Reply Quote 1
                                  • J
                                    Jossk
                                    last edited by Jossk

                                    I am having a similar issue on 5100. The difference being, I can see my installed packages, but the Available Packages is empty, nor is it able to check for system updates.

                                    I have checked the pfSense.conf file. It looks to be correct (from what others have posted).

                                    I have also tried switching to the development branch, then back.

                                    pkg -d update
                                    

                                    DBG(1)[96943]> pkg initialized
                                    Updating pfSense-core repository catalogue...
                                    DBG(1)[96943]> PkgRepo: verifying update for pfSense-core
                                    DBG(1)[96943]> PkgRepo: need forced update of pfSense-core
                                    DBG(1)[96943]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense-core.sqlite'
                                    DBG(1)[96943]> Request to fetch pkg+https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-core/meta.conf
                                    DBG(1)[96943]> opening libfetch fetcher
                                    DBG(1)[96943]> Fetch > libfetch: connecting
                                    DBG(1)[96943]> Fetch: fetching from: https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-core/meta.conf with opts "i"
                                    DBG(1)[96943]> Fetch: fetching from: https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-core/meta.conf with opts "i"
                                    DBG(1)[96943]> Fetch: fetching from: https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-core/meta.conf with opts "i"
                                    DBG(1)[96943]> Request to fetch pkg+https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-core/meta.txz
                                    DBG(1)[96943]> opening libfetch fetcher
                                    DBG(1)[96943]> Fetch > libfetch: connecting
                                    DBG(1)[96943]> Fetch: fetching from: https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-core/meta.txz with opts "i"
                                    DBG(1)[96943]> Fetch: fetching from: https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-core/meta.txz with opts "i"
                                    DBG(1)[96943]> Fetch: fetching from: https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-core/meta.txz with opts "i"
                                    pkg: https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-core/meta.txz: No address record
                                    repository pfSense-core has no meta file, using default settings
                                    DBG(1)[96943]> Request to fetch pkg+https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-core/packagesite.pkg
                                    DBG(1)[96943]> opening libfetch fetcher
                                    DBG(1)[96943]> Fetch > libfetch: connecting
                                    DBG(1)[96943]> Fetch: fetching from: https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-core/packagesite.pkg with opts "i"
                                    DBG(1)[96943]> Fetch: fetching from: https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-core/packagesite.pkg with opts "i"
                                    DBG(1)[96943]> Fetch: fetching from: https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-core/packagesite.pkg with opts "i"
                                    pkg: https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-core/packagesite.pkg: No address record
                                    DBG(1)[96943]> Request to fetch pkg+https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-core/packagesite.txz
                                    DBG(1)[96943]> opening libfetch fetcher
                                    DBG(1)[96943]> Fetch > libfetch: connecting
                                    DBG(1)[96943]> Fetch: fetching from: https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-core/packagesite.txz with opts "i"
                                    DBG(1)[96943]> Fetch: fetching from: https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-core/packagesite.txz with opts "i"
                                    DBG(1)[96943]> Fetch: fetching from: https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-core/packagesite.txz with opts "i"
                                    pkg: https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-core/packagesite.txz: No address record
                                    Unable to update repository pfSense-core
                                    Updating pfSense repository catalogue...
                                    DBG(1)[96943]> PkgRepo: verifying update for pfSense
                                    DBG(1)[96943]> PkgRepo: need forced update of pfSense
                                    DBG(1)[96943]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense.sqlite'
                                    DBG(1)[96943]> Request to fetch pkg+https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-pfSense_plus_v22_05/meta.conf
                                    DBG(1)[96943]> opening libfetch fetcher
                                    DBG(1)[96943]> Fetch > libfetch: connecting
                                    DBG(1)[96943]> Fetch: fetching from: https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-pfSense_plus_v22_05/meta.conf with opts "i"
                                    DBG(1)[96943]> Fetch: fetching from: https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-pfSense_plus_v22_05/meta.conf with opts "i"
                                    DBG(1)[96943]> Fetch: fetching from: https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-pfSense_plus_v22_05/meta.conf with opts "i"
                                    DBG(1)[96943]> Request to fetch pkg+https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-pfSense_plus_v22_05/meta.txz
                                    DBG(1)[96943]> opening libfetch fetcher
                                    DBG(1)[96943]> Fetch > libfetch: connecting
                                    DBG(1)[96943]> Fetch: fetching from: https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-pfSense_plus_v22_05/meta.txz with opts "i"
                                    DBG(1)[96943]> Fetch: fetching from: https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-pfSense_plus_v22_05/meta.txz with opts "i"
                                    DBG(1)[96943]> Fetch: fetching from: https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-pfSense_plus_v22_05/meta.txz with opts "i"
                                    pkg: https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-pfSense_plus_v22_05/meta.txz: No address record
                                    repository pfSense has no meta file, using default settings
                                    DBG(1)[96943]> Request to fetch pkg+https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-pfSense_plus_v22_05/packagesite.pkg
                                    DBG(1)[96943]> opening libfetch fetcher
                                    DBG(1)[96943]> Fetch > libfetch: connecting
                                    DBG(1)[96943]> Fetch: fetching from: https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-pfSense_plus_v22_05/packagesite.pkg with opts "i"
                                    DBG(1)[96943]> Fetch: fetching from: https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-pfSense_plus_v22_05/packagesite.pkg with opts "i"
                                    DBG(1)[96943]> Fetch: fetching from: https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-pfSense_plus_v22_05/packagesite.pkg with opts "i"
                                    pkg: https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-pfSense_plus_v22_05/packagesite.pkg: No address record
                                    DBG(1)[96943]> Request to fetch pkg+https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-pfSense_plus_v22_05/packagesite.txz
                                    DBG(1)[96943]> opening libfetch fetcher
                                    DBG(1)[96943]> Fetch > libfetch: connecting
                                    DBG(1)[96943]> Fetch: fetching from: https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-pfSense_plus_v22_05/packagesite.txz with opts "i"
                                    DBG(1)[96943]> Fetch: fetching from: https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-pfSense_plus_v22_05/packagesite.txz with opts "i"
                                    DBG(1)[96943]> Fetch: fetching from: https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-pfSense_plus_v22_05/packagesite.txz with opts "i"
                                    pkg: https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-pfSense_plus_v22_05/packagesite.txz: No address record
                                    Unable to update repository pfSense
                                    Error updating repositories!

                                    I also made sure ".pfsense.org" & ".netgate.com" were in the DNSBL whitelist.

                                    Any ideas for me to try?

                                    Thanks

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

                                      @jossk said in Unable to check for updates (SOLVED):

                                      pkg: https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-pfSense_plus_v22_05/packagesite.txz: No address record
                                      Unable to update repository pfSense
                                      Error updating repositories!

                                      No address record means it cannot resolve the repo server so you have a DNS issue on the firewall. Go to Diag > DNS Lookup and resolving firmware.netgate.com. Make sure you are seeing results from the configures servers.

                                      Steve

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

                                        @stephenw10

                                        Host "firmware.netgate.com" could not be resolved.

                                        Name Servers:
                                        127.0.0.1 ----> No Response

                                        System > Gen. Setup set to "Use Local DNS, ignore remote DNS Servers".

                                        So I guess I have a misconfiguration in the DNS Resolver, then?

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

                                          Yes, I would think so. And you have no other servers configured or being passed? They won't be used with that setting in general setup though.

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

                                            @stephenw10

                                            I added all of my interfaces as DNS servers in General Setup. Only 2 interfaces are having issues, the loopback (127.0.0.1), and one other network.

                                            With any of those added, pfS can check for system updates, and the Package Manager can load the Available Packages.

                                            Knowing that, I'm more inclined to think that the more likely cause is a firewall config.

                                            Cursory glance at my firewall rules doesn't show anything that should block these 2 interfaces.

                                            I'll have to keep investigating.

                                            Thank you for the idea. Now I have a direction and a stop-gap solution until I get it working properly.

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