Project

General

Profile

Actions
Copy link

Bug #12365

closed

PFBlockerNG - Unbound fails to start 3.1.0

Added by D B over 2 years ago. Updated over 2 years ago.

Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
pfBlockerNG
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
2.5.2
Affected Plus Version:
Affected Architecture:
amd64

Description

Hi;

Unbound fails to start after reloading pfBlockerNG. Seems to have only started with PfBlockerNG - 3.1.0

I have tried both unbound/python modes

Python Mode:

Starting Unbound Resolver... Not completed. [ 09/11/21 11:27:41 ]
error: SSL handshake failed

Unbound Mode:
Assembling DNSBL database...... completed [ 09/11/21 11:43:06 ]
Stopping Unbound Resolver.
Unbound stopped in 2 sec.
Additional mounts:
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

Actions
Copy link

Also available in: Atom PDF