• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
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 96.0k 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.
  • T
    techpro2004
    last edited by Sep 17, 2022, 4:14 AM

    bug is still there

    A little more info: It wont even let me manually install a package. in pfSense.conf it only lists part of the urls. Not sure what the rest are to correct it but the beginning of the urls are missing.

    1 Reply Last reply Reply Quote 0
    • T
      techpro2004
      last edited by Sep 17, 2022, 4:28 AM

      I have developed a temporary fix.

      edit /usr/local//etc/pkg/repos/pfSense.conf

      add the following to the beginning of both urls inside the quotes

      pkg+https://firmware.netgate.com/pkg

      T D 2 Replies Last reply Jan 16, 2023, 10:25 AM Reply Quote 7
      • B
        bingo600
        last edited by bingo600 Sep 17, 2022, 8:47 AM Sep 17, 2022, 6:53 AM

        I have the same issue on my "Home Firewall in DK" (22.05)

        Discovered by me , due to extremely long Web-Gui login time.
        And some fumbling around revealed the "Unable to check for updates" in the GUI.

        Saw this in the system log:

        Sep 17 01:00:03 	pkg-static 	24861 	pfSense-repo upgraded: 22.05_2 -> 22.05_5
        Sep 17 01:00:03 	pkg-static 	24861 	pfSense-upgrade upgraded: 1.0_26 -> 1.0_27 
        

        And running "pkg-static -d update" .. Barfs at me:

        22.05-RELEASE][admin@fw-01]/root: pkg-static -d update
        DBG(1)[74683]> pkg initialized
        pkg-static: invalid url: /pfSense_plus-v22_05_amd64-core
        pkg-static: Cannot parse configuration file!
        [22.05-RELEASE][admin@fw-01]/root:
        

        If i go to Installed Packages it says none is installed, but if i goto my zabbix package , it shows up fine , and Zabbix isn't Barfing.

        a27d14bd-02ae-4409-8356-ae8a2f971c85-image.png

        The Summerhouse (22.05) in SE , don't have this issue

        Saw this in the system log:

        Sep 17 08:11:49 	pkg-static 	55031 	pfSense-repo upgraded: 22.05_2 -> 22.05_9
        Sep 17 08:11:49 	pkg-static 	55031 	pfSense-upgrade upgraded: 1.0_26 -> 1.0_27 
        

        Would there be a difference in upgrades pulled at 01.00 vs 08.00

        I'm in the summerhouse right now, and my ATV (AppleTv) exit's in DK.

        Due to "Possible Wife imposed health issues, or Ear-Pain" if the ATV connection is lost. I will "Chiken out" on doing reboot or other "dangerous things to the DK firewall"

        Edit - Just noticed the :
        DK firewall did a 22.05_2 -> 22.05_5 upgrade (has issues)
        SE firewall did a 22.05_2 -> 22.05_9 upgrade (has no issues)

        So the update repos version switched in that timeframe.
        Did Netgate fix a goof ??

        Edit2:
        Reading the nice hint from @techpro2004

        I see that important info is missing in my DK
        /usr/local/etc/pkg/repos/pfSense.conf

        cat /usr/local/etc/pkg/repos/pfSense.conf
        FreeBSD: { enabled: no }
        
        pfSense-core: {
          url: "/pfSense_plus-v22_05_amd64-core",
          mirror_type: "srv",
          signature_type: "fingerprints",
          fingerprints: "/usr/local/share/pfSense/keys/pkg",
          enabled: yes
        }
        
        pfSense: {
          url: "/pfSense_plus-v22_05_amd64-pfSense_plus_v22_05",
          mirror_type: "srv",
          signature_type: "fingerprints",
          fingerprints: "/usr/local/share/pfSense/keys/pkg",
          enabled: yes
        }
        
        

        SE (working) contains:
        /usr/local/etc/pkg/repos/pfSense.conf

        cat /usr/local/etc/pkg/repos/pfSense.conf
        FreeBSD: { enabled: no }
        
        pfSense-core: {
          url: "pkg+https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-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_amd64-pfSense_plus_v22_05",
          mirror_type: "srv",
          signature_type: "fingerprints",
          fingerprints: "/usr/local/share/pfSense/keys/pkg",
          enabled: yes
        }
        
        

        NB:
        The path should be : /usr/local/etc/pkg/repos/pfSense.conf

        Solved:
        Replacing the two url: entries in the /usr/local/etc/pkg/repos/pfSense.conf , on my DK firewall, with the contents from my SE fiewwall. And running a pkg-static -d update , seems to have fixed the issue.

        I how have this in the GUI:
        6439ba9f-91c5-42b9-911c-1ed731a662dc-image.png

        And my Installed Packages shows up again.
        Indicating that System_Patches package should be manually updated.
        The new System_Patches, adds the CRL fix as recommended.

        @techpro2004
        Thanx for the hint 👍 👍

        /Bingo

        If you find my answer useful - Please give the post a 👍 - "thumbs up"

        pfSense+ 23.05.1 (ZFS)

        QOTOM-Q355G4 Quad Lan.
        CPU  : Core i5 5250U, Ram : 8GB Kingston DDR3LV 1600
        LAN  : 4 x Intel 211, Disk  : 240G SAMSUNG MZ7L3240HCHQ SSD

        1 Reply Last reply Reply Quote 7
        • M
          mvikman
          last edited by Sep 17, 2022, 8:48 AM

          I had this exact same problem (noticed it yesterday) and can confirm the findings from techpro2004 and bingo6000

          After fixing the URLs in "/usr/local/etc/pkg/repos/pfSense.conf" everything went back to normal.

          pfSense Plus 24.11-RELEASE (amd64)
          Dell Optiplex 7040 SFF
          Core i5-6500, 8GB RAM, 2x 240GB SSD (ZFS Mirror)
          HPE 561T (X540-AT2), 2-port 10Gb RJ45
          HPE 562SFP+ (X710-DA2), 2-port 10Gb SFP+

          1 Reply Last reply Reply Quote 1
          • B
            Bob.Dig LAYER 8
            last edited by Bob.Dig Sep 17, 2022, 10:21 AM Sep 17, 2022, 9:30 AM

            Still would be nice to have an automatic fix for the lazy people. I was frightened seeing this until I came here.

            Screenshot 2022-09-17 113220.png

            1 Reply Last reply Reply Quote 2
            • B
              bingo600
              last edited by bingo600 Sep 17, 2022, 12:40 PM Sep 17, 2022, 11:20 AM

              Here is a "One Liner" , that ought to fix it.

              sed -i "" 's/url: "/url: "pkg+https:\/\/firmware.netgate.com\/pkg/g' /usr/local/share/pfSense/pkg/repos/pfSense-repo.conf
              

              Note:
              /usr/local/etc/pkg/repos/pfSense.conf - Is symlinked to /usr/local/share/pfSense/pkg/repos/pfSense-repo.conf

              ls -l /usr/local/etc/pkg/repos/pfSense.conf                                            lrwxr-xr-x  1 root  wheel  52 Sep  2 19:36 /usr/local/etc/pkg/repos/pfSense.conf -> /usr/local/share/pfSense/pkg/repos/pfSense-repo.conf
              

              And sed won't work on a symlink

              Therefore the "One-Liner" refers to the real file , not the symlinked one.

              sed -i "" 's/url: "/url: "pkg+https:\/\/firmware.netgate.com\/pkg/g' /usr/local/share/pfSense/pkg/repos/pfSense-repo.conf
              

              Backup your existing : /usr/local/share/pfSense/pkg/repos/pfSense-repo.conf , before using the above command.

              Something like

              cp /usr/local/share/pfSense/pkg/repos/pfSense-repo.conf /usr/local/share/pfSense/pkg/repos/pfSense-repo.conf.org
              

              After fixing with the "One-Liner" maybe update the repos from CLI:

              pkg-static -d update 
              

              /Bingo

              If you find my answer useful - Please give the post a 👍 - "thumbs up"

              pfSense+ 23.05.1 (ZFS)

              QOTOM-Q355G4 Quad Lan.
              CPU  : Core i5 5250U, Ram : 8GB Kingston DDR3LV 1600
              LAN  : 4 x Intel 211, Disk  : 240G SAMSUNG MZ7L3240HCHQ SSD

              1 Reply Last reply Reply Quote 6
              • B
                Bob.Dig LAYER 8
                last edited by Sep 17, 2022, 12:03 PM

                @jimp I hope netgate will fix it too.

                B 1 Reply Last reply Sep 17, 2022, 12:38 PM Reply Quote 1
                • B
                  bingo600 @Bob.Dig
                  last edited by bingo600 Sep 17, 2022, 12:51 PM Sep 17, 2022, 12:38 PM

                  @bob-dig said in Unable to check for updates:

                  @jimp I hope netgate will fix it too.

                  That could be a "Chicken / Egg" issue, if the pfS uses those url's to fetch everything.

                  Even though it's weekend , i find it a bit strange that we haven't heard anything from Netgate, not even an ACK.

                  /Bingo

                  If you find my answer useful - Please give the post a 👍 - "thumbs up"

                  pfSense+ 23.05.1 (ZFS)

                  QOTOM-Q355G4 Quad Lan.
                  CPU  : Core i5 5250U, Ram : 8GB Kingston DDR3LV 1600
                  LAN  : 4 x Intel 211, Disk  : 240G SAMSUNG MZ7L3240HCHQ SSD

                  B 1 Reply Last reply Sep 17, 2022, 12:40 PM Reply Quote 0
                  • B
                    Bob.Dig LAYER 8 @bingo600
                    last edited by Bob.Dig Sep 17, 2022, 12:43 PM Sep 17, 2022, 12:40 PM

                    @bingo600 But why now, it has worked until yesterday, I am on 22.05 for months now. So what has changed when? Sry, for not getting the root of the problem.

                    B 1 Reply Last reply Sep 17, 2022, 12:48 PM Reply Quote 1
                    • B
                      bingo600 @Bob.Dig
                      last edited by Sep 17, 2022, 12:48 PM

                      @bob-dig
                      See my initial post here

                      https://forum.netgate.com/post/1062012

                      And note that my DK FW (with the issue) updated to 22.05_5 at 01:00 CEST

                      Sep 17 01:00:03 	pkg-static 	24861 	pfSense-repo upgraded: 22.05_2 -> 22.05_5
                      

                      My SE FW (with no issue) updated to 22.05_9 at 08:11 CEST

                      Sep 17 08:11:49 	pkg-static 	55031 	pfSense-repo upgraded: 22.05_2 -> 22.05_9
                      

                      My guess is that the 22.05_05 update somehow FSCK'ed up the repos url's. And that Netgate got it fixed, sometime in the 01:00 to 08:11 timeframe.

                      So "Slow updaters" are not affected , "Fast updaters" are affected.

                      /Bingo

                      If you find my answer useful - Please give the post a 👍 - "thumbs up"

                      pfSense+ 23.05.1 (ZFS)

                      QOTOM-Q355G4 Quad Lan.
                      CPU  : Core i5 5250U, Ram : 8GB Kingston DDR3LV 1600
                      LAN  : 4 x Intel 211, Disk  : 240G SAMSUNG MZ7L3240HCHQ SSD

                      B 1 Reply Last reply Sep 17, 2022, 12:56 PM Reply Quote 0
                      • B
                        Bob.Dig LAYER 8 @bingo600
                        last edited by Sep 17, 2022, 12:56 PM

                        @bingo600 So we are talking not about an update of pfSense to a new version but to the repos stored in pfSense? And there is no Boot Environment for fixing it. Also there is nothing in Config History, maybe because I changed stuff today.

                        But lets say, I didn't changed something of interest in the last two days, I can use my own backup und it should be good. I will try that.

                        B 1 Reply Last reply Sep 17, 2022, 1:27 PM Reply Quote 0
                        • B
                          bingo600 @Bob.Dig
                          last edited by bingo600 Sep 17, 2022, 1:28 PM Sep 17, 2022, 1:27 PM

                          @bob-dig said in Unable to check for updates:

                          @bingo600 So we are talking not about an update of pfSense to a new version but to the repos stored in pfSense?

                          Yes, a repos update ... And the naming might hint that 22.09 is close.

                          And there is no Boot Environment for fixing it.

                          I do not know pfSense well enough to know if there is another way of downloading a fix.

                          Also there is nothing in Config History, maybe because I changed stuff today.

                          I saw it (the update) in the System General Log

                          6ba322a6-6dfe-4e59-a1fb-e36aebd172e6-image.png

                          .
                          .

                          But lets say, I didn't changed something of interest in the last two days, I can use my own backup und it should be good. I will try that.

                          Your config should not have been affected , and restoring the config would not fix it.

                          A full reinstall would probably fix it, as it would pull the '09 repos update not the '05.
                          But that would (IMHO) be a lot of hassle, in order to avoid doing a ssh admin@xxxxxx , select 8 , and do the "One-Liner"

                          /Bingo

                          If you find my answer useful - Please give the post a 👍 - "thumbs up"

                          pfSense+ 23.05.1 (ZFS)

                          QOTOM-Q355G4 Quad Lan.
                          CPU  : Core i5 5250U, Ram : 8GB Kingston DDR3LV 1600
                          LAN  : 4 x Intel 211, Disk  : 240G SAMSUNG MZ7L3240HCHQ SSD

                          M B 2 Replies Last reply Sep 17, 2022, 1:29 PM Reply Quote 1
                          • M
                            mcury @bingo600
                            last edited by Sep 17, 2022, 1:29 PM

                            @bingo600 said in Unable to check for updates:

                            Yes, a repos update ... And the naming might hint that 22.09 is close.

                            I think it is close indeed..
                            https://redmine.pfsense.org/projects/pfsense-plus/issues?fixed_version_id=60&set_filter=1&status_id=%2A

                            dead on arrival, nowhere to be found.

                            1 Reply Last reply Reply Quote 1
                            • S
                              sgc Rebel Alliance
                              last edited by sgc Sep 17, 2022, 2:30 PM Sep 17, 2022, 2:29 PM

                              This is what NetGate support sent to me about this problem.

                              Diagnostics --> Edit File --> and in the "Path to file to be Edited", please enter the following and click "Load":

                              /usr/local/share/pfSense/pkg/repos/pfSense-repo.conf

                              You can then replace the file with the following contents and hit "Save". This will resolve your issue:

                              FreeBSD: { enabled: no }

                              pfSense-core: {
                              url: "pkg+https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-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_amd64-pfSense_plus_v22_05",
                              mirror_type: "srv",
                              signature_type: "fingerprints",
                              fingerprints: "/usr/local/share/pfSense/keys/pkg",
                              enabled: yes
                              }

                              The problem is gone after changing this.

                              W 1 Reply Last reply Jan 10, 2023, 1:43 AM Reply Quote 13
                              • B
                                Bob.Dig LAYER 8 @bingo600
                                last edited by Bob.Dig Sep 17, 2022, 2:44 PM Sep 17, 2022, 2:37 PM

                                @bingo600
                                I rolled back an "Image" from yesterday mornings backup, fixed it as well. The good thing about all that, I just noticed that I can't roll back an Image of pfSense when it is not running, do to the way I built my network lately, so I had to change that again. 😊

                                I think the (official) solution should be pinned somehow.

                                B 1 Reply Last reply Sep 17, 2022, 2:45 PM Reply Quote 0
                                • B
                                  bingo600 @Bob.Dig
                                  last edited by Sep 17, 2022, 2:45 PM

                                  @bob-dig
                                  How did you do that "image backup" ?
                                  Via the new Boot Environment in 22.05 ?

                                  Wonder if that one would restore the system too ?
                                  Anyone knows ???

                                  If you find my answer useful - Please give the post a 👍 - "thumbs up"

                                  pfSense+ 23.05.1 (ZFS)

                                  QOTOM-Q355G4 Quad Lan.
                                  CPU  : Core i5 5250U, Ram : 8GB Kingston DDR3LV 1600
                                  LAN  : 4 x Intel 211, Disk  : 240G SAMSUNG MZ7L3240HCHQ SSD

                                  B 1 Reply Last reply Sep 17, 2022, 3:11 PM Reply Quote 0
                                  • S
                                    stephenw10 Netgate Administrator
                                    last edited by Sep 17, 2022, 2:57 PM

                                    This is fixed now. As noted the newer repo pkg has the correct URL.

                                    If you're still seeing it, because the firewall pulled in the bad pkg, then switching the update branch to development and then back to latest stable will pull in the fixed pkg.

                                    Doing that you will see logged:

                                    Sep 17 15:36:45 	pkg-static 	13430 	pfSense-repo upgraded: 22.05_5 -> 22.09.a.20220802.0600
                                    Sep 17 15:37:19 	pkg-static 	22387 	pfSense-repo downgraded: 22.09.a.20220802.0600 -> 22.05_9 
                                    

                                    Steve

                                    1 Reply Last reply Reply Quote 7
                                    • B
                                      Bob.Dig LAYER 8 @bingo600
                                      last edited by Bob.Dig Sep 17, 2022, 3:13 PM Sep 17, 2022, 3:11 PM

                                      @bingo600 said in Unable to check for updates:

                                      @bob-dig
                                      How did you do that "image backup" ?

                                      I use a vm for pfSense.

                                      @stephenw10 said in Unable to check for updates:

                                      This is fixed now.

                                      Too bad I can't test this slick approach to that problem anymore. 😉

                                      B 1 Reply Last reply Sep 17, 2022, 3:16 PM Reply Quote 0
                                      • B bingo600 referenced this topic on Sep 17, 2022, 3:12 PM
                                      • B
                                        bingo600 @Bob.Dig
                                        last edited by Sep 17, 2022, 3:16 PM

                                        @bob-dig said in Unable to check for updates:

                                        @bingo600 said in Unable to check for updates:

                                        @bob-dig
                                        How did you do that "image backup" ?

                                        I use a vm for pfSense.

                                        Ahh 👍

                                        If you find my answer useful - Please give the post a 👍 - "thumbs up"

                                        pfSense+ 23.05.1 (ZFS)

                                        QOTOM-Q355G4 Quad Lan.
                                        CPU  : Core i5 5250U, Ram : 8GB Kingston DDR3LV 1600
                                        LAN  : 4 x Intel 211, Disk  : 240G SAMSUNG MZ7L3240HCHQ SSD

                                        1 Reply Last reply Reply Quote 0
                                        • I
                                          Innz
                                          last edited by Innz Sep 19, 2022, 1:13 PM Sep 19, 2022, 1:08 PM

                                          Awesome! Worked on my 6100 without any issues

                                          1 Reply Last reply Reply Quote 1
                                          • G Gertjan referenced this topic on Sep 22, 2022, 9:28 AM
                                          16 out of 104
                                          • First post
                                            16/104
                                            Last post
                                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                                            This community forum collects and processes your personal information.
                                            consent.not_received