[SUPPORT] pihole for unRaid - Spants repo


898 posts in this topic Last Reply

Recommended Posts

Hi there!

 

Am I the only one with problems with latest update? Had to roll it back to v5.7 to make it work again.

 

Thanks

 

EDIT:

Got it fixed deleting dns from "Extra parameters"

Captura de pantalla 2021-04-15 123852.png

Edited by Carlos
Link to post
  • Replies 897
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

See Spaceinvader One's setup video here:        I wrote the template that pulls in the Official Docker Container from PiHole. I swapped over from my unofficial one a long

Hi, I wanted to use this pihole docker as my second dns server, i already have a hardware raspberry pi as my main pihole dns, but having a backup is always good. I was wondering how i could

I just wanted to share a trick I used to have hostnames show up in the Pihole Dashboard for my local devices instead of IP addresses. Like this:     First make a copy of the /etc/

Posted Images

On 4/3/2021 at 5:39 PM, ThatNewb said:

not sure if this is the correct place to post possible bugs for unraid-pihole or pi-hole itself as I'm not sure what's the issue

 

 

upon updating to

Pi-hole v5.2.4

Web Interface v5.4

FTL v5.7

 

when pi-hole restarts the dns server automatically resets to google dns. I had set it as cloudflare. Tested a 2nd time and it reverted back to google. Unsure if I'm the only one with the issue as I have not seen it posted with a simple google search. The issue seems to only happen with restart.  Changing DNS and clicking save seems to set the DNS to the one you want.

 

I posted a bit above you about this exact same issue. 

No response. 

Have you gotten it fixed? I hate that it keeps resetting itself to Google. I don't want to use Google. 

Link to post
3 hours ago, Froberg said:

 

I posted a bit above you about this exact same issue. 

No response. 

Have you gotten it fixed? I hate that it keeps resetting itself to Google. I don't want to use Google. 

 

there was no reply to my comment 

 

Link to post

Great - thats the way to do it. 

The template is for the official Pi-hole docker, I don't make any changes so please check their github for issues.

 

I just changed the template to remove the dns entries from the extra parameters setting though as this was causing issues for some... Unfortunately this change doesnt roll down if you have already have Pihole setup. ( I dont think this fixes your issue though).

 

