@nogbadthebad Andy, thanks for that tip! My wife's out until this afternoon but I'll definitely look into what you suggest. I never knew you could do that on an iphone (not much of an apple guy). I'll let you guys know what I find out. Thanks again!

Try the following fix https://forum.netgate.com/topic/169610/ip-logs-are-not-being-created-populated/10

@j-lanham said in PFBlockerNG Webserver not running.: What's the best way to uninstall the current version and install the correct version? I tried installing it on my home version and the DHCP server went nuts. Uninstall, reboot, then install the devel version? It was a long time ago that I made the switch and my memory is a bit foggy. To the best of my memory I just installed the devel version. But doing a complete uninstall would not be a bad way to do it either. Just make sure that you do a full backup of your complete system first. And before uninstalling or doing an update of the current version make sure that you have the following enabled in the pfblocker settings: [image: 1646322364389-ba1e36f0-3efd-45b7-8a63-664810658e74-image.png] There is an issue with DHCP in the devel version. Once you update you should switch this setting off in DNS Resolver settings: [image: 1646322744500-8bf06834-06e2-469b-bfea-fbf086897bad-image.png] If you do have specific clients that you need to register in DNS assign them a static IP address and enable this setting in DNS Resolver: [image: 1646322862661-ead8a93d-9c88-472c-9413-b91074f535c4-image.png]

I was seeing this too but now it's downloading it again.

This is reported here: https://redmine.pfsense.org/issues/12827 Forum discussion: https://forum.netgate.com/topic/169955/latency-spikes-during-filter-reload-ce-2-6-0

I ran into this issue as well after upgrading to 2.6.0/22.01 and confirm that logging is working properly again after applying the patch. Below is a link to an updated post from @BBcan177 on Reddit: https://www.reddit.com/r/pfBlockerNG/comments/t1awl6/updated_patch_for_pfsense_2621x_ip_logging_issues/ Link to the original post on this issue for reference: https://forum.netgate.com/topic/169610/ip-logs-are-not-being-created-populated/

@gmenelau In addition to what @Gertjan mentioned above you can also click on the red lock icon to temporarily unblock the IP or domain. Sometimes it's not completely obvious what is actually keeping a webpage from working correctly and this allows you to try to figure out what you want to add more permanently to your whitelist.

@pierrelyon I'm using this list instead: https://dsi.ut-capitole.fr/blacklists/download/blacklists_for_pfsense.tar.gz Info: https://dsi.ut-capitole.fr/blacklists/ (Google Translate) To be honest, I think there is no other free list alive I'm aware of.

@bambos Hi, I would suggest you start with the set up wizard for pfBlocker-NG-devel. The learning curve for pf bocker can be steep, so go slow and read everything......twice. In addition, go to the help on your pfSense dashboard, then click pf Sense book and navagate to pf blocker package and read up. just type pf blocker in the search of the book.This will give you a good start and basic understanding.[image: 1645549741940-screenshot-from-2022-02-22-08-46-26.png][image: 1645549879322-screenshot-from-2022-02-22-09-10-59.png]

Solved - see https://forum.netgate.com/topic/170142/updated-to-22-01-sg1100-high-cpu-usage-sbin-pfctl-vvsr/16

@pftdm007 See here for a patch: https://www.reddit.com/r/pfBlockerNG/comments/sk9txi/ip_block_logging_not_working_pfsense_260rc/hvv99s1/?utm_source=reddit&utm_medium=web2x&context=3

@periko found the solution, change the DNSBL web server interface from localhost to LAN, done, thanks!!!

@clokwork said in What to whitelist to allow YouTube history?: just unsure The solution that always works : Remove all feeds (IP and DNSBL). Iterate over : => Flush local DNS cache (Micrsoft OS : ipconfig /flusdns) => Test youtube history => Add one feed => pfBlockerNG-devel full reload => reloop

I left pfBlocker up and running and everything seems fine after the update. Thanks.

@wesleywillis There is a way to order rules in pfBlocker settings, but what I find easier and clearer is for any of those type of blocks where I need to allow some, create the pfB list as Alias Native. That just creates the alias without any rules. You can then use the alias in whatever rules, NAT forward, etc. allow from Good_IP block from Bad_IPs

False alarm. Problem fixed by forcing a pfBlocker update.

@thelastunicorn LogFile? Without be a problem BrNP