I have Pi-hole running in Docker on a Synology NAS. Everything worked well for quite some time until recently when the interface stopped responding. Also, I noticed that ad blocking no longer works.
Web UI displays
"Unable to Connect" message displays
Mhr5b2NQ
What is your configuration for the container in the Synology Docker setup?
What URL are you using to try to access the Web UI?
Does this happen with the most recent docker image? You are on an image from September of 2022.
Please, post here the compose file or docker command used to start the container.
Dan,
I'm accessing the web UI from the IP address:
http://192.168.1.16/admin/login.php
The Docker image from Synology is 20.10.3-1308. According to Synology, that is the current image.
INSTALL_WEB_INTERFACE=true
WEBPASSWORD=
QUERY_LOGGING=true
DNSMASQ_LISTENING=single
DNS_FQDN_REQUIRED=false
DNS_BOGUS_PRIV=false
DNSSEC=false
REV_SERVER=false
BLOCKING_ENABLED=true
PIHOLE_DNS_1=8.8.8.8
PIHOLE_DNS_2=2001:4860:4860:0:0:0:0:8888
PIHOLE_DNS_3=1.1.1.1
PIHOLE_DNS_4=1.0.0.1
I am using the start and restart options within Portainer.
Clicking on the container name (in Portainer interface), scroll-down to the end.
Which network are you using?
Example:
Are you using any port redirection? (you need to scroll up a little)
Example:
How are you managing Docker on the Syno? The stock Docker or via another management tool? You have some environment variables and setupVars.conf entries that are in conflict and incorrect. The way to fix things depends on how you are running Docker on Synology and what management tools you are using.
Initially, I setup Docker through the Syno interface. I switched to Portainer after setup. Everything worked well for several months before the ad-blocking failed and I lost the pi-hole web ui.
Apologies for misunderstanding your version question. I have now pulled the latest pi-hole image and recreated the container with that image. The web-ui is still unavailable.
Please, generate a new debug log and provide the token.
The Portainer config shows you are using 2 networks. The debug log shows you have 2 different IP addresses on the container, but 192.168.1.16 is not one of them:
*** [ DIAGNOSING ]: Network routing table
default via 192.168.42.1 dev eth0
192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.17
192.168.42.0/24 dev eth0 proto kernel scope link src 192.168.42.2
Try to access the web interface using http://192.168.42.2/admin/login.php or http://192.168.1.17/admin/login.php
That was the issue. I'm not sure why/how it was working for months before it stopped. I've looked back through all my setup notes and Pi-hole was always on 192.168.1.16. Thanks for the help and patience.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.