Home Assistant Community Add-on: Pi-hole

Installation Home Assistant OS
,
407

THIS was the solution to my problem too. Thanks!

408

Would appear that version 4.3 isn’t taking. This is on a fresh install.

image
image2014×84 13.7 KB

409

sorry all, ive read a load of topics,but still not sure where im going wrong.
everything loads OK, however i cant access the console with my duckdns url or via the “open web UI” button?

doesnt work: https://xxx.duckdns.org:4865/
does work: https://192.168.0.xxx:4865/ ( i do get an certificate error over https)

{
  "password": "!secret pihole_password",
  "update_lists_on_start": true,
  "admin_port": 4865,
  "dns_port": 53,
  "ssl": true,
  "certfile": "fullchain.pem",
  "keyfile": "privkey.pem",
  "interface": "eth0",
  "ipv6": false,
  "ipv4_address": "",
  "ipv6_address": "",
  "virtual_host": "jamieworthing.duckdns.org",
  "hosts": [],
  "log_level": "info"
}

  - platform: pi_hole
    verify_ssl: false 
    host: localhost:4865
    monitored_conditions:
      - ads_blocked_today
      - ads_percentage_today
      - dns_queries_today
      - domains_being_blocked
      - queries_cached
      - queries_forwarded
      - unique_clients
      - unique_domains
      - clients_ever_seen
    ssl: true

log

[cont-init.d] 50-gravity.sh: exited 0.
[cont-init.d] 99-tests.sh: executing…
dnsmasq: syntax check OK.
[25-Jun-2019 12:06:30] 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] 99-tests.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[2019-06-25 12:06:30.231 1125] Using log file /var/log/pihole-FTL.log
[2019-06-25 12:06:30.232 1125] ########## FTL started! ##########
[2019-06-25 12:06:30.232 1125] FTL branch: master
[2019-06-25 12:06:30.232 1125] FTL version: v4.2.3
[2019-06-25 12:06:30.232 1125] FTL commit: aae487e-dirty
[2019-06-25 12:06:30.232 1125] FTL date: 2019-02-25 17:18:14 -0800
[2019-06-25 12:06:30.232 1125] FTL user: pihole
[2019-06-25 12:06:30.233 1125] Starting config file parsing (/etc/pihole/pihole-FTL.conf)
[2019-06-25 12:06:30.233 1125] SOCKET_LISTENING: only local
[2019-06-25 12:06:30.233 1125] AAAA_QUERY_ANALYSIS: Show AAAA queries
[2019-06-25 12:06:30.233 1125] MAXDBDAYS: max age for stored queries is 365 days
[2019-06-25 12:06:30.233 1125] RESOLVE_IPV6: Resolve IPv6 addresses
[2019-06-25 12:06:30.233 1125] RESOLVE_IPV4: Resolve IPv4 addresses
[2019-06-25 12:06:30.233 1125] DBINTERVAL: saving to DB file every minute
[2019-06-25 12:06:30.233 1125] DBFILE: Using /etc/pihole/pihole-FTL.db
[2019-06-25 12:06:30.234 1125] MAXLOGAGE: Importing up to 24.0 hours of log data
[2019-06-25 12:06:30.234 1125] PRIVACYLEVEL: Set to 0
[2019-06-25 12:06:30.235 1125] IGNORE_LOCALHOST: Show queries from localhost
[2019-06-25 12:06:30.235 1125] BLOCKINGMODE: Null IPs for blocked domains
[2019-06-25 12:06:30.235 1125] REGEX_DEBUGMODE: Inactive
[2019-06-25 12:06:30.235 1125] ANALYZE_ONLY_A_AND_AAAA: Disabled. Analyzing all queries
[2019-06-25 12:06:30.236 1125] DBIMPORT: Importing history from database
[2019-06-25 12:06:30.236 1125] PIDFILE: Using /var/run/pihole-FTL.pid
[2019-06-25 12:06:30.236 1125] PORTFILE: Using /var/run/pihole-FTL.port
[2019-06-25 12:06:30.236 1125] SOCKETFILE: Using /var/run/pihole/FTL.sock
[2019-06-25 12:06:30.236 1125] WHITELISTFILE: Using /etc/pihole/whitelist.txt
[2019-06-25 12:06:30.236 1125] BLACKLISTFILE: Using /etc/pihole/black.list
[2019-06-25 12:06:30.236 1125] GRAVITYFILE: Using /etc/pihole/gravity.list
[2019-06-25 12:06:30.236 1125] REGEXLISTFILE: Using /etc/pihole/regex.list
[2019-06-25 12:06:30.236 1125] SETUPVARSFILE: Using /etc/pihole/setupVars.conf
[2019-06-25 12:06:30.236 1125] AUDITLISTFILE: Using /etc/pihole/auditlog.list
[2019-06-25 12:06:30.236 1125] Finished config file parsing
[2019-06-25 12:06:30.238 1125] Database successfully initialized
[2019-06-25 12:06:30.239 1125] Imported 0 queries from the long-term database
[2019-06-25 12:06:30.239 1125] → Total DNS queries: 0
[2019-06-25 12:06:30.239 1125] → Cached DNS queries: 0
[2019-06-25 12:06:30.239 1125] → Forwarded DNS queries: 0
[2019-06-25 12:06:30.239 1125] → Exactly blocked DNS queries: 0
[2019-06-25 12:06:30.239 1125] → Unknown DNS queries: 0
[2019-06-25 12:06:30.239 1125] → Unique domains: 0
[2019-06-25 12:06:30.239 1125] → Unique clients: 0
[2019-06-25 12:06:30.240 1125] → Known forward destinations: 0
[2019-06-25 12:06:30.240 1125] Successfully accessed setupVars.conf
[2019-06-25 12:06:30.886 1125] WARNING: Unable to write PID to file.
[2019-06-25 12:06:30.886 1125] Continuing anyway…

