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

    Fetching package: connection reset by peer

    Scheduled Pinned Locked Moved pfSense Packages
    89 Posts 4 Posters 17.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.
    • DaddyGoD
      DaddyGo @float
      last edited by

      @float said in Fetching package: connection reset by peer:

      "Network interfaces" doesn't work, but when I select "LAN" and "localhost" it works.

      Hmmm 😉 ✋

      Cats bury it so they can't see it!
      (You know what I mean if you have a cat)

      F 1 Reply Last reply Reply Quote 0
      • F
        float @DaddyGo
        last edited by float

        @DaddyGo Weird, I just put "ALL" again and now it works. I'll reinstall and try again.

        @stephenw10 I'll reinstall and try again.

        DaddyGoD 1 Reply Last reply Reply Quote 1
        • DaddyGoD
          DaddyGo @float
          last edited by

          @float said in Fetching package: connection reset by peer:

          I'll reinstall and try again.

          No, no, Unbound has to restart, it's such an animal

          Cats bury it so they can't see it!
          (You know what I mean if you have a cat)

          1 Reply Last reply Reply Quote 0
          • F
            float
            last edited by

            I want to know if you actually have to click on "ALL" in order to make it work. Because after I changed it to "LAN" and "localhost" it worked.

            DaddyGoD 1 Reply Last reply Reply Quote 0
            • DaddyGoD
              DaddyGo @float
              last edited by

              @float

              Don't forget that "ALL" includes the WAN!
              Unbound always restarts anyway, see DHCP leases or pfBlockerNG lists reload, etc

              Cats bury it so they can't see it!
              (You know what I mean if you have a cat)

              1 Reply Last reply Reply Quote 0
              • F
                float
                last edited by

                Then that would be the cause of my error. Weird because the default install of pfsense is "all"?

                DaddyGoD 1 Reply Last reply Reply Quote 0
                • DaddyGoD
                  DaddyGo @float
                  last edited by

                  @float

                  For me, the first is to configure the network interfaces and I don't care about the default config...

                  So I haven't even dealt with it yet

                  btw:
                  The pfSense DNS system is atom safe and works very well

                  Cats bury it so they can't see it!
                  (You know what I mean if you have a cat)

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

                    Mmm, listening for queries on 'all' should not be a problem. That's the default setting as you say.
                    Queries cannot actually come into WAN unless you have added rules to allow it.

                    Steve

                    1 Reply Last reply Reply Quote 0
                    • F
                      float
                      last edited by

                      It started working after I changed those settings and unbound restarted. This was the only option that changed.

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