(Implemented) Pi-Hole

**Iridium** · July 22, 2018 at 9:49 AM Official Post

xbmcmu No further support will be offered until ALL banned add-ons (See Here) are removed from your system.

xbmcmu · July 22, 2018 at 11:13 AM

Quote from Iridium

xbmcmu No further support will be offered until ALL banned add-ons (See Here) are removed from your system.

Huge task, but am on it. Will get back to you soon.

**Klojum** · July 22, 2018 at 11:19 AM Official Post

Quote from xbmcmu

Huge task, but am on it.

Or simply start fresh without all that crap. It's quicker that way too.

xbmcmu · July 22, 2018 at 1:51 PM

Quote from xbmcmu

Huge task, but am on it. Will get back to you soon.

Please see a new log here http://ix.io/1i4z

**Iridium** · July 22, 2018 at 5:48 PM Official Post

Can you try on a standard 8.2.5 RPi3 image and see if you get the same problem. Pi-Hole was tested on a Milhouse build but as it is Alpha and Nightly - it maybe related to LE9.

xbmcmu · July 22, 2018 at 7:12 PM

I have now created a fresh profile and got it running such that I can see the configuration GUI (see screenshot). Log here http://ix.io/1i6q

Few noob questions

The RPI2 is on a static IP.

I have set an admin password in the config window. Do any of the other settings need to be changed?

I typed in <ip address>/admin on chrome but no luck.

What needs to be done to open port 53?

**Iridium** · July 22, 2018 at 7:27 PM Official Post

Ok we are getting somewhere. Either it's LE9 or your original setup (That is my best guess) that is casing your original problem.

You shouldn't need to worry about 53 as this will just work. Try without a password and it should just work.

xbmcmu · July 22, 2018 at 7:58 PM

Am now on 8.2.5. Log here http://ix.io/1i6f

Cannot install pi-hole. Error states

Code

The dependency on os.libreelec.tv version 9.0 could not be satisfied

**aptalca** · July 23, 2018 at 1:18 PM

Quote from xbmcmu
Am now on 8.2.5. Log here http://ix.io/1i6f

Cannot install pi-hole. Error states
Code
The dependency on os.libreelec.tv version 9.0 could not be satisfied

Where did you get the addon from and what os exactly are you using?

The addon in the repo requires le 7, not 9

libreelec-addon-repo/addon.xml at master · linuxserver/libreelec-addon-repo · GitHub

**Iridium** · July 23, 2018 at 1:22 PM Official Post

Not too sure what you are doing wrong. I've just installed Pi-Hole on 8.2.5 and it works perfectly. As you've got the settings page, everything has installed. Are you sure you WAITED for the Pi-Hole contained to be downloaded at the end of the installation? It can take a while.

Was this a fresh install or an upgrade/downgrade?

punkid · July 23, 2018 at 2:10 PM

I was in a similar situation a month back, trying to get pihole working on CoreELEC.

Gave up and set up the container manually. Heres the command:

Code

docker run -d \
    --name pihole \
    --network host \
    --cap-add NET_ADMIN \
    -v "/storage/.kodi/userdata/addon_data/pihole/pihole/:/etc/pihole/" \
    -v "/storage/.kodi/userdata/addon_data/pihole/dnsmasq.d/:/etc/dnsmasq.d/" \
    -e ServerIP="192.168.1.xx" \
    -e WEBPASSWORD="yourpasswordhere" \
    -e TZ="Asia/Karachi" \
    -e IPv6="False" \
    diginc/pi-hole-multiarch:debian_armhf

Display More

Set your server IP, webpassword and timezone, then just paste the command and hit enter. Your pihole will be up and running, with a working DHCP component if you want to use that too.

The problem with my setup after doing this was that after a reboot, pihole would try to run before the network was ready, so i added a delay by doing the following:
Create 2 files:

pihole.service

Code

[Unit]
Description=pihole

[Service]
Restart=always
ExecStart=/storage/.kodi/addons/service.system.docker/bin/docker start -a pihole
ExecStop=/storage/.kodi/addons/service.system.docker/bin/docker stop -t 2 pihole

[Install]
WantedBy=multi-user.target

pihole.timer

Code

[Unit]
Description=Runs pihole

[Timer]
OnBootSec=30s
OnUnitActiveSec=12h
Unit=pihole.service

[Install]
WantedBy=multi-user.target

Then copy these files to your \Configfiles\system.d folder (i used SMB share)

FInally, run this command using SSH to enable the timer so that it starts pihole 30s after boot.

Code

systemctl enable pihole.timer

xbmcmu · July 23, 2018 at 10:22 PM

punkid Thanks. Worked like a charm. You are a star.

Iridium Thanks for the addon

xbmcmu · July 24, 2018 at 1:45 PM

Pardon my stupidity. I believe that this addon will block ads on all devices connected to my router.Is that correct?

I have it running, can see the web GUI, can see that some standard block lists are installed, but still get ads on my connected devices (eg youtube ads on android tablet). Where might I be going wrong?

**Iridium** · July 24, 2018 at 2:03 PM Official Post

Depends how you have configured your router. If you have it set so that DNS 1 is Pi-hole say 192.168.0.101 and DNS2 is Quad9 9.9.9.9 then yes. If like me - I cannot change the DNS settings in my router, you need to have your devices set to a static IP and set DNS1/2 manually.

graschbaten · November 14, 2018 at 6:40 PM

Hi @all,

How can i upgrade the piHole Docker from diginc/pi-hole to pihole/pihole?

**aptalca** · November 15, 2018 at 2:06 AM

Error moving /etc/lighttp/lighttpd.conf in fresh container on arm · Issue #308 · pi-hole/docker-pi-hole · GitHub

**Iridium** · November 15, 2018 at 9:28 AM Official Post

Quote from graschbaten

Hi @all,

How can i upgrade the piHole Docker from diginc/pi-hole to pihole/pihole?

They are the same thing - just renamed. Here

At the moment the LE addon is using pihole V 3.3 to use V4 you'll need to disable the pihole LE addon.

Download the new container:

docker pull pihole/pihole:latest

Then create and run a new script

docker run -d \

--name pihole \

-p 53:53/tcp \

-p 53:53/udp \

-p 80:80 \

-e DNS1=9.9.9.9 \

-e DNS2=149.112.112.112 \

-v /etc/localtime:/etc/localtime \

-v /storage/.config/pihole/:/etc/pihole \

-v /storage/.config/pihole/dnsmasq.d/:/etc/dnsmasq.d \

-v /storage/.config/pihole/html/:/var/www/html/html/ \

-h $(cat /etc/hostname) \

-e ServerIP=$(ip route get 9.9.9.9 | awk '{ print $NF; exit }') \

-e WEBPASSWORD=libreelec \

--restart=unless-stopped \

pihole/pihole:latest

That will get you running on 4.0. There may be issues as noted by @aptalca

punkid · November 15, 2018 at 2:13 PM

I've been running pihole in docker for a while. The v3.3 digic images worked, but since the update for 4.0, they havent worked. User Vashiru on github made a special 4.0 image which was working for me until last week when it again started giving the error.

You can try his image here: https://hub.docker.com/r/vashiru/pihole/

It might work for you, the problem may be at my end. But the pihole/pihole images do not work on LE or CE, i'm guessing it has something to do with the docker version we have (17.10)