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

    Unable to Check For Updates

    Scheduled Pinned Locked Moved General pfSense Questions
    84 Posts 51 Posters 73.7k 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
      taius
      last edited by

      @luckman212:

      I was getting this too on a fresh 2.3.3 build earlier today.
      try getting to a console/ssh and issuing:

      pkg update -f
pkg upgrade -f

      Worked for me too.  Thanks!

      1 Reply Last reply Reply Quote 0
      • G
        ginne
        last edited by

        pkg update -f
            pkg upgrade -f

        did not help. I still have:

        2.3.3-RELEASE-p1 (i386)
        built on Thu Mar 09 07:17:43 CST 2017
        FreeBSD 10.3-RELEASE-p16

        Unable to check for updates

        Anybody an idea? Please.

        Guenther

        1 Reply Last reply Reply Quote 0
        • W
          woo
          last edited by

          Got this same issue.. Dashboard claims 'unable to check for updates'.
          I can see successful traffic to files00.netgate.com in tcpdump, and pkg update -f told me that all repositories are up to date.

          1 Reply Last reply Reply Quote 0
          • O
            oldunixguy
            last edited by

            It is happening again. I'm running 2.4.0-RC (arm)
            built on Wed Aug 23 01:13:55 CDT 2017
            FreeBSD 11.0-RELEASE-p11

            It started at least late yesterday (31 Aug 2017) and is the same now.

            oldunixguy

            {Update]
            I can do a packet capture but I'm not sure what to look for. Can you give me a hint at what the "Check for Update" transaction is like such as destination host, etc?

            oldunixguy

            1 Reply Last reply Reply Quote 0
            • S
              shastacourts
              last edited by

              Just curious,  is there a solution for this issue?  We have the same issue running 2.3-RELEASE.

              1 Reply Last reply Reply Quote 0
              • S
                shaker242
                last edited by

                pkg-static update –f
                pkg-static upgrade –f

                I'm a late upgrader, found this issue and running pkg -f  was presented with missing libssl.so.8, switched to pkg-static and the update, upgrade worked… although, I did have to reboot the pfsense server afterwards to get things up and running.

                1 Reply Last reply Reply Quote 0
                • M
                  mrpush
                  last edited by

                  Ok folks, this never addressed the issue I though it was addressing!

                  I need to connect a new PF box to the internet to get it updated.  I have its WAN interface disabled and its hooked up to my local LAN.  How do it get it to "see" the internet so i can update it???

                  My LAN is 1.x/22 (and has another PF box active as 1.1) and the new PF box is 3.1/22.

                  How in the world do i get a PF box to access the internet from just its LAN interface?????  You can't tell it to use a GATEWAY in the LAN setup and adding the existing gateway of my Lan 1.1 PF box does not work, it says "gateway IP already exists"????

                  HELP!

                  Thanks,

                  MP

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

                    @mrpush:

                    I need to connect a new PF box to the internet to get it updated.  I have its WAN interface disabled and its hooked up to my local LAN.  How do it get it to "see" the internet so i can update it??? 
                    My LAN is 1.x/22 (and has another PF box active as 1.1) and the new PF box is 3.1/22.
                    How in the world do i get a PF box to access the internet from just its LAN interface?????  You can't tell it to use a GATEWAY in the LAN setup and adding the existing gateway of my Lan 1.1 PF box does not work, it says "gateway IP already exists"????

                    ;D
                    Hook up your second pfSense as a device on the lan of the first pfSense, which is hooked up to the net.
                    Activate it's WAN interface, activate DHCP on it, and it will update, upgrade, etc.
                    Hook yourself up to the LAN of this second pfSense box to pilot it (or use the console access).

                    Think about it : a router/firewall with only one interface …. that's like a car without wheels ...

                    @mrpush:

                    Ok folks, this never addressed the issue I though it was addressing!

                    It is actually not an issue ^^

                    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
                    • M
                      mrpush
                      last edited by

                      Ok Thanks,  I think Ii get it now, Lan interface on PFS is really WAN access for clients.  So what you are saying is I must use the WAN interface for a 2nd PFS box hooked to my local LAN to get to the internet.

                      Thanks!

                      MP

                      1 Reply Last reply Reply Quote 0
                      • R
                        RoccoC
                        last edited by

                        @shaker242:

                        pkg-static update –f
                        pkg-static upgrade –f

                        I'm a late upgrader, found this issue and running pkg -f  was presented with missing libssl.so.8, switched to pkg-static and the update, upgrade worked… although, I did have to reboot the pfsense server afterwards to get things up and running.

                        My problem matched yours and this worked perfectly.  Thank you!

                        1 Reply Last reply Reply Quote 0
                        • J
                          Javik
                          last edited by

                          I don't want to be hacking around in the console, so I found another solution via the web configurator only.

                          1: 2.3.4-RELEASE-p1 (amd64): Unable to check for updates

                          2: Update Settings
                          Change to "Legacy Stable version (Security/Errata Only 2.3.x)
                          Save

                          3. System Update…
                          Current Base System: 2.3.4_1
                          Latest Base System: 2.3.5_1
                          Confirm Update: Confirm

                          4. Updating system… failed!
                          Updating repositories metadata... 2.3.5_1 is available

                          5. System Update…
                          Current Base System: 2.3.4_1
                          Latest Base System: 2.3.5_1
                          Confirm Update: Confirm

                          6. Update to 2.3.5_1 succeeds

                          7. Update settings.
                          Change back to: Latest stable version (2.4.x)
                          Save

                          8. System Update.
                          Current Base System 2.3.5_1
                          Latest Base System 2.4.2_1
                          Confirm Update: Confirm

                          9. Update to 2.4.2_1 succeeds

                          1 Reply Last reply Reply Quote 0
                          • I
                            infinityfort
                            last edited by

                            @Javik:

                            I don't want to be hacking around in the console, so I found another solution via the web configurator only.

                            1: 2.3.4-RELEASE-p1 (amd64): Unable to check for updates

                            2: Update Settings
                            Change to "Legacy Stable version (Security/Errata Only 2.3.x)
                            Save

                            3. System Update…
                            Current Base System: 2.3.4_1
                            Latest Base System: 2.3.5_1
                            Confirm Update: Confirm

                            4. Updating system… failed!
                            Updating repositories metadata... 2.3.5_1 is available

                            5. System Update…
                            Current Base System: 2.3.4_1
                            Latest Base System: 2.3.5_1
                            Confirm Update: Confirm

                            6. Update to 2.3.5_1 succeeds

                            7. Update settings.
                            Change back to: Latest stable version (2.4.x)
                            Save

                            8. System Update.
                            Current Base System 2.3.5_1
                            Latest Base System 2.4.2_1
                            Confirm Update: Confirm

                            9. Update to 2.4.2_1 succeeds

                            Thank you that worked for me just now!

                            1 Reply Last reply Reply Quote 0
                            • G
                              gatop
                              last edited by

                              @infinityfort:

                              @Javik:

                              I don't want to be hacking around in the console, so I found another solution via the web configurator only.

                              1: 2.3.4-RELEASE-p1 (amd64): Unable to check for updates

                              2: Update Settings
                              Change to "Legacy Stable version (Security/Errata Only 2.3.x)
                              Save

                              3. System Update…
                              Current Base System: 2.3.4_1
                              Latest Base System: 2.3.5_1
                              Confirm Update: Confirm

                              4. Updating system… failed!
                              Updating repositories metadata... 2.3.5_1 is available

                              5. System Update…
                              Current Base System: 2.3.4_1
                              Latest Base System: 2.3.5_1
                              Confirm Update: Confirm

                              6. Update to 2.3.5_1 succeeds

                              7. Update settings.
                              Change back to: Latest stable version (2.4.x)
                              Save

                              8. System Update.
                              Current Base System 2.3.5_1
                              Latest Base System 2.4.2_1
                              Confirm Update: Confirm

                              9. Update to 2.4.2_1 succeeds

                              Thank you that worked for me just now!

                              Awesome!
                              Just as side note, the last upgrade to 2.4.2 failed the first time, just gave the command again and then it perfectly worked.
                              Thanks a lot

                              1 Reply Last reply Reply Quote 0
                              • J
                                JJ5588
                                last edited by

                                Just wanted to come here to say I ran into this issue today when trying to update from v2.3.4-p1 as well as update the bios via a Netgate_Coreboot_Upgrade package on a netgate sg-2440. I couldn't install the Netgate_Coreboot_Upgrade package to update the bios, remove all packages before upgrading, or actually upgrade the firmware through the UI.

                                What I did:

                                • Did a backup through the UI

                                • Connected via console https://www.netgate.com/docs/pfsense/sg-2440/connect-to-console.html#connecting-to-console-port

                                • Updated the bios https://www.netgate.com/docs/pfsense/sg-2440/adi-bios-flash.html#update-manually

                                • Updated via console option 13 (I think)

                                It 'just worked' and I'm now running 2.4.3 without any issues.

                                1 Reply Last reply Reply Quote 0
                                • tittanT
                                  tittan
                                  last edited by

                                  Just go to console menu and "update from console" (option 13). After that wait for reboot and your sistem is updated and normal again.

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