@Laxarus This worked for me as well. Though I had to search the web how to edit the file (the easiest way).

Therefore:

Addition for anyone struggling to find where to edit files on your pfsense system.

Go to Diagnostics --> Edit File --> insert the location of the file:

/usr/local/pkg/pfblockerng/pfblockerng.sh

Go to line number 1232 by filling it in the Go to line field.

That line should read:

s1="$(grep -cv ^${ip_placeholder2}$ ${masterfile})"

replace only (leave the rest intact):

masterfile

to

mastercat

Then follow the above instructions from @Laxarus https://forum.netgate.com/post/1219635

@AlexK-0 Alternatively, you can download the free IP2Location LITE database to use with pfBlockerNG.

Thanks everyone. That did it. No more errors!!

@Qinn Thank you, I just turned it back on and it is working!

@Qinn said in Feed issue on SWC:

Got a reply from Dan and here it is solved.

Thanks for feedback!

You can download it here now:

https://raw.githubusercontent.com/ianb/alexa-sites/refs/heads/master/top-1m.csv

@The-Party-of-Hell-No excellent. I’m glad some experimentation proved successful.

@mikekoke You should just set Null Block in the DNSBL Groups Summary section.
As @gertjan clearly explained, HTTPS traffic cannot be intercepted and redirected like HTTP.
This means showing a block page when accessing a blocked HTTPS domain (like stats.g.doubleclick.net) won’t work — your browser will flag a certificate error, because pfBlockerNG cannot present a valid certificate for those domains.

➡️ The recommended solution is to switch to Null blocking (logging), which silently blocks access without trying to show a redirect page.
This way, users won’t see certificate errors, and the block is still effective.

Let me know if you need help finding where to set this.

@Gertjan Thanks for the thoughts!!
I find that most Windows PCs generate more traffic in general. There is lots of app and utilities that cause the traffic.

@Uglybrian said in LibreWolf: Block Applications from Connecting to a IP (*.googleusercontent.com):

I myself just used a blocking method.

Yes, I've done this before myself in another system but keep putting it off for my current, I used pfSense pfBlockerNG configuration guide. So I decided today to get this back working. Its much easeir using granular control then generic. My system diagram is like:

Bond0 Diagram.jpg

I will be using the above quide for the Lab-pfSense. I was trying to get blocking working just using pfBlocker alone, but unsuccessful. This guide and pfSense baseline guide with VPN, Guest and VLAN support for the Bare-bone pfSense.

What do you think, any inputs and additions?