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.
    • D
      dougf4nnie
      last edited by

      Same problem here. Some other workaround?

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

        @dougf4nnie:

        Same problem here. Some other workaround?

        Is hitting save an issue?

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

          @serialdie:

          @dougf4nnie:

          Same problem here. Some other workaround?

          Is hitting save an issue?

          Yes

          Modem Draytek Vigor 130
          pfSense 2.4 Supermicro A1SRi-2558 - 8GB ECC RAM - Intel S3500 SSD 80GB - M350 Case
          Switch Cisco SG350-10
          AP Netgear R7000 (Stock FW)
          HTPC Intel NUC5i3RYH
          NAS Synology DS1515+
          NAS Synology DS213+

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

            @Wolf666:

            @serialdie:

            @dougf4nnie:

            Same problem here. Some other workaround?

            Is hitting save an issue?

            Yes

            You can go to the gui and see you have the same issue but you cant navigate to your update settings and hit save.  :o
            …..
            lol  ::)
            .....

            To answer your question I dont know of another work around.

            1 Reply Last reply Reply Quote 0
            • B
              bratell
              last edited by

              I simply rebooted and the error disappeared.  :o

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

                I am still unable to check for updates, but more importantly…how do you do a manual update??

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

                  Have you guys check this sticky post: https://forum.pfsense.org/index.php?topic=109337.0

                  EDIT: Nevermind, just had the issue after the update ;)

                  EDIT2: Go in System/Update… Choose the Update Settings tab... Select the default value which is "Follow 2.3 snapshots........" and hit "save" then go back in "System Update" and it will say you are at the current version and it also fix the dashboard...

                  Hope this help

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

                    Nope! Still "unable to check for updates" error, and no way to update manually…nice!

                    1 Reply Last reply Reply Quote 0
                    • C
                      cmb
                      last edited by

                      @jits:

                      Nope! Still "unable to check for updates" error, and no way to update manually…nice!

                      If you're still getting that at this point, you likely have connectivity issues. First guess, the system thinks it has IPv6 connectivity and it doesn't, but could be any number of things. SSH in, option 8, run:

                      pfSense-upgrade -4

                      what's that get you?

                      1 Reply Last reply Reply Quote 2
                      • J
                        jits
                        last edited by

                        wait-a-minute….I have pfblocker running and blocking all countries with only 4 exceptions. I think this could be it...be right back...

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

                          Ok..

                          PFblocker uninstalled. System rebooted. Still unable to update.

                          SSH into system, and as instructed, pfSense-upgrade -4  … This works!! System was updated. Nice!

                          However, I am still getting "unable to check for updates" in the Dashboard.

                          Again, system restarted and same thing. I am able to ping no problem to Yahoo.com, and others...

                          To recap, updating works via SSH Option 8. Does not work via dashboard, on my system anyway...

                          Jits..

                          1 Reply Last reply Reply Quote 0
                          • C
                            cmb
                            last edited by

                            Do you have IPv6 connectivity? Doesn't appear you have functional IPv6 but are preferring IPv6.

                            System>Advanced, Networking, check "Prefer IPv4 over IPv6". Reboot. Work then?

                            1 Reply Last reply Reply Quote 0
                            • D
                              dougf4nnie
                              last edited by

                              My steps:

                              1. System>Advanced, Networking, check "Prefer IPv4 over IPv6" - checked and reboted (Does not work)
                              2. I try update via ssh pfSense-upgrade -4 - Ok, system updated… But after refreshing my gui, crash reported:

                              Crash report begins.  Anonymous machine information:

                              amd64
                              10.3-RELEASE
                              FreeBSD 10.3-RELEASE #13 eac8329(RELENG_2_3): Wed Apr  6 06:20:01 CDT 2016    root@ce23-amd64-builder:/builder/pfsense/tmp/obj/builder/pfsense/tmp/FreeBSD-src/sys/pfSense

                              Crash report details:

                              PHP Errors:
                              [06-Apr-2016 23:27:32 America/Bahia] PHP Stack trace:
                              [06-Apr-2016 23:27:32 America/Bahia] PHP  1. {main}() /usr/local/www/widgets/widgets/installed_packages.widget.php:0
                              [06-Apr-2016 23:27:32 America/Bahia] PHP  2. require_once() /usr/local/www/widgets/widgets/installed_packages.widget.php:63
                              [06-Apr-2016 23:27:32 America/Bahia] PHP  3. require_once() /usr/local/www/guiconfig.inc:79
                              [06-Apr-2016 23:27:32 America/Bahia] PHP  4. include_once() /etc/inc/authgui.inc:56
                              [06-Apr-2016 23:27:32 America/Bahia] PHP Stack trace:
                              [06-Apr-2016 23:27:32 America/Bahia] PHP  1. {main}() /usr/local/www/widgets/widgets/installed_packages.widget.php:0
                              [06-Apr-2016 23:27:32 America/Bahia] PHP  2. require_once() /usr/local/www/widgets/widgets/installed_packages.widget.php:63
                              [06-Apr-2016 23:27:32 America/Bahia] PHP  3. require_once() /usr/local/www/guiconfig.inc:79
                              [06-Apr-2016 23:27:32 America/Bahia] PHP  4. include_once() /etc/inc/authgui.inc:56
                              [06-Apr-2016 23:27:32 America/Bahia] PHP Stack trace:
                              [06-Apr-2016 23:27:32 America/Bahia] PHP  1. {main}() /usr/local/www/widgets/widgets/installed_packages.widget.php:0
                              [06-Apr-2016 23:27:32 America/Bahia] PHP  2. require_once() /usr/local/www/widgets/widgets/installed_packages.widget.php:63
                              [06-Apr-2016 23:27:32 America/Bahia] PHP  3. require_once() /usr/local/www/guiconfig.inc:79
                              [06-Apr-2016 23:27:32 America/Bahia] PHP  4. session_auth() /etc/inc/authgui.inc:62
                              [06-Apr-2016 23:27:32 America/Bahia] PHP  5. session_start() /etc/inc/auth.inc:1573

                              Filename: /var/crash/minfree
                              2048

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

                                ok..

                                Checked Prefer IPv4, rebooted, and still no joy… "unable to check for updates"

                                No crash report here...

                                One more note... this system was upgraded from 2.2.6

                                1 Reply Last reply Reply Quote 0
                                • C
                                  cmb
                                  last edited by

                                  Doesn't matter whether it was upgraded. My next guess is the first server in resolv.conf isn't responding to DNS queries and the GUI doesn't wait long enough for it to get through the timeout and try enough subsequent options for it to work. What's in /etc/resolv.conf, and do all those IPs resolve beta.pfsense.org?

                                  1 Reply Last reply Reply Quote 0
                                  • A
                                    AspiringNSATroglodyte
                                    last edited by

                                    After I went to:

                                    System > Update > Update Settings

                                    and pressed save I was able to see update 2.3.r.20160406.1411_1

                                    Once I installed it I haven't had the issue happen again.

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

                                      ok..

                                      after checking resolv.conf…

                                      I have changed DNS servers to 8.8.8.8, and 8.8.4.4. Also, 127.0.0.1 will no longer be used for DNS.

                                      Then, I am able to ping beta.pfsense.org and it does resolve to IP Address and ping replies.

                                      System restarted. Still no joy...

                                      1 Reply Last reply Reply Quote 0
                                      • ?
                                        A Former User
                                        last edited by

                                        Just had this problem and hitting save on the update page worked for me. If you were to gitsync (with a dev approval) could that help get around this issue?

                                        1 Reply Last reply Reply Quote 0
                                        • D
                                          dugeem
                                          last edited by

                                          @crisdavid:

                                          Just had this problem and hitting save on the update page worked for me.

                                          This worked for me as well.

                                          1 Reply Last reply Reply Quote 0
                                          • K
                                            Koenig
                                            last edited by

                                            Having this issue as well.

                                            Hitting save in Update/Settings does nothing for me but updating via console works.

                                            This is on a fresh install, nothing but the "setup guide" has been configured  (except enabling TRIM via console)

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