With zero knowledge of container/pihole I started to integrate PiHole on my UDM (minion). Mainly because i did not have a suitable Pi available. I did fall in some rookie mistakes mainly do to the following:
- do not mix tutorials with different IP-addresses for the Pi-hole
- understand on which level you put DNS reference to get separate clients
In other words RTFM. I also experienced problems that PiHole was not active after a reboot of the UDM, this was solved when I followed the manual "on-boot" steps (over the single command at this page (this error was likely again caused by previous my mistakes).
So at the moment PiHole seems to be working fine, reboots when the UDM reboots and has separate clients, so far so good. However checking the "Generate debug log" I notice some warnings/errors/X, not sure if these are normal for my setup or if I should fix them.
So that is the question. So if anyone can give me a hint most appreciated, no hurry though.
Generated token is U4kk5ImL.
*** [ INITIALIZING ] Sourcing setup variables
/etc/pihole/setupVars.conf does not exist or cannot be read.
- Based upon this topic I think I can ignore this and in later stage it probably will be removed from the debug log???
*** [ DIAGNOSING ]: Operating system
[✗] Distribution unknown -- most likely you are on an unsupported platform and may run into issues. (https://docs.pi-hole.net/main/prerequisites/)
- Not sure if the UDM/Pro/SE are already official supported but it might explain this X.
- The SSH-command for repository "podman images" gives for the PiHole:
REPOSITORY TAG IMAGE ID CREATED SIZE R/O
docker.io/pihole/pihole latest c55dbcd3e7c3 12 hours ago 316 MB false
<none> <none> 54acedb38e92 4 days ago 309 MB false
- none is the result after executing the "upd_pihole.sh" script.
- Not sure if "R/O=false" is correct or THE indication something is wrong.
*** [ DIAGNOSING ]: Networking
[✗] No IPv4 address(es) found on the interface.
[✗] No IPv6 address(es) found on the interface.
[i] Default IPv4 gateway: 192.168.5.1
* Pinging 192.168.5.1...
[✗] Gateway did not respond. (https://discourse.pi-hole.net/t/why-is-a-default-gateway-important-for-pi-hole/3546)
*** [ DIAGNOSING ]: Ports in use
[✗] udp:0.0.0.0:53 is in use by (https://docs.pi-hole.net/main/prerequisites/#ports)
[✗] udp:*:53 is in use by (https://docs.pi-hole.net/main/prerequisites/#ports)
[✗] tcp:127.0.0.1:4711 is in use by (https://docs.pi-hole.net/main/prerequisites/#ports)
[✗] tcp:0.0.0.0:80 is in use by (https://docs.pi-hole.net/main/prerequisites/#ports)
[✗] tcp:0.0.0.0:53 is in use by (https://docs.pi-hole.net/main/prerequisites/#ports)
[✗] tcp:[::1]:4711 is in use by (https://docs.pi-hole.net/main/prerequisites/#ports)
[✗] tcp:*:53 is in use by (https://docs.pi-hole.net/main/prerequisites/#ports)
- I am able to ping 192.168.5.1 from tablets, phones even from a different LAN
Other blocks with errors:
*** [ DIAGNOSING ]: Pi-hole processes
[✗] lighttpd daemon is inactive
[✗] pihole-FTL daemon is inactive
*** [ DIAGNOSING ]: Dashboard and block page
[✗] Block page X-Header: X-Header does not match or could not be retrieved.
HTTP/1.1 200 OK
Content-type: text/html; charset=UTF-8
Expires: Sat, 03 Sep 2022 09:41:12 GMT
Cache-Control: max-age=0
Date: Sat, 03 Sep 2022 09:41:12 GMT
Server: lighttpd/1.4.59
*** [ DIAGNOSING ]: contents of /etc/pihole
/etc/pihole does not exist.
*** [ DIAGNOSING ]: contents of /etc/dnsmasq.d
/etc/dnsmasq.d does not exist.
*** [ DIAGNOSING ]: contents of /etc/lighttpd
/etc/lighttpd does not exist.
*** [ DIAGNOSING ]: contents of /etc/cron.d
/etc/cron.d does not exist.
*** [ DIAGNOSING ]: contents of /var/log/lighttpd
/var/log/lighttpd does not exist.
*** [ DIAGNOSING ]: contents of /var/log/pihole
/var/log/pihole does not exist.
*** [ DIAGNOSING ]: contents of /dev/shm
/dev/shm does not exist.
*** [ DIAGNOSING ]: contents of /etc
/etc does not exist.
Details about my system:
- System: UDM (minion)
- UniFi OS Version: 1.12.24.4315
- Network: 7.2.93_18692
- Standard IP-range: 192.168.0.x (MAIN), 192.168.20.x (IoT), 192.168.30.x (NoT)
- Pi-Hole IP-address: 182.168.5.3
- Docker Tag 2022.09.1
- Pi-hole v5.12
- FTL v5.17
- Web Interface v5.14.1
Other Observations:
- I noticed a slide difference in the DNS settings between the update example and initial, likely not relevant ("--dns=1.0.0.1 " instead off "--dns=8.8.8.8 ").
- the Pi-Hole "device" is not visible in device overview of the UDM (not sure if this is normal behavior)