PFBlockerNG - Unbound fails to start 3.1.0
Unbound fails to start after reloading pfBlockerNG. Seems to have only started with PfBlockerNG - 3.1.0
I have tried both unbound/python modes
Starting Unbound Resolver... Not completed. [ 09/11/21 11:27:41 ]
error: SSL handshake failed
Assembling DNSBL database...... completed [ 09/11/21 11:43:06 ]
Stopping Unbound Resolver.
Unbound stopped in 2 sec.
No changes required.
Starting Unbound Resolver... Not completed. [ 09/11/21 11:43:43 ]
It then cycles through the IPs with seemingly no problems
Disabling PfBlockerNG allows Unbound to start and DNS to be resolved.
System Log just shows the service stopping and that's it
Please let me know if I can give any more info - I'm certainly no expert
php-fpm 52285 /status_services.php: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was ' unbound[62823:0] error: bind: address already in use  unbound[62823:0] fatal error: could not open ports'
Updated by Kris Phillips 20 days ago
- Status changed from New to Feedback
Completed the following tests:
1. Installed pfBlockerNG-dev
2. Ran a force update and reload
3. Monitored logging
I wasn't able to reproduce this problem.
Based on the error message you have it would seem that something is already bound to unbound's ports. Do you possibly have the DNS Forwarder enabled or another DNS package for pfSense? I would recommend trying to reboot to see if your problem goes away because this seems unique to your firewall install and not representative of pfSense as a whole.
If you do believe this is a bug please reply after testing again post-reboot and provide additional logging.