ENV: pfSense v2.4.3, pfBlockerNG v2.1.2_2
Please see attached screenshots..
Background: When accessing sites blocked by DNSBL, I get an SSL error: CERTIFICATE AUTHORITY INVALID error on the latest Chrome as well as Firefox browsers. As suggested by other related post on the forum, I have edited the pfBlockerNT.inc line#3630 so the pfBlockerNG/DNSBL does *not* use the DNSBL VIP; the modified line looks like: $domain_data .= "local-data: \"" . $line . " 60 IN A 0.0.0.0\"\n";
Also, I had force updated DNSBL. After making all the changes and restarting service, I still continue to get the SSL CERTIFICATE AUTHORITY INVALID ERRORS.
To @BBcan177:
I use internal self-signed CA to generates user & server certificates for openVPN purposes.
Should DNSBL be using the internal/self-signed CA Authority for creating certificates in order to avoid SSL Cert errors? I would assume that in most scenarios, the internal CA created under pfSense is setup as Trusted CA by the client machines (as it is in my home network). Having this configuration setup, would eliminate the errors mentioned.