Yestereday, I was vegetating on my phone and noticed a lot of ads were being presented to me. Normally, I get minimal ads due to using Pihole...not today, though.
When I logged into the admin panel to check on it, nothing seemed amiss, until I tried to run queries against the logs. The whole admin panel seized up and would not recover, so I decided to shut down the docker instance and re-run it...it was failing. The specific error that I was focused on was, "SQLite3: statement aborts at 4: [DETACH ?] no such database: disk (1)". Now, I don't usually conduct maintenance on the Pihole instance since it's containerized (via Docker). I'm thinking that the DB got full and the container nuked it, but I didn't want to spend a lot of time troubleshooting it.
What did I do? I just created a new folder named "pihole-REBUILD" and copied my compose.yml file to it, then I ran "docker compose up -d". After that, I had to access the pihole to run a password reset command. Once that was done, I was able to log in.
Because I couldn't remember where I backed up the pihole config files, I basically have to start from scratch, but I went to https://github.com/hagezi/dns-blocklists/blob/main/sources.md and copied the blocklist sources from that URL, then posted them to Pihole as blocklists (total was 11,342,549 domains blocked).
After that, I visited a bunch of sites, trying to generate block logs...and saw nothing. I couldn't determine why the Pihole wasn't logging. I ended up doing a bunch of internet searches and found this and this.
I basically had to go to the Settings section, then the DNS section, and set the interface settings check box from "Allow only local requests to Bind only" to "Bind only to interface eth0" (this was hidden until I noticed a small "Basic" web link - clicking it changed the mode from Basic to Advanced, and I was then able to see those config options).
Once I did that, I immediately noticed that Pihole was seeing and blocking things.
I'm not sure why the DNS issue wasn't something I'd seen before, as I've been running Pihole awhile now.
I'll admit that it was super quick (relatively) to deploy a new instance of Pihole.
Instead of waiting a day for it to fail (my daughter said it failed yesterday morning - I didn't notice it until 11 PM, but I also didn't work at home yesterday). It may be time for me to look for an AM/HM Docker container setup.