Community Add-on: Pi-hole

Tags: #<Tag:0x00007fd0768bd578> #<Tag:0x00007fd0768bd3c0>


:tada: Release v2.0.1

Full Changelog


  • Corrects incorrect permission of DHCP leases file
  • Migrates additional DNSMasq configuration on upgrade

Questions? Join our Discord server!
Enjoying my add-ons? Consider supporting my work:


I am not forwarding my 80. Do I have to do it even if I’m using direct IP address?


You might want to upgrade to the new 2.0.1 version of the add-on. This new version simplifies the ports used. See the v2.0.0 release notes above.


@frenck I checked but looks its still not showing updated version on Add-on page. The latest it showing is 1.3.0, I am in PST time zone.


There is a refresh button… top right… in the add-on store…


@frenck Refersh button worked, so I went through all installation again. Updated my password in config file. Restarted the add-on. Restarted HA to be on safe side. Now, when I click open web interface it takes me to but page is not loading. You mentioned earlier that 2.0.1 handles port differently. Do I have to expose 4865 on my router?


Duckdns domain == outside world.
If you want to expose it to the outside world, you’d need a port forward, yes.

Generally, forward the least ports possible and use hassio.local for none forwarded stuff (and disable SSL on those non-forwarded ports as well)


So I was able to get working my putting my local IP address http://local_ip_address::4865/admin in virtual host place. Thank you very much.


I’ve been curious about this for a while. I’m not able to select IPv6 upstream DNS servers. The options are grayed out. I haven’t really worried about it, but I’m seeing more and more IPv6 queries. (26%) What do I need to change to also filter these requests?


pi hole does not work for me since the updates in the last 24h. log file tell me that everything looks good but i kep getting line after line containing the following:

dnsmasq: unknown user or group: dnsmasq

i took a look at the breaking changes, and just found that I needed to add a “nice” password.

I am not using pi hole in a very fancy way, just the default settings and protect my devices manually, by adding the dns on the device of my choice. However, I am running hassio via duckdns.

any idea?


@k1282 Sorry to hear you are experiencing problems.

Could you please provide me the logs from the start until the first you’ve shown occurs?



> [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
> [s6-init] ensuring user provided files have correct perms...exited 0.
> [fix-attrs.d] applying ownership &amp; permissions fixes...
> [fix-attrs.d] 01-resolver-resolv: applying...
> [fix-attrs.d] 01-resolver-resolv: exited 0.
> [fix-attrs.d] 01-sudo: applying...
> [fix-attrs.d] 01-sudo: exited 0.
> [fix-attrs.d] 02-nginx: applying...
> [fix-attrs.d] 02-nginx: exited 0.
> [fix-attrs.d] 03-pihole: applying...
> [fix-attrs.d] 03-pihole: exited 0.
> [fix-attrs.d] done.
> [cont-init.d] executing container initialization scripts...
> [cont-init.d] executing...
> -----------------------------------------------------------
> []( Add-on: Pi-hole v2.0.1
> Network-wide ad blocking using your []( instance
> From: Community []( Add-ons
> By: Franck Nijhof &lt;[[email protected]](mailto:[email protected])&gt;
> -----------------------------------------------------------
> armhf / Resin OS 2.3.0+rev1 / HA 0.76.2 / SU 127 / stable
> -----------------------------------------------------------
> [cont-init.d] exited 0.
> [cont-init.d] executing...
> Log level is set to INFO
> [cont-init.d] exited 0.
> [cont-init.d] executing...
> INFO: You are running the latest version of this add-on
> [cont-init.d] exited 0.
> [cont-init.d] executing...
> INFO: Password is NOT in the Have I Been Pwned database! Nice!
> [cont-init.d] exited 0.
> [cont-init.d] executing...
> [cont-init.d] exited 0.
> [cont-init.d] executing...
> [cont-init.d] exited 0.
> [cont-init.d] executing...
> [cont-init.d] exited 0.
> [cont-init.d] executing...
> [cont-init.d] exited 0.
> [cont-init.d] executing...
> [cont-init.d] exited 0.
> [cont-init.d] executing...
> [✓] New password set
> [cont-init.d] exited 0.
> [cont-init.d] executing...
> [cont-init.d] exited 0.
> [cont-init.d] executing...
> [cont-init.d] exited 0.
> [cont-init.d] executing...
> [cont-init.d] exited 0.
> [cont-init.d] executing...
> [cont-init.d] exited 0.
> [cont-init.d] executing...
> dnsmasq: syntax check OK.
> [24-Aug-2018 09:07:53] NOTICE: configuration file /etc/php7/php-fpm.conf test is successful
> nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
> nginx: configuration file /etc/nginx/nginx.conf test is successful
> [cont-init.d] exited 0.
> [cont-init.d] done.
> [services.d] starting services
> [services.d] done.
> dnsmasq: unknown user or group: dnsmasq
> dnsmasq: unknown user or group: dnsmasq
> dnsmasq: unknown user or group: dnsmasq
> dnsmasq: unknown user or group: dnsmasq



After upgrading to 2.0.1, I got error:

Log Details (ERROR)

Fri Aug 24 2018 18:29:22 GMT+1000 (AUS Eastern Standard Time)

Unable to fetch data from Pi-hole

However on pi-hole log it seems to be OK, it started and it is working. Any idea please?


Thank you @k1282, meanwhile I’ve received the same issue on GitHub, you can track the issue here:


That is a weird looking error message format. Where do you get this message?
Anything in the add-on logs?


i had same issue upgrading to 2.0:
dnsmasq: unknown user or group: dnsmasq,
since i’ve upgraded to 2.1 it’s gone…
Phi-hole seems to work flawless ( not fully tested)
but the log says:
Unable to fetch data from Pi-hole


The Hassio log does not report these things. I guess you are talking about the home assistant Pi-hole component. Did you change the port number in your Component configuration?


sorry, you where right, the log it’s referred to home assistant log not!
anyway, i’ve not changed the default ports on the config, what do you mean?

“log_level”: “info”,
“password”: “***”,
“update_lists_on_start”: false,
“admin_port”: 4865,
“dns_port”: 53,
“ssl”: false,
“certfile”: “fullchain.pem”,
“keyfile”: “privkey.pem”,
“interface”: “”,
“ipv6”: true,
“ipv4_address”: “”,
“ipv6_address”: “”,
“virtual_host”: “”,
“hosts”: [],
“http_port”: 80,
“https_port”: 443


As per changelog (post above) and the breaking changes, the default admin port is now 4865. Did you change your Home Assistant pihole component configuration to match that?


Which option of the Pi-hole Sensor component should be set? Because there is no specific ‘port’-option, I assume the following should be correct?

  - platform: pi_hole
    host: localhost:4865
    location: ""

I made this assumption knowing the used Python API sets the base_url for requests in the format of {schema}://{host}/{location}/api.php.

EDIT: see frenck’s post below for the correct usage. To avoid confusion I updated my example as well.