Expected Behaviour:
Api should work normally, Windows Docker.
Actual Behaviour:
Crashing randomly, and hundreds of thousands of requests for the API.
(screenshot before it crashes)
Api should work normally, Windows Docker.
Crashing randomly, and hundreds of thousands of requests for the API.
(screenshot before it crashes)
Your debug log shows that you have configured Pi-hole to use a loopback address as one of its upstreams:
*** [ DIAGNOSING ]: Setup variables
(...)
PIHOLE_DNS_1=127.17.0.1
PIHOLE_DNS_2=1.1.1.1
In doing so, you've instructed Pi-hole to ask itself for DNS, i.e. you have configured an endless DNS loop.
Remove 127.17.0.1
from your Pi-hole's custom upstream DNS servers.
In addition, you should remove the custom LocaL DNS records for pi.hole
and 0.0.0.0
.
*** [ DIAGNOSING ]: contents of /etc/pihole
-rw-r--r-- 1 root root 46 Sep 22 12:11 /etc/pihole/custom.list
192.168.86.190 pi.hole
192.168.86.190 0.0.0.0
Pi-hole manages ist own name autonomically, and 0.0.0.0
is not a domain (it is an IP address).
Thanks, is there any way to remove the spam in logs without reinstalling pi-hole
You could consider to delete Pi-hole's long term query database:
Stop your Docker container
sudo rm </path/to>/pihole-FTL.db
(edit: substitute </path/to> with the actual path on your host.)
Restart your Docker container.
How on docker windows
It seems you've shared your docker run command in another post:
That command does not create any volumes or bind mounts, so your Pi-hole's data won't survive a restart.
If that is still current, stopping, removing and starting your Pi-hole container would be enough.
You can do that now, but after that, I'd recommend to line-up your installation with Pi-hole's Docker example template.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.