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

    22.05-RELEASE (amd64) Unable to check for updates?

    Scheduled Pinned Locked Moved General pfSense Questions
    61 Posts 6 Posters 20.2k 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.
    • TAC57T
      TAC57 @stephenw10
      last edited by

      @stephenw10 I just rebooted my pfSense SBC and now pfSense says I'm on the latest version, and I see a number of updates in my installed packages. Go figure! :-)

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

        @tac57 TBH that sounds a bit like it was in the process of installing? If you run into further issues it might be an incomplete install if you booted in the middle, meaning a reinstall might be necessary.

        To clarify, were you upgrading to 22.05 or from 22.05 to the dev version?

        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!

        TAC57T 1 Reply Last reply Reply Quote 0
        • TAC57T
          TAC57 @SteveITS
          last edited by TAC57

          @steveits Now in the process of updating pfBlockerNG-devel it's been fetching the pkg for 15 minutes and the red bar above the package reinstallation bar hasn't moved a bit.

          I wasn't updating 22.05, it just said it was unable to check.

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

            Hmm, 15mins is far longer than I'd expect for any package. Unless your WAN is very slow.

            I would check the system logs if it's still doing it.

            1 Reply Last reply Reply Quote 0
            • TAC57T
              TAC57 @stephenw10
              last edited by

              @stephenw10 I'm having this problem again. This DNS Lookout command times out after 2 minutes with Host "firmware.netgate.com" could not be resolved.

              9.9.9.9 No response
              149.112.112.112 No response

              I'm also getting the Notice:
              An error occurred while uploading the encrypted Netgate pfSense Plus configuration to https://acb.netgate.com/save ( Unable to resolve acb.netgate.com )

              I am running pfSense 23.05-RELEASE (amd64) on a Zima SBC (4GB RAM), 240GB SSD (zfs), Intel PRO/1000 PT dual port.

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

                What if you query 9.9.9.9 directly like:

                steve@steve-MacBookPro:~$ dig +short @9.9.9.9 firmware.netgate.com
                208.123.73.209
                208.123.73.207
                
                TAC57T 1 Reply Last reply Reply Quote 0
                • TAC57T
                  TAC57 @stephenw10
                  last edited by

                  @stephenw10 I entered this from the pfsense+ command line and got:

                  ;; communications error to 9.9.9.9#53: timed out
                  ;; communications error to 9.9.9.9#53: timed out
                  ;; communications error to 9.9.9.9#53: timed out
                  ;; no servers could be reached

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

                    @TAC57 if you’re forwarding to Quad9 it sounds like that isn’t working…Snort block maybe? Try turning off forwarding or use a different DNS.

                    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!

                    TAC57T 2 Replies Last reply Reply Quote 0
                    • TAC57T
                      TAC57 @SteveITS
                      last edited by

                      @SteveITS In System / General Setup / DNS Servers I changed 9.9.9.9 to 1.1.1.1 and ran the command above with @1.1.1.1 and got the following:

                      ;; communications error to 1.1.1.1#53: timed out
                      ;; communications error to 1.1.1.1#53: timed out
                      ;; communications error to 1.1.1.1#53: timed out
                      ;; no servers could be reached

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

                        Can you query either of those from a host behind pfSense?

                        TAC57T 1 Reply Last reply Reply Quote 0
                        • TAC57T
                          TAC57 @stephenw10
                          last edited by

                          @stephenw10
                          This from my windows command prompt:
                          Microsoft Windows [Version 10.0.19045.3031]
                          (c) Microsoft Corporation. All rights reserved.

                          C:\Users\Tom>ping 9.9.9.9

                          Pinging 9.9.9.9 with 32 bytes of data:
                          Reply from 9.9.9.9: bytes=32 time=266ms TTL=57
                          Reply from 9.9.9.9: bytes=32 time=15ms TTL=57
                          Reply from 9.9.9.9: bytes=32 time=15ms TTL=57
                          Reply from 9.9.9.9: bytes=32 time=16ms TTL=57

                          Ping statistics for 9.9.9.9:
                          Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
                          Approximate round trip times in milli-seconds:
                          Minimum = 15ms, Maximum = 266ms, Average = 78ms

                          C:\Users\Tom>ping 1.1.1.1

                          Pinging 1.1.1.1 with 32 bytes of data:
                          Reply from 1.1.1.1: bytes=32 time=267ms TTL=57
                          Reply from 1.1.1.1: bytes=32 time=16ms TTL=57
                          Reply from 1.1.1.1: bytes=32 time=15ms TTL=57
                          Reply from 1.1.1.1: bytes=32 time=15ms TTL=57

                          Ping statistics for 1.1.1.1:
                          Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
                          Approximate round trip times in milli-seconds:
                          Minimum = 15ms, Maximum = 267ms, Average = 78ms

                          C:\Users\Tom>ping 8.8.8.8

                          Pinging 8.8.8.8 with 32 bytes of data:
                          Reply from 8.8.8.8: bytes=32 time=14ms TTL=115
                          Reply from 8.8.8.8: bytes=32 time=13ms TTL=115
                          Reply from 8.8.8.8: bytes=32 time=14ms TTL=115
                          Reply from 8.8.8.8: bytes=32 time=14ms TTL=115

                          Ping statistics for 8.8.8.8:
                          Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
                          Approximate round trip times in milli-seconds:
                          Minimum = 13ms, Maximum = 14ms, Average = 13ms

                          C:\Users\Tom>ping acb.netgate.com

                          Pinging acb.netgate.com [208.123.73.212] with 32 bytes of data:
                          Reply from 208.123.73.212: bytes=32 time=39ms TTL=51
                          Reply from 208.123.73.212: bytes=32 time=39ms TTL=51
                          Reply from 208.123.73.212: bytes=32 time=38ms TTL=51
                          Reply from 208.123.73.212: bytes=32 time=39ms TTL=51

                          Ping statistics for 208.123.73.212:
                          Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
                          Approximate round trip times in milli-seconds:
                          Minimum = 38ms, Maximum = 39ms, Average = 38ms

                          1 Reply Last reply Reply Quote 0
                          • TAC57T
                            TAC57 @SteveITS
                            last edited by TAC57

                            @SteveITS I have DNS resolver enabled. What is the easiest way to turn all this off?

                            And this has to be related:
                            An error occurred while uploading the encrypted Netgate pfSense Plus configuration to https://acb.netgate.com/save ( Unable to resolve acb.netgate.com ) @ 2023-05-28 16:49:05

                            2988e27e-e34c-4d91-9a68-b6c85b940b33-image.png

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

                              Do you have the DNS resolver set to forwarding mode though?

                              If you do try just unchecking that so it resolves directly.

                              TAC57T 1 Reply Last reply Reply Quote 0
                              • TAC57T
                                TAC57 @stephenw10
                                last edited by

                                @stephenw10 It was, unchecking made no difference.

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

                                  Hmm. Just to be clear is that failing to resolve any host? Even when resolving directly?

                                  That sounds like it must be something blocking DNS requests from the firewall. But I expect anything doing that to apply to NAT'd traffic from clients behind it also. 🤔

                                  TAC57T 1 Reply Last reply Reply Quote 0
                                  • TAC57T
                                    TAC57 @stephenw10
                                    last edited by TAC57

                                    @stephenw10 I'm sorry but I don't understand your question. Is there a screenshot you'd like to see or some setting I can change that might solve this issue.

                                    BTW I ran the dig command from a Raspberry Pi on my network:
                                    crites@raspberrypi:~ $ dig +short @9.9.9.9 firmware.netgate.com
                                    208.123.73.207
                                    208.123.73.209

                                    crites@raspberrypi:~ $ dig +short @9.9.9.9 acb.netgate.com
                                    208.123.73.212

                                    I have a basic homelab setup with some desktop computer, TrueNAS server running Plex, and some IOT stuff.

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

                                      @TAC57 You’ve posted DNS to third party servers works from devices on LAN but not pfSense. Which implies something is blocking it. Can you post your LAN rules and any floating rules, and routes (diagnostics menu)?

                                      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!

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

                                        I meant does Diag > DNS Lookup fail for any host or just firmware.netgate.com?

                                        Are you running Snort or Suricata?

                                        TAC57T 1 Reply Last reply Reply Quote 0
                                        • TAC57T
                                          TAC57 @stephenw10
                                          last edited by

                                          @stephenw10 Before rebooting I'd get the Unable to check for updates and DNS Lookup would not report anything from any host. On rebooting pfsense it now reports on the latest version. And DNS Lookup does report back (see below) and it reports back from google.com

                                          I am running Snort.

                                          31e9cab6-c456-4848-9682-f1caa3127335-image.png

                                          1 Reply Last reply Reply Quote 0
                                          • TAC57T
                                            TAC57 @SteveITS
                                            last edited by

                                            @SteveITS I'm not running any floating rules. Can DM you my routes?

                                            LAN rules:
                                            da46e5d9-911d-4efc-87bd-eeeece0bca70-image.png

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