410

Is there a way we can upgrade to 4.3

411

Hi there. Began using Pi-Hole in the past few days and I’m liking it a lot. One thing I’d love to implement is some redundancy in a second instance as I do reboot my HA instance every now and again. Pi-Hole (nor Adguard Home) doesn’t make this easy however it seems like some people have had success running commands via SSH etc. for other install methods.

I suspect the answer is (still) no due to how Hassio works, but is there any way for a Hassio addon instance of Pi-Hole to be interfaced with via SSH or some other means so that we could automate the synchronisation of changes from one instance to another (non Hassio instance), in particular the whitelist and blacklist. Blocklist I’m less fussed about as once the URL is setup those will sync on a schedule anyway with the remote source. Capabilities required to facilitate this would be to pull the (white/black) list, write back to the list and then force Gravity to do a sync. Even if the pull wasn’t timestamped I’m sure a staging file could be used to identify differences between the last sync. The thing I’m not sure about is how we get data in or out to begin with if Hassio is hosting Pi-Hole as an addon.

Any advice is appreciated. Built in support for multi instances seems to be on the Pi-Hole feature request which would negate the need for a more hack solution. AdGuard Home doesn’t seem to have the function either after having a quick look.

412

Found a solution for this already?
I’m switching to Hass.io but it sems i can’t use unbound.

413

I use for this reason 2 instances in 2 host, and on my computers as DNS put the IP of the 2 hosts

414

Are the two instances synchronised in that changes to a whitelist or block list are copied between the instances, or do you just apply changes to both instances separately?

No issue setting up two stand along instances, but it’d be nice to only update one and have configuration replicate to the other. Unsure how to do this when one a hass.io addon.

Right now I think I’ll need to just do seperate installs rather than as an add-on to do this.

415

No sync, just default install

416

Just noticed my config for mapping hostnames to IPs doesn’t seem to be working any more so I just get IPs. Only change I have made recently was to add a single extra entry the other day, and I didn’t pay too close of attention to whether the issues happened either side of that, but I have eyeballed the config and nothing stands out as being problematic. Reduced the hostname mapping to a single hostname + IP and that one still didn’t resolve.

Is it just me, or have other had this? I can’t tell if the DNS issues as part of Name resolution problem since 0.97.2 might be the cause. It’d coincide with me noting the problem but it may be completely unrelated.

Update 24/8: Started working again today. Haven’t touched the config in the past week for the add-on, had done multiple restarts etc but. Guessing it’s just something environmental changing. All good now anyway.

417

Release v4.0.0

Full Changelog

:tada: This is a major release of the add-on, changing and improving a lot!

:sparkles: First of all, this release introduces Ingress support. This means you can now access the interface from Home Assistant, even via the NabuCasa cloud. If you had configured a panel_iframe, you can no go ahead and remove that and check the “Show in Sidebar” toggle on the add-on page. Still, want to access the Pi-Hole web interface directly? You can always do that, by setting a port in the add-on network options.

:closed_lock_with_key: Pi-hole has single password protection (yeah, without username even), which is not really uh… Ok, we’ve improved that by adding Home Assistant authentication. You can now login with your HA username/password. However, when using Ingress, Home Assistant will take care of that for you :tada: (So this only applies to direct access).

:house_with_garden: Integrating the add-on with Home Assistant has always been a pain. We’ve solved that in this release, by adding a special endpoint for Pi-Hole integration of Home Assistant. The example in the add-on documentation is now a “copy, paste, restart & enjoy”-example. There is nothing more to it.

:globe_with_meridians: The add-on has been adjusted to work and play nicely with the new Hass.io DNS services. Should solve a lot of headaches for quite a few people.

