Updated to 3.1.0_4 a couples of minutes ago, and as usual I forgot to look at the state of unbound, and it was stopped of course. But, what I do now is doing a full reload, as I see the yellow thingy : [image: 1648572659842-2c281196-02a3-438a-a1df-2a08039ccfd5-image.png] and that will also take care of the unbound issue.

Hi, After some troubleshooting, I found out the problem was with Private DNS (dns.google) setting on the phone. Once I set it to auto, everything turned out smooth again. Thank you.

@pst said in Logging not working in 3.1.0_2: @fireodo Thank you!

@cool_corona said in pfBlockerNG-devel: Version 3.1.0_2 - Fix for #12706: @gertjan Does it matter? As https://redmine.pfsense.org/issues/12706 tells me : Description How to reproduce: 1) Install pfBlockerNG-devel, and configure DNSBL in python mode 2) Enable RAM disk for /var 3) After reboot, all files associated with pfblockerng are deleted: /var/unbound/pfb_unbound.py /var/unbound/pfb_unbound_include.inc /var/unbound/pfb_py_hsts.txt 4) ...and unbound doesn't start: But I have no RAM disks, as 'my case' is like many others : not much RAM, but loads of (SSD) disk space. So, no step 2 for me. The issue becomes a none issue. The issue is real, that's not the question.

Apparently being fixed in next release pfBlockerNG-devel v3.1.0_3: https://github.com/pfsense/FreeBSD-ports/pull/1151

@fiblimitless please ignore/delete my previous post. When Global loggings Enabled, it takes priority, and is in effect, no matter the option shows inside the log's settings. when disabled, logs show back to what you changed it to.

@scorpoin Goto the pfB logs page, select the error.log file and click on the waste bin. Do an Update, reload, All. If the error persists, wastebin the error.log file again. Remove the incriminating feed. Do an Update, reload, All.

@steveits There is no "Feeds" tab. At the top I go to: Firewall -> PFBlockerNG Then this is what I see in the image: [image: 1647646046996-pfblocker.png] You were right. I was not using the "devel" version and was on the pfBlockerNG 2.1.4_26 version. I uninstalled this and installed the devel version. Now I see all the feeds. Thank you.

The patch and a filter restart did the job - thank you!

@gertjan You are well come :) .

@felipepipers said in Block Apps over Wi-Fi (Facebook-Instagram..): And for HTTPS, some idea? There is no workaround for HTTPS. It works on HTTP because pfblocker serves up the page when it blocks a site. Since the page is unencrypted the browser just serves up the page it's given. Pfblocker acts as a Man-In-The-Middle between the browser and the intended server and injects a non-asked for page. By its design, HTTPS works by the browser verifying that the security certificate of the server it is trying to connect to is from the same domain it is intending to reach. So in pfblocker's case if it tries to serve up the blocked page the browser will not display it because it did not come from the validated server it was trying to reach. The browser then displays a security warning and won't load the page that it was served. As an aside I noticed that there is a Facebook DNSBL feed in pfblocker that I had not noticed before: [image: 1647291771427-a2a347ee-92e5-4d48-a905-66fa4c788afe-image.png]

@dma_pf Thank you! I see that I am not using DHCP Registration so I think I am good to go. Took the plunge. Noticed a few things. The memory utilization is actually higher. Not sure if there is a lot of initial work going on due to the change, but it's almost doubled from 8% of 8GB to 16%. Under reports, the DNSBL area isn't showing the blocks in red anymore even though the (DNSBL Block Event color). The background is simply white. Working as intended. I wasn't seeing the DNS Reply Events previously in unbound mode.

@patch said in PfBlockerNG Alias: Alias Native would have the same net effect, using it would involve more processing when updating the list but less processing while using the list Technically it would be the other way around, Alias Native does not look for duplicates. However you should all probably read this thread which seems to have found that Alias Deny will remove IPs found in other lists which may not be the result you want, if rules for both lists are not denying the same port.

@clokwork I just did just this at the weekend after recently installing pfBlocker as I found it was preventing visitors reaching sites via Google search. googleadservices.com # For Google search links www.googleadservices.com # For Google search links James.

Do not use top Spammer list from geo blocking Strange things are happening means that legit and clean ranges are blocked BR np