I’m sad to hear you are all having the same problem (as it seems).
I think it has to do with the following:
If you are using the PI-Hole add-on as a DHCP server for your network, please be sure your Hassio device has a static IP address. (Note: this is not the same as DHCP reservation)
If you have assigned the IP statically and still experience issues, please create an issue on the GitHub repository and add details about your installation, the add-on configuration JSON, and debug add-on output.
I’m NOT using the pihole as my DHCP server. I added the pihole IP adresse as the DNS server for my “normal” DHCP Server.
At this moment. Hassio (ResinOS) has a static IP address and a static DNS Server which is different to pihole.
So all devices in my Network received the pihole DNS server execpt hassio.
And now its working fine except the Hostname resolution in PiHole Web UI. But this is not a big deal
@wrique In my setup, hassio is now the only DHCP devices without the pihole DNS.
you can give hassio a static ip address/DNS Address by editing the resin configuration files ons the SD Card. https://docs.resin.io/deployment/network/2.x/
Any idea how this will behave if you already have Home Assistant proxied through an nginx instance (on another pi) which exposes port 80 & 443 already. Might seem like pihole running on port 80 would conflict with my nginx proxy.
I am running on port 88 as I am running HA on port 80. The “OPEN WEB UI” does not append the port number. If you manually add it, it opens fine (i.e. http://192.168.0.62:88/admin/index.php). Seems to be working ok.
@iAutom8 Answered already; nevertheless, I personally do not use port 80 of the Nginx proxy add-on. So I’ve disabled it by putting null into the field of port 80 of the Nginx add-on.
I still haven’t figured out a solution for my problem. pi hole not able to download blocklist files.
I tried setting hass io with static IP address, that didn’t help.
My system shows eth0 has IP address 172.30.33.1. Not sure if it’s relevant to my problem.
I am still getting errors when updating ad-server list… Please advice what could be going wrong for me?
[i] Target: raw.githubusercontent.com (hosts)
[i] Status: Pending…
[✗] Status: Connection Refused
[✗] List download failed: no cached list available
[i] Target: mirror1.malwaredomains.com (justdomains)
[i] Status: Pending…
[✗] Status: Connection Refused
[✗] List download failed: no cached list available
[i] Target: sysctl.org (hosts)
[i] Status: Pending…
[✗] Status: Connection Refused
[✗] List download failed: no cached list available
Nevermind this is fixed. With fixed ip Pi-hole works now fine
Hi Frenck,
Really love this add-on. Unfortunately I have some strange issue. When I first installed pi-hole 0.5 everything worked fine. But tonight I also installed DuckDNS. After this my pi doesn’t have any internet connection anymore. A lot of sensors like Buienradar, speedtest and also Nest are not functioning anymore. Also pi-hole can’t update his repositories.
I have the same issue as @jakes. Essentially pihole doesn’t block anything as the “domains on blocklist” is 0.
And i can’t update list. I get the same error.
I just performed a clean hassio install in a new SD card. Modified the resin-sample as follows:
Hey. For some reason the sensor isn’t showing up on my home screen, and adding the damn iframe basically causes my entire system to not load the Web UI for Hass. I’m running the latest version of Hassbian on a Pi3
The above example by @tanasi is faulty, which I guess a lot of people experience.
The DNS is pointing to itself, which causes issues at times Pi-Hole (dnsmasq) isn’t started yet.
Only use Pi-hole when your installation has configured a static IP. Secondly, please be sure it points to a working DNS entry and NOT ITSELF! e.g., use the DNS (IP) provided by your router, ISP or use a public one like 8.8.8.8