[SOLVED] pfBlockerNG - Reloading unbound fails

fpv

All right, thanks for your help.

One more thing: When I ran the unbound-control command just then I was NOT logged in as admin/root, but as another user who I thought had the same rights, which does not seem to be true. Running as root gives me

unbound-control -c /var/unbound/unbound.conf status
error: SSL handshake failed
34386131464:error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed:/builder/pfsense-232/tmp/FreeBSD-src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_clnt.c:1185:

fpv

I don't know how, but a reboot seems to have fixed it. unbound doesn't throw any errors, and DNSBL work as they should.

Coornail

I had the same problem, restart didn't work for me.

What did help is that I disabled EasyPrivacy in DNSBL EasyList.

Not sure why this happened exactly, but maybe it will help people out who find this topic.

lmannyr

I had this same Error: Reloading Unbound… Failed to Reload... Restoring previous database.... Not completed.

Disabling EasyPrivacy in DNSBL EasyList also worked for me.

Using PFSense 2.4.2 p1 latest release

Superluminar

I had the same issues and found another solution:

Sometimes the certificates generated by ubound are not valid (by time/date/etc.).

Solution: delete all certificates from ubound in the folder /var/ubound/ - than restart pfsense/ubound.

noplan

same here,
after deleting

unbound_control.key
unbound_control.pem
unbound_server.key
unbound_server.pem

reboot everything worked no error in

unbound-control -c /var/unbound/unbound.conf status

alearero

@noplan said in [SOLVED] pfBlockerNG - Reloading unbound fails:

unbound-control -c /var/unbound/unbound.conf status

Hello, I am a beginner in pfsense, please can you tell me what are the commands to delete these files? or is there an interface to remove them?

alearero

@Superluminar

Hello, I am a beginner in pfsense, please can you tell me what are the commands to delete these files? or is there an interface to remove them?

noplan

rm unbound_control.key

be aware ! and understand what you are doing.

brNp

alearero

@noplan

It worked for me, thanks everyone.

noplan

cool thing !
have fun & stay safe nP

juanzelli

@noplan Many thanks. Removing those files (dated 1969) and restarting the Unbound service worked for me