IPv4 using ASN returns SSL certificate problem: self-signed certificate
-
-
I forgot to mention. Don't know when this broke, but know it used to work. I running pfblockerNG 3.2.0_10 on pfsense 24.03.
-
-
@Gertjan I did a force update this morning, The pfblockerNG log file shows:
[ AS3356_Level3_hulu_v4 ] Reload [ 06/11/24 09:35:26 ] . completed ..
Empty file, Adding '127.1.7.7' to avoid download failure.[ AS11483_Conviva_hulu_v4 ] Reload . completed ..
Empty file, Adding '127.1.7.7' to avoid download failure.[ AS13335_Cloudflare_hulu_v4 ] Reload . completed ..
Empty file, Adding '127.1.7.7' to avoid download failure.[ AS15133_Edgecast_hulu_v4 ] Reload . completed ..
Empty file, Adding '127.1.7.7' to avoid download failure.[ AS22822_LimelightNetworks_v4 ] Reload . completed ..
Empty file, Adding '127.1.7.7' to avoid download failure.[ AS40027_Netflix_v4 ] Reload . completed ..
Empty file, Adding '127.1.7.7' to avoid download failure.[ AS54113_fastly_hulu_v4 ] Reload . completed ..
Empty file, Adding '127.1.7.7' to avoid download failure.and the error log shows:
[PFB_FILTER - 2] Invalid URL (not allowed2) [ AS16625 ] [ 06/10/24 09:56:14 ]
[PFB_FILTER - 2] Invalid URL (not allowed2) [ AS20940 ] [ 06/10/24 09:56:14 ]
[PFB_FILTER - 2] Invalid URL (not allowed2) [ as16625 ] [ 06/10/24 09:57:55 ]
[PFB_FILTER - 2] Invalid URL (not allowed2) [ as20940 ] [ 06/10/24 09:57:55 ]
[PFB_FILTER - 2] Invalid URL (not allowed2) [ as16625 ] [ 06/10/24 09:58:10 ]
[PFB_FILTER - 2] Invalid URL (not allowed2) [ as20940 ] [ 06/10/24 09:58:10 ]Didn't get the self signed certificate error this time.
-
@jskeen so your issue your having is the asn your trying to download are not downloading?
I tried to duplicate your problem - but working here.
What version of pfsense, what version of the pfblocker package?
Are you routing traffic through a vpn, or using an upstream proxy?
-
I'm running pfblockerNG 3.2.0_10 on pfsense 24.03. I have been doing the updates through a vpn, which has been working without a problem. I changed it to force the update out the wan, which worked.
Taking a look at the vpn logs, it has started showing some udp write errors, although the vpn channel would come up and appear to function properly. Since it works through the WAN, it must be the vpn causing the problem. Will have to take a closer look at that.
I appreciate your help! I wouldn't have suspected the vpn, if you hadn't asked the question.