I will take another look tomorrow (I'm in the UK).

Link to post
On 4/6/2021 at 4:42 AM, spants said:

how did you update? Was it the docker container or inside the docker container (which you shouldn't do)?.

 

My template pulls down the official docker container with no changes. If there are bugs with Pi-hole, please log them at https://github.com/pi-hole/pi-hole/issues or https://pi-hole.net/

 

I clicked update all for all my modules at once.

 

 

I posted it to pi-hole and it's a known issue.
https://github.com/pi-hole/docker-pi-hole/issues/822

 

this seems to be the suggested fix

https://github.com/pi-hole/docker-pi-hole/actions/runs/745678042

 

though I'm unsure how to actually do it lol

Edited by ThatNewb
Link to post

I could use some expert help.  I installed a SSD cache drive and was attempting to move all docker apps off the array and onto the cache drive.  I failed.......   I have since removed all other docker apps and started again but this time installing all the apps again on the cache drive instead.  The only app that refuses to come back gracefully is Pihole Template.

 

I receive the following error running pihole after deleting and re-installing pihole-template from CA:

"Execution error

Error code 403"

 

I have tried removing pihole and ensuring that the appdata folder has been cleaned of any leftover data however each time I try to reinstall I get the same result.  When I choose to look at the logs from Pihole they are blank.  It does not appear as if anything is being written to them. Previous attempts would yield a failure stating that the address is already in use at installation time.  I no longer get that error message.  The app seems to install cleanly now but again will not start with the above error. 

 

I am really stuck and run out of talent to get this fixed.  Tried Googling the answer but I'm not really finding any help.  My Linux knowledge is very limited which doesn't help but I can get around a little.

 

I've rebooted and created a Diagnostic which I hope attaches OK.  Any help from the community would be appreciated!! 

unraid-diagnostics-20210418-1411.zip

Link to post
6 hours ago, Lichtywara said:

I could use some expert help.  I installed a SSD cache drive and was attempting to move all docker apps off the array and onto the cache drive.  I failed.......   I have since removed all other docker apps and started again but this time installing all the apps again on the cache drive instead.  The only app that refuses to come back gracefully is Pihole Template.

 

I receive the following error running pihole after deleting and re-installing pihole-template from CA:

"Execution error

Error code 403"

 

I have tried removing pihole and ensuring that the appdata folder has been cleaned of any leftover data however each time I try to reinstall I get the same result.  When I choose to look at the logs from Pihole they are blank.  It does not appear as if anything is being written to them. Previous attempts would yield a failure stating that the address is already in use at installation time.  I no longer get that error message.  The app seems to install cleanly now but again will not start with the above error. 

 

I am really stuck and run out of talent to get this fixed.  Tried Googling the answer but I'm not really finding any help.  My Linux knowledge is very limited which doesn't help but I can get around a little.

 

I've rebooted and created a Diagnostic which I hope attaches OK.  Any help from the community would be appreciated!! 

unraid-diagnostics-20210418-1411.zip 72.91 kB · 0 downloads

 

I've been reading and digging deeper.  I read that sometimes the error can occur if the port is already in use.  I SSH into Unraid and ran some checks using the lsof command to see if the Pihole ports were already in use.  None of the ports seem to be in use.

 

Next I tried changing from custom br0 (needed for Pihole to work properly) to Host.  The app then amazingly does start!!!  So I tried changing it to bridge to see what would happen which fails the same way as using custom br0.

 

So I feel like I am closer but not sure what is involved here that could be crashing Pihole in Docker immediately when those settings are used.  The IP in the previous setup is exactly identical to the current one.  Perhaps something is lingering behind so when Pihole now tries to setup/use the same settings its a bust.  I don't know where this could be.

 

 

Link to post
On 4/18/2021 at 9:04 PM, Lichtywara said:

 

I've been reading and digging deeper.  I read that sometimes the error can occur if the port is already in use.  I SSH into Unraid and ran some checks using the lsof command to see if the Pihole ports were already in use.  None of the ports seem to be in use.

 

Next I tried changing from custom br0 (needed for Pihole to work properly) to Host.  The app then amazingly does start!!!  So I tried changing it to bridge to see what would happen which fails the same way as using custom br0.

 

So I feel like I am closer but not sure what is involved here that could be crashing Pihole in Docker immediately when those settings are used.  The IP in the previous setup is exactly identical to the current one.  Perhaps something is lingering behind so when Pihole now tries to setup/use the same settings its a bust.  I don't know where this could be.

 

 

 

Anyone have an idea or a few cycles to help me out??

 

Any time I try to reinstall pihole I get the following output.  As mentioned previously I've checked TCP/UDP ports 53, UDP port 67 and TCP port 80, 443 to ensure nothing else was using them.  As I understand it ports 53 and 67 are the big ones.  Nothing is using them.  Port 443 is being utilized by nginx.  Changing any of the ports does not seem to make any difference.

 

It is as if there is some network config data still linked from the previous instance of the pihole container that did not get removed properly associated with "custom br0".  I tried changing the static IP assigned to my Unraid server also altering all the IPs manually in my other containers.  All other containers are working but pihole still breaks if I choose custom br0.

 

"root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='pihole-template' --net='br0' --ip='192.168.50.2' -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'TCP_PORT_53'='53' -e 'UDP_PORT_53'='53' -e 'UDP_PORT_67'='67' -e 'TCP_PORT_80'='80' -e 'TCP_PORT_443'='443' -e 'DNS1'='8.8.8.8' -e 'DNS2'='8.8.4.4' -e 'TZ'='America/Toronto' -e 'WEBPASSWORD'='admin' -e 'INTERFACE'='br0' -e 'ServerIP'='192.168.50.2' -e 'ServerIPv6'='' -e 'IPv6'='False' -e 'DNSMASQ_LISTENING'='all' -v '/mnt/cache/appdata/pihole/pihole/':'/etc/pihole/':'rw' -v '/mnt/cache/appdata/pihole/dnsmasq.d/':'/etc/dnsmasq.d/':'rw' --cap-add=NET_ADMIN --restart=unless-stopped 'pihole/pihole:latest'

7c9619cf37bece81f38cfae61a42e46142d727c03348dbe2b94a0795d57fc9b9
docker: Error response from daemon: Address already in use.

The command failed."

 

 

Link to post

It's 192.168.50.2 that you're assigning it that's in use by something else, in this case presumably your server since that's the SERVERIP variable you've done.  If you're running on br0, you need to assign it a unique address (and keep ServerIP pointed at your server)

Link to post
3 hours ago, Squid said:

It's 192.168.50.2 that you're assigning it that's in use by something else, in this case presumably your server since that's the SERVERIP variable you've done.  If you're running on br0, you need to assign it a unique address (and keep ServerIP pointed at your server)

 

Changed custom br0 to 192.168.50.3 and made sure the SERVER IP variable was the same.  Fired right up!  I feel a little dumb now but at least I am a dummy with less ads floating around.  :)

 

Will make the new changes in my router and I'll be back in business!!! 

 

Thank you Squid.  Your help was MUCH appreciated!

Link to post
On 4/17/2021 at 3:28 PM, ThatNewb said:

I clicked update all for all my modules at once.

 

 

I posted it to pi-hole and it's a known issue.
https://github.com/pi-hole/docker-pi-hole/issues/822

 

this seems to be the suggested fix

https://github.com/pi-hole/docker-pi-hole/actions/runs/745678042

 

though I'm unsure how to actually do it lol

As far as I know it's recommended to set up the DNS in the template and not in the Pi-hole config.

 

Cheers

Link to post

Hey, how can I access to /etc/hosts on pihole ? Folder seems not mapped on app data : https://discourse.pi-hole.net/t/how-do-i-show-hostnames-instead-of-ip-addresses-in-the-dashboard/3530

 

/etc/hosts/ > /mnt/user/appdata/pihole/hosts/

 

i added a shared volume but I start the container i have an error : bad parameter.

 

docker: Error response from daemon: OCI runtime create failed: container_linux.go:367: starting container process caused: process_linux.go:495: container init caused: rootfs_linux.go:60: mounting "/mnt/user/appdata/pihole/hosts" to rootfs at "/var/lib/docker/btrfs/subvolumes/d18b3637147cb103614bb30364157cdf203716e8baf58ae01a1068fe9b32f168/etc/hosts" caused: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type.
 

Edited by Alex.b
Link to post

What do you want to do?

 

You can either mount /etc/hosts to the container (a file not a directory, it will "overwrite" the file in the container)

You can 'docker exec -it pihole bash' to get a shell in the container and change/read the file from there

Supply an 'extra_hosts (or add-host)' to your container then docker will inject it into /etc/hosts (https://docs.docker.com/engine/reference/run/#network-settings)

Link to post

Hey,

 

i just want edit /etc/hosts on pihole container to add some IP / hostname.

 

I’ll try your last method with an extra argument.

Edited by Alex.b
Link to post
  • 3 weeks later...
Posted (edited)

I think I am in the right place.

 

I am having difficulty upgrading to the most recent template version (running 5.2.4 currently).  When I check for updates in the GUI, I see:

 

image.png.3e01aa9d1ab3017d3a319b9e436244d2.png

 

I am pointed to the repository:

https://github.com/limetech/docker-templates

 

The Github instructions seem to say that the ideal way to upgrade is to install a new Docker, but I would like to backup my settings first.  Can someone help or put me on the right path?

 

Thanks!

Edited by Chester
Link to post
1 minute ago, Chester said:

I am having difficulty upgrading to the most recent template version (running 5.2.4 currently).  When I check for updates in the GUI, I see:

Unraid 6.8.3?  Try updating to 6.9.2.

 

 

Link to post
  • 3 weeks later...
  • 3 weeks later...

Thank you for your response! I followed SpaceInvaderOne guide to setup OpenVpn - AS and Pihole. In my router settings i changed DNS to Pihole Ip address, and i installed Open Vpn on my desktop and my phone and  i imported ovpn file on both from the webgui. If not Pihole, what else for blocking ads? Thank you!

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.