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

    Problem with pfBlockerNG and port 443 used in dns resolver.

    Scheduled Pinned Locked Moved General pfSense Questions
    5 Posts 2 Posters 514 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.
    • E
      e0x
      last edited by

      Hi! I change the port in DNS Resolver to 443 and this generates a conflict with the package pfBlockerNG.

      Stopping Unbound Resolver
      Unbound stopped in 1 sec.
      Starting Unbound Resolver Not completed. [ 09/4/23 11:54:38 ]
      [1693828478] unbound[38166:0] error: can't bind socket: Address already in use for :: port 443
      [1693828478] unbound[38166:0] fatal error: could not open ports
      

      Captura de pantalla 2023-09-04 090239.png

      Any help to solve this problem?

      Thanks.

      All the best.

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

        You can revert the config change from the console menu using option 15.

        E 1 Reply Last reply Reply Quote 1
        • E
          e0x @stephenw10
          last edited by

          @stephenw10 HI! Thanks!

          I changed the port of the DNS resolver to 53 and do a cron job, now is working. But why change the port to 443 in DNS resolver generate conflict with pfBlockerNG?

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

            Because pfBlocker is serving pages on port 443. It replaces ads with a single pixel to make pages load correctly. Looks like the conflict is on IPv6 localhost.

            E 1 Reply Last reply Reply Quote 0
            • E
              e0x @stephenw10
              last edited by

              @stephenw10 Thanks!

              Regards.

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