Pi-hole on Docker not blocking ad since system upgrade. Docker and Home Assistant still running.
Your debug log shows the Pi-hole is receiving and processing DNS queries.
-----tail of pihole.log------
Sep 17 10:18:50 dnsmasq[262]: query[A] edge.microsoft.com from 192.168.1.91
Sep 17 10:18:50 dnsmasq[262]: forwarded edge.microsoft.com to 127.0.0.1#5335
Sep 17 10:18:50 dnsmasq[262]: query[HTTPS] edge.microsoft.com from 192.168.1.91
Sep 17 10:18:50 dnsmasq[262]: forwarded edge.microsoft.com to 127.0.0.1#5335
Sep 17 10:18:50 dnsmasq[262]: dnssec-query[DS] a-msedge.net to 127.0.0.1#5335
Sep 17 10:18:50 dnsmasq[262]: reply a-msedge.net is no DS
Sep 17 10:18:50 dnsmasq[262]: validation result is INSECURE
Sep 17 10:18:50 dnsmasq[262]: reply edge.microsoft.com is <CNAME>
Sep 17 10:18:50 dnsmasq[262]: reply edge-microsoft-com.dual-a-0036.a-msedge.net is <CNAME>
Sep 17 10:18:50 dnsmasq[262]: reply dual-a-0036.a-msedge.net is 13.107.21.239
Sep 17 10:18:50 dnsmasq[262]: reply dual-a-0036.a-msedge.net is 204.79.197.239
Sep 17 10:18:50 dnsmasq[262]: validation result is INSECURE
But, you do have a database problem in your gravity database:
*** [ DIAGNOSING ]: Gravity Database
-rw-rw-r-- 1 pihole pihole 60M Sep 17 10:12 /etc/pihole/gravity.db
[i] Checking integrity of /etc/pihole/gravity.db ... (this can take several minutes)
[✗] Integrity errors in /etc/pihole/gravity.db found.
row 244321 missing from index idx_gravity
I don't know how I missed that. I deleted all the adlists, flushed logs and network table, restarted the system, and reloaded the adlists. Still showing only 0.1% blocked as opposed to 17% a couple of weeks ago.
Forgot to mention that I'm using unbound but I doubt that makes a difference.
Please generate a fresh debug log and post the new token.