Thanks for the answer.

I ended up just leaving it to run the CRON job for a day rather than forcing the update.

It cleared itself up. Sorry for the unsatisfying resolution!

@damelloman said in Pfblocker … is this normal after 3 hours of uptime:

I kept doing the wrong thing and "blocking the whole world" and didn't know HOW to do this. Thank you all for helping me understand! :) Smarter not harder!

We all as newbies did this only to learn later that it made no sense.

Solved.

Ok Thanks

:( maybe it not working with IE too?)
What dev console is saying?

@snore It depends on how many entries you want to display as well as the size of the log files.

On my pfsense I show 150 Alerts for IP and DNSBL,
I keep 100 000 lines for both IP and DNSBL log files.

It takes 10 seconds to display.

Unbound 1.9.3 will allow multiple Python modules: https://github.com/NLnetLabs/unbound/pull/6

@dragoangel That's my same thoughts as well because when I had setup mine, I didn't have to do anything special to access Google services.

@dragoangel thanks a lot it works now.

Ok this is werid, I did update after update, and reload. Decided to give up for the day and hit it tomorrow, woke up this morning to get back at it, it is working now. I did nothing from yesterday, the only thing is the cron job probably ran and that fixed it. No clue what else is in the cron job, but all has green lights and is blocking what is in my lists.

I'm not a web guy these days, but it's only blocking domains so I would think that any constructs the page is supposed to render, like frames and containers, will still be there. I suspect that it only works for static images and other simple content.

Spoke too soon, I removed ntopng, snort, darkstat and avahi and I'm still getting the IP's in pi-hole. My thoughts are not to use pi-hole or what I'm doing is wrong in some way. Also nothing connected on the LAN side at all - laptop off.

I think the obvious answer is Pfblocker or some weird interaction with pi-hole. Why I think this, I turn on another laptop WIFI'd to the router (so it's on the WAN side of pfsense and pi-hole starts seeing these IP's.

I'll take pi-hole out of the loop and put 9.9.9.9 into pfsense in the system/general DNS

@BBcan177 said in [Solved] Ad-Blocking broken after VM Host reboot:

@provels said in Ad-Blocking after VM Host reboot:

@BBcan177 Yes, that must be it. Using RAM for /var and /tmp.
Thanks for a great package!

Thanks for the feedback!
Disabling Ramdisks will solve that issue. Or just run a "Force Reload - All" after each reboot to get it all back.

Would there be a way to add a script to automate "reload all" post-reboot when using RAM disks? I also use XigmasNAS (was NAS4Free) and they have a GUI option for that (adding pre- and postinit scripts), but I would have no idea how to add that to pfSense. I'm pretty BSDumb. Maybe add

/usr/local/bin/php /usr/local/www/pfblockerng/pfblockerng.php cron >> /var/log/pfblockerng/pfblockerng.log

somewhere?
EDIT - Found this. I'll try. https://docs.netgate.com/pfsense/en/latest/development/executing-commands-at-boot-time.html

After changing the "Max Table Entries", try a Reboot.

Thanks @jdeloach for suggesting I tried the dev version it appears to work, although I feel a bit uneasy whitelisting a Cloudflare IP 😒 (not an issue with outbound of course 🙄 )

I can now confirm Pfblocker dev whitelisting works - almost as good as Pi-hole 😆