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

    DSNBL error: connect: Can't assign requested address for 127.0.0.1 port 953

    Scheduled Pinned Locked Moved pfBlockerNG
    37 Posts 7 Posters 12.5k 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.
    • GrimsonG
      Grimson Banned
      last edited by

      https://forum.netgate.com/topic/104772/unbound-restarting
      https://forum.netgate.com/topic/138449/unbound-restarting-more-frequently

      Also if you use the Service Watchdog package make sure it does not monitor unbound.

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

        @BBcan177 fixed my issue which was unrelated to pfblocker. Somehow my Pfsense became corrupted related to the unbound_control.key and unbound_server.pem. He got it to generate new ones that fixed unbound which in turn got Pfblocker working. We are not sure why it happened but he is reporting issues to them. Owe him for sure, great guy.

        T 1 Reply Last reply Reply Quote 0
        • T
          themadsalvi @SnowmanUT
          last edited by

          @SnowmanUT said in DSNBL error: connect: Can't assign requested address for 127.0.0.1 port 953:

          @BBcan177 fixed my issue which was unrelated to pfblocker. Somehow my Pfsense became corrupted related to the unbound_control.key and unbound_server.pem. He got it to generate new ones that fixed unbound which in turn got Pfblocker working. We are not sure why it happened but he is reporting issues to them. Owe him for sure, great guy.

          Can you please post how you were able to get it to generate new unbound_control.key and unbound_server.pem? Mine seems to have the same issue, and it doesn't resolve itself when I restore older known working configs.

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

            lol I have the same thing happening as well..

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

              @BBcan177 helped me fix it through some remote support. Not sure of the exact commands he ran on the console to fix it. If he sees this post maybe he can provide them.

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

                Hope he sees it.. I can't figure this out

                1 Reply Last reply Reply Quote 0
                • RonpfSR
                  RonpfS
                  last edited by

                  @SnowmanUT said in DSNBL error: connect: Can't assign requested address for 127.0.0.1 port 953:

                  unbound_control.key

                  Guys why don't you use the search "unbound_control.key" feature of the forum ?

                  https://forum.netgate.com/topic/106011/solved-pfblockerng-reloading-unbound-fails/12

                  Basically remove the cert files, restart unbound or reboot.

                  2.4.5-RELEASE-p1 (amd64)
                  Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
                  Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

                  F 1 Reply Last reply Reply Quote 0
                  • F
                    freebs @RonpfS
                    last edited by

                    @RonpfS I did exactly that.. removed keys firstly... didn't work.. renamed /var/unbound to unbound.bak.. restarted same thing.. very stange

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

                      fixed.. would not work on just restarting DNS.. had to reboot the box.

                      RonpfSR 1 Reply Last reply Reply Quote 0
                      • RonpfSR
                        RonpfS @freebs
                        last edited by

                        @freebs
                        Maybe save DNS Resolver settings then Apply settings would do the trick.

                        2.4.5-RELEASE-p1 (amd64)
                        Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
                        Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

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