:hammer: Changes

  • :arrow_up: Upgrades gcc/g++ to 8.3.0-r0
  • :arrow_up: Upgrades wget to 1.20.3-r0
  • :arrow_up: Upgrades Pi-hole web interface to v4.3
  • :pencil2: Maintaince -> Maintenance
  • :arrow_up: Upgrades libexecinfo-dev to 1.1-r1
  • :arrow_up: Upgrades linux-headers to 4.19.36-r0
  • :arrow_up: Upgrades nettle-dev to 3.4.1-r1
  • :fire: Removes Bash, since the base image provides it
  • :arrow_up: Upgrades bc to 1.07.1-r1
  • :arrow_up: Upgrades bind-tools to 9.14.3-r0
  • :arrow_up: Upgrades coreutils to 8.31-r0
  • :arrow_up: Upgrades git to 2.22.0-r0
  • :arrow_up: Upgrades grep to 3.3-r0
  • :arrow_up: Upgrades libcap to 2.27-r0
  • :arrow_up: Upgrades libxml2 to 2.9.9-r2
  • :arrow_up: Upgrades ncurses to 6.1_p20190518-r0
  • :arrow_up: Upgrades openssl to 1.1.1c-r0
  • :arrow_up: Upgrades perl to 5.28.2-r1
  • :arrow_up: Upgrades sed to 4.7-r0
  • :arrow_up: Upgrades sudo to 1.8.27-r0
  • :arrow_up: Upgrades Pi-hole core to v4.3.1
  • :ambulance: Fixes path handling for SSL certificates
  • :arrow_up: Upgrades add-on base image to v4.1.1
  • :arrow_up: Upgrades musl-dev to 1.1.22-r3
  • :arrow_up: Upgrades php to 7.3.8-r0
  • :arrow_up: Upgrades nginx to 1.16.1-r0
  • :arrow_up: Upgrades Pi-hole FTL to v4.3.1
  • :tractor: :hammer: Complete rewrite of the add-on
  • :books: Updates documentation to match latest changes

Questions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work: https://patreon.com/frenck

1 Like
418

Hi all, I am new to all of this…I keep getting the following message in Pi-hole:

dnsmasq: failed to create listening socket for port 53: Address in use.

Any thoughts on what I have misconfigured?

419

Maybe you have another add-on running that is using port 53 and creating the conflict. Try changing the port number in the add-on settings.

420

After updating to 4.0, i get this in the log:

[2019-08-26 20:53:09.496 761] Finished config file parsing
[2019-08-26 20:53:09.503 761] Database version is 3
[2019-08-26 20:53:09.503 761] Database successfully initialized
[2019-08-26 20:53:09.505 761] SQLite3 message: database corruption at line 65183 of [0eca3dd3d3] (11)
[2019-08-26 20:53:09.505 761] SQLite3 message: statement aborts at 4: [SELECT * FROM queries WHERE timestamp >= 1566759189] database disk image is malformed (11)
[2019-08-26 20:53:09.506 761] Imported 0 queries from the long-term database
[2019-08-26 20:53:09.506 761] read_data_from_DB() - SQL error step (11): database disk image is malformed
[2019-08-26 20:53:09.506 761] dbclose() - SQL error (5): unable to close due to unfinalized statements or unfinished backups
[2019-08-26 20:53:09.506 761] check_database(11): Disabling database connection due to error
[20:53:09] INFO: Starting NGinx....
nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html)

Also, i’m using DuckDNS addon with pi-hole, and i never get to use my duckdns domain to get into pihole, i always have to use the direct ip, else, i get a blank page with only:

“Failed Host Check: xxxxxx.duckdns.org vs 192.168.0.48, , a0d7b954-pi-hole, pi.hole, localhost, xxxxxx, xxxxxx.local”
where xxxxxx is my ducdkns domain

421

Pi_hole sensor stopped working after the update. Is this a known issue? Do we need to change the config for the update?

422

I got the same behavior.
Solved it by removing the ssl and verify ssl settings, give it a try

423

this fixed it, thanks

424

HI All. First off I want to say how much I love this add on.
I run this add on as well as another pi-hole on an older raspberry pi to block all those dns adds

One thing which occurred after upgrading to 4.0 is that I can no longer temporarily turn off pi-hole as described in this post

Essentially because there is no password, there is no API key, and running the curl commands fails.
Does anyone know of some commands to turn off pi hole without the API key, I have tried it without the key but it says “not authorised”

Thanks all

2 Likes
426

I have this same setup and I was able to make it work by just removing the API key and making it like in the example since the example doesn’t use the API key either. I can try to help more if you don’t have any luck.

428

@frenck Is there is a reason that the host UDP port 67 for DHCP is not mapped to the container?

I want to use pi-hole as DHCP server as that means, I will be able to resolve hostnames of my dhcp clients.

For now I edited the hassio addons.json file to allow UDP/67