Pi-Hole not working after install & configuration

Help Community Help
1

:uk:/:us: Pi-hole not working after install

Hardware: Raspberry: Pi4B 8GB
YunoHost version: 4.3.6.2
Pi-hole [5.4]
Web Interface [5.6]
FTL [5.9 ]
I have access to my server : Through SSH | through the webadmin
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no
If yes, please explain: not applicable

Description of my issue

Dear community,
I installed Pi-Hole for Yunohost a few times with different combinations (3.X, last available). Currently, I am only able to install the last avaliable version, normal access is given via SSH and webUI to the raspberry as well as to other applications.
I included Upstream DNS provider as well as changed local DNS to the IP of the raspberry at my router (Fritz!Box (EN) - Pi-hole documentation).

Problems (link to error log https://tricorder.pi-hole.net/zirJ4C3t/):

Right now I have no idea how to solve this. Based on online description & guides it should be easy to use Pi-Hole with Yunohost.
So my last hope is the commnity :slight_smile:
Did anybody have similar problems? Any idea what I can try next?

I also reached out within Yunohost community (Pi-Hole not working after install & configuration - Support apps - YunoHost Forum)

Thank you in advance,
Markus

2

This should not be a problem since you have changed your lighttpd port to 8080:

-rw-r--r-- 1 root root 20 Mar  7 18:43 /etc/lighttpd/external.conf
   server.port := 8080

There is no wlan address on the Pi. Is it the Pi that is connected to wlan0 and not working, or the client devices?

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] aolcmp.122.2o7.net is 0.0.0.0 on lo (127.0.0.1)
[✗] Failed to resolve aolcmp.122.2o7.net on eth0 (192.168.1.106)
[✓] No IPv4 address available on wlan0
[✗] Failed to resolve aolcmp.122.2o7.net on docker0 (172.17.0.1)
[✓] doubleclick.com is 142.251.39.14 via a remote, public DNS server (8.8.8.8)
3

Sorry, not a good description on my end.

WiFi commtent: What I tried to say was that if I use the raspberry (with a static IP) as DNS and cut the connection of a WiFi device (e.g. phone), so that it gets the new configuration, there is now internet connection/browser pages won't load. Same result if I make the changes and restart the modem.
The raspberry is connected via LAN, not directly but via a access point: modem/Fritzbox-->OpenWRT (dumb access point)-->raspberry

Edit: just realised I did not even thank you. Sorry again.
Thank you for your input and help!

4

Just tried the DHCP in Pi-Hole. Deactivated it on the modem/Fritzbox and activated it in Pi-Hole. After reconnecting to the network no internet connection was possible. I was still able to access the modem/Fritzbox via IP and fritz.box via WiFi as well as raspberry via SSH (also WiFi).
https://tricorder.pi-hole.net/rrAk67Rs

5

Just wanted to give an update in case somebody has a similar issue. Even after fresh setup of the pi, I was not able to get either Pi-Hole (3.x or 5.x) or Adguard to work with Yunohost.
There is also a chance that the combination or Yunohost with DNS sink hole does not work or is at least not easy to configure. Higher probability of a wrong congiguration on my end :wink:

In the meantime I switched to Docker/Portainer and DNS sinkhole works :slight_smile:

6

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.