Pihole is blocking ads clearly in the blacklist database and/or rules.
Actual Behaviour:
Pihole is not blocking ads but has plenty of requests. Log shows status: Unknown(0) but used to show status: Blocked (gravity) on request clearly in the blacklist database. This happened after a day of normal use.
I have tried repairing, rebooting and restarting DNS.
The Pihole is running on an Oracle cloud server (Ubuntu 20.04) and is accessed through a Wireguard tunnel. Worked perfectly until now. Nothing else is running on the server besides Wireguard and Pihole.
-rw-r--r-- 1 pihole pihole 2551224 Oct 30 13:57 /var/log/pihole.log
-----head of pihole.log------
Oct 30 00:00:01 dnsmasq[3538]: query[A] web.facebook.com from 10.66.66.2
Oct 30 00:00:01 dnsmasq[3538]: config error is REFUSED
Oct 30 00:00:01 dnsmasq[3538]: query[A] web.facebook.com from 10.66.66.2
Oct 30 00:00:01 dnsmasq[3538]: config error is REFUSED
Oct 30 00:00:13 dnsmasq[3538]: query[A] p2pal.myp2pcam.com from 10.66.66.2
Oct 30 00:00:13 dnsmasq[3538]: config error is REFUSED
Oct 30 00:00:24 dnsmasq[3538]: query[A] www.privateinternetaccess.com from 10.66.66.2
Oct 30 00:00:24 dnsmasq[3538]: config error is REFUSED
Oct 30 00:00:24 dnsmasq[3538]: query[A] serverlist.piaservers.net from 10.66.66.2
Oct 30 00:00:24 dnsmasq[3538]: config error is REFUSED
Oct 30 00:00:27 dnsmasq[3538]: query[A] piaproxy.net from 10.66.66.2
Oct 30 00:00:27 dnsmasq[3538]: config error is REFUSED
Oct 30 00:01:01 dnsmasq[3538]: query[A] web.facebook.com from 10.66.66.2
Oct 30 00:01:01 dnsmasq[3538]: config error is REFUSED
Oct 30 00:01:01 dnsmasq[3538]: query[A] web.facebook.com from 10.66.66.2
Oct 30 00:01:01 dnsmasq[3538]: config error is REFUSED
Oct 30 00:01:31 dnsmasq[3538]: query[A] ssl.google-analytics.com from 10.66.66.2
Oct 30 00:01:31 dnsmasq[3538]: gravity blocked ssl.google-analytics.com is 0.0.0.0
Oct 30 00:01:33 dnsmasq[3538]: query[A] graph.facebook.com from 10.66.66.2
Oct 30 00:01:33 dnsmasq[3538]: config error is REFUSED
server=10.66.66.1
Does that upstream work? Does the problem exist without the additional 66 blocklists added?
The upstream server (my router) used to work but I suspect that changes on the router may have crashed something.
I changed the upstream servers to OpenDNS, Google and Cloudflare in the Pihole GUI. Now everything goes through as e.g.:
2020-10-31 08:49:11 A secure.adnxs.com 10.66.66.2 OK (forwarded) CNAME (1.2ms)
And adnxs.com should be on the blacklist.
Have testet all the blocklists (50 active - 64 in total) and they all respond. The lists are either in this format: "0.0.0.0 cinektyper.blogspot.com" or "127.0.0.1 aintdoinshit.com" or in a format without preceding IP.
I have these two RegEx's on the Whitelist (local adresses - testet to work on other software):
Pretty much what it says: A network connection was refused by an upstream server (or no such server was supplied at all).
Check your group management.
Pi-hole is behaving exactly as you've configured it: Your 10.66.66.2 is assigned to your group 2 (labeled by you as Router), while all your blocklists belong to the Default group exclusively.
I doubt uBlockOrigin/uAssets/master/filters/ are in hosts format (a peek into one of them has shown it isn't). uBO is a browser extensions filtering at URL level, so those definitions won't work with Pi-hole.
Your debug log shows those entries are disabled at the moment, but you may as well remove them completely.
Those attempts at matching some private IPv4 address ranges won't do anything, as IP addresses are not queried for in DNS.
Also, you may want ot reverify your blocking strategy
Your current approach of applying some 60+ blocklists seems to force you to define over 200 whitelist regex expressions in return.
A third-party utility like yubiuser 's adlist tool could provide some insights into your actual blocklist utilisation and help you decide which blocklists to keep.
Some of your lists are not in the correct format (HOSTS) for Pi-hole and will cause a lot of problems, primarily with false positives. Remove these lists:
Thanks for your help guys. Everything is working now and as mentioned, the main reason was that I'd misunderstood the use of Groups and Clients.
/Søren