Problem with pfBlockerNG and port 443 used in dns resolver.
-
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
Any help to solve this problem?
Thanks.
All the best.
-
You can revert the config change from the console menu using option 15.
-
@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?
-
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.
-
@stephenw10 Thanks!
Regards.
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.