[SUPPORT] pihole for unRaid - Spants repo


Recommended Posts

1 minute ago, dreadu said:

Low importance question here:
I just noticed today (did work last week), that the link to the support forum seems to be wrong.

 

Would you mind fixing it, when you change the template the next time?

As said before: not high prio, but simply convenient 🙂

 

They must have had a tidy up!. Will do.

Note that I dont use this anymore as I am running Adguard on my Opnsense firewall instead.

 

  • Thanks 1
Link to comment
  • 1 month later...

Hi,
Could anyone please advise how to configure the edit docker settings to use a DOH (DNS over HTTPS provider).
I would like to use the mullvad server for all upstream checks.

I've been trying to use the DOH client docker, with the following config

## Google's resolver, good ECS, good DNSSEC
#[[upstream.upstream_ietf]]
#    url = "https://doh.mullvad.net/dns-query"
#    weight = 50

## CloudFlare's resolver, bad ECS, good DNSSEC
## ECS is disabled for privacy by design: https://developers.cloudflare.com/1.1.1.1/nitty-gritty-details/#edns-c>
[[upstream.upstream_ietf]]
    url = "https://cloudflare-dns.com/dns-query"
    weight = 50

But when I enable the mullvad ones I get
HTTP error from upstream https://doh.mullvad.net/dns-query: 400 Bad Request
In the logs.
 

 

ALTERNATIVELY

Is there a way to feed the pihole container through the binhex-deluge-vpn docker?
I've got my jacket going through it. If I could feed pihole through it, I would be able to use mullvad's regular DNS they use for users on the VPN. But there's a lot more port management with pihole than there is jackett. I tried and failed.

Edited by 4554551n
Link to comment

Does anyone have problems with direct plex connection while using this container? Or different question, is there a way to add exception to dns rebind protection? It seems this container does not contain unbound service which would help with this issue as all workarounds I found cover this.

Link to comment

Help needed. I've installed Pi-hole as container using Spaceinvader's guide and it seems not to be working.

Unraid server itself is configured to use Cloudflare/Google DNS (so not relying on pi-hole)

Pi-Hole docker configured to use custom/br0 network with dedicated fixed ip address 192.168.2.201, the same for Server IP variable. 

Docker settings - Host access available is set to yes, using macvlan (the latter doesn't make much difference compared to ipvlan actually).

I can access Pi-hole WebUI, but as soon as I login into shell, I cannot ping anything out of host network (e.g. router, dns servers themselved are unavailable).

Thus DNS resolving is not available, etc.

Suppose I miss something simple here, but cannot find what.

Link to comment
49 minutes ago, gunner20163 said:

I can not, for the life of me, get docker to give my pi-hole container an ipv6 address. I set up ipv6 on my Unraids NIC as well as well as enabled custom subnet for docker.

 

My home network consists of several local networks, each with their Pi-hole DNS server which is setup for both IPv4 and IPv6.

Here are some configuration guide lines for the main interface (eth0 / br0).

 

1. Under network settings, ensure bridging and ipv4 + ipv6 is enabled

 

image.png

 

2. Under Docker settings, enable both IPv4 and IPv6 (note: IPv4 you should set a DHCP pool which does not conflict with the DHCP pool of your router)

 

image.png

image.png

 

3. Next you need to configure your Pi-hole container

 

Assign fixed IPv4 and IPv6 addresses to the pi-hole container (make sure these are valid addresses for your local network)

 

image.png

 

You need to instruct pi-hole to use these addresses for its DNS function

 

image.png

 

image.png

 

image.png

 

4. Within the Pi-hole container itself, you need to configure the DNS upstream servers for both IPv4 and IPv6. You can use either predefined upstream servers or any custom upstream servers

 

image.png

 

The last step is to configure your DHCP server (router) to provide the DNS server addresses to the clients in your network.

How to configure this depends on what router you have.

 

Here is an example of my Ubuntu PC with both IPv4 and IPv6

Note: I have configured a primary (.100) and secondary (.200) DNS server, these are two different pi-hole servers running on different hardware and are used to backup each other in case one is down

 

image.png

 

  • Like 1
Link to comment
  • 2 weeks later...

This is a very strange issue. I had pihole running on my network on a separate raspberry pi. While trying to configure the rpi as a backup server for unraid, it stopped POSTing after a restart so I had to take that raspberry pi offline and factory reset my router. I decided to make my main instance of pihole on unraid. I got the docker running however, when I access the webGUI it comes from the IP address of the raspberry pi I took offline. I didn't configure it to this IP, it's an entirely different one and won't work when I try to access it from the IP address I configure it to. there's even a new device on that IP. One that can't run pihole, it isn't even accessible for SSH. it only opens up on the raspberry pi's IP address even though that device is not on my network anymore. and that IP address got reserved to an smart home device so I shouldn't even be able to access anything on that IP address from my browser. How can I remedy this?

Edited by Renel
Link to comment
  • 1 month later...

I am running pihole as a dhcp server in my network, working fine !  I am a bit of a pureist, therefor it bugs me that pihole has a generated dns name... I can change it, but this reverts when the docker restarts.. Anyone any idea ?

 

Also: anyone any idea how to set the password to "no password" ? When I  delete it in the docker config it reverts back to "admin"

Edited by Helmonder
Link to comment
  • 3 weeks later...

I can't get the web interface to load. Can someone tell me what i did wrong here?

 

Settings are attached.

 

Logs show:

s6-rc: info: service cron: starting
s6-rc: info: service cron successfully started
s6-rc: info: service _uid-gid-changer: starting
s6-rc: info: service _uid-gid-changer successfully started
s6-rc: info: service _startup: starting
s6-rc: info: service _startup successfully started
s6-rc: info: service pihole-FTL: starting
s6-rc: info: service pihole-FTL successfully started
s6-rc: info: service lighttpd: starting
s6-rc: info: service lighttpd successfully started
s6-rc: info: service _postFTL: starting
s6-rc: info: service _postFTL successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
ServerIP is deprecated. Converting to FTLCONF_LOCAL_IPV4
  [i] Starting docker specific checks & setup for docker pihole/pihole
  [i] Setting capabilities on pihole-FTL where possible
  [i] Applying the following caps to pihole-FTL:
        * CAP_CHOWN
        * CAP_NET_BIND_SERVICE
        * CAP_NET_RAW
        * CAP_NET_ADMIN
  [i] Ensuring basic configuration by re-running select functions from basic-install.sh

  [i] Installing configs from /etc/.pihole...
  [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
  [✓] Installed /etc/dnsmasq.d/01-pihole.conf
  [✓] Installed /etc/dnsmasq.d/06-rfc6761.conf

  [i] Installing latest logrotate script...
        [i] Existing logrotate file found. No changes made.
  [i] Assigning password defined by Environment Variable
  [✓] New password set
  [i] Added ENV to php:
                    "TZ" => "America/Los_Angeles",
                    "PIHOLE_DOCKER_TAG" => "",
                    "PHP_ERROR_LOG" => "/var/log/lighttpd/error-pihole.log",
                    "CORS_HOSTS" => "",
                    "VIRTUAL_HOST" => "f611cac0d28a",
  [i] Using IPv4
  [i] Preexisting ad list /etc/pihole/adlists.list detected (exiting setup_blocklists early)
  [i] Setting DNS servers based on PIHOLE_DNS_ variable
  [i] Applying pihole-FTL.conf setting LOCAL_IPV4=192.168.1.24
  [i] FTL binding to custom interface: br0
  [i] Enabling Query Logging
  [i] Testing lighttpd config: Syntax OK
  [i] All config checks passed, cleared for startup ...
  [i] Docker start setup complete

  [i] pihole-FTL (no-daemon) will be started as root

  Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf
  [i] Neutrino emissions detected...
  [✓] Pulling blocklist source list into range

  [✓] Preparing new gravity database
  [i] Using libz compression

  [i] Target: https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
  [✓] Status: Retrieval successful
  [i] Imported 182498 domains, ignoring 1 non-domain entries
      Sample of non-domain entries:
        - 0.0.0.0
  [i] List stayed unchanged

  [✓] Creating new gravity databases
  [✓] Storing downloaded domains in new gravity database
  [✓] Building tree
  [✓] Swapping databases
  [✓] The old database remains available.
  [i] Number of gravity domains: 182498 (182498 unique domains)
  [i] Number of exact blacklisted domains: 0
  [i] Number of regex blacklist filters: 0
  [i] Number of exact whitelisted domains: 0
  [i] Number of regex whitelist filters: 0
  [✓] Cleaning up stray matter

  [✓] FTL is listening on port 53
     [✓] UDP (IPv4)
     [✓] TCP (IPv4)
     [✓] UDP (IPv6)
     [✓] TCP (IPv6)

  [✓] Pi-hole blocking is enabled

  Pi-hole version is v5.16.2 (Latest: v5.16.2)
  AdminLTE version is v5.19 (Latest: v5.19)
  FTL version is v5.22 (Latest: v5.22)
  Container tag is: 2023.03.1

 

Screenshot 2023-05-19 at 10-01-00 Tower_UpdateContainer.png

Link to comment
  • 1 month later...
On 7/18/2023 at 2:25 AM, nothus said:

I'm having the same webui access issue suddenly. No changes to the docker config but the webui ip won't connect anymore. I just tried the development-v6 branch and no luck.

 

On 5/19/2023 at 6:01 PM, tknx said:

I can't get the web interface to load. Can someone tell me what i did wrong here?

 

Settings are attached.

 

Logs show:

s6-rc: info: service cron: starting
s6-rc: info: service cron successfully started
s6-rc: info: service _uid-gid-changer: starting
s6-rc: info: service _uid-gid-changer successfully started
s6-rc: info: service _startup: starting
s6-rc: info: service _startup successfully started
s6-rc: info: service pihole-FTL: starting
s6-rc: info: service pihole-FTL successfully started
s6-rc: info: service lighttpd: starting
s6-rc: info: service lighttpd successfully started
s6-rc: info: service _postFTL: starting
s6-rc: info: service _postFTL successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
ServerIP is deprecated. Converting to FTLCONF_LOCAL_IPV4
  [i] Starting docker specific checks & setup for docker pihole/pihole
  [i] Setting capabilities on pihole-FTL where possible
  [i] Applying the following caps to pihole-FTL:
        * CAP_CHOWN
        * CAP_NET_BIND_SERVICE
        * CAP_NET_RAW
        * CAP_NET_ADMIN
  [i] Ensuring basic configuration by re-running select functions from basic-install.sh

  [i] Installing configs from /etc/.pihole...
  [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
  [✓] Installed /etc/dnsmasq.d/01-pihole.conf
  [✓] Installed /etc/dnsmasq.d/06-rfc6761.conf

  [i] Installing latest logrotate script...
        [i] Existing logrotate file found. No changes made.
  [i] Assigning password defined by Environment Variable
  [✓] New password set
  [i] Added ENV to php:
                    "TZ" => "America/Los_Angeles",
                    "PIHOLE_DOCKER_TAG" => "",
                    "PHP_ERROR_LOG" => "/var/log/lighttpd/error-pihole.log",
                    "CORS_HOSTS" => "",
                    "VIRTUAL_HOST" => "f611cac0d28a",
  [i] Using IPv4
  [i] Preexisting ad list /etc/pihole/adlists.list detected (exiting setup_blocklists early)
  [i] Setting DNS servers based on PIHOLE_DNS_ variable
  [i] Applying pihole-FTL.conf setting LOCAL_IPV4=192.168.1.24
  [i] FTL binding to custom interface: br0
  [i] Enabling Query Logging
  [i] Testing lighttpd config: Syntax OK
  [i] All config checks passed, cleared for startup ...
  [i] Docker start setup complete

  [i] pihole-FTL (no-daemon) will be started as root

  Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf
  [i] Neutrino emissions detected...
  [✓] Pulling blocklist source list into range

  [✓] Preparing new gravity database
  [i] Using libz compression

  [i] Target: https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
  [✓] Status: Retrieval successful
  [i] Imported 182498 domains, ignoring 1 non-domain entries
      Sample of non-domain entries:
        - 0.0.0.0
  [i] List stayed unchanged

  [✓] Creating new gravity databases
  [✓] Storing downloaded domains in new gravity database
  [✓] Building tree
  [✓] Swapping databases
  [✓] The old database remains available.
  [i] Number of gravity domains: 182498 (182498 unique domains)
  [i] Number of exact blacklisted domains: 0
  [i] Number of regex blacklist filters: 0
  [i] Number of exact whitelisted domains: 0
  [i] Number of regex whitelist filters: 0
  [✓] Cleaning up stray matter

  [✓] FTL is listening on port 53
     [✓] UDP (IPv4)
     [✓] TCP (IPv4)
     [✓] UDP (IPv6)
     [✓] TCP (IPv6)

  [✓] Pi-hole blocking is enabled

  Pi-hole version is v5.16.2 (Latest: v5.16.2)
  AdminLTE version is v5.19 (Latest: v5.19)
  FTL version is v5.22 (Latest: v5.22)
  Container tag is: 2023.03.1

 

Screenshot 2023-05-19 at 10-01-00 Tower_UpdateContainer.png

Same problem , that problem on /etc/resolv.conf came back... 

127.0.0.11 it's not a valid nameserver soo webui doesn't work

Link to comment
  • 4 weeks later...

seems like support in this read is dead, but here goes:

 

my pihole container stopped working some unknown amount of time ago (i have a physical backup so i only just noticed). the logs say it's working but I can't access the webgui or ping it. I tried nuking the appdata/pihole folder and rebuilding it, that didn't work either. changing the ip address also did not work.

Link to comment
  • 1 month later...
On 8/16/2023 at 2:09 PM, sage2050 said:

seems like support in this read is dead, but here goes:

 

my pihole container stopped working some unknown amount of time ago (i have a physical backup so i only just noticed). the logs say it's working but I can't access the webgui or ping it. I tried nuking the appdata/pihole folder and rebuilding it, that didn't work either. changing the ip address also did not work.

 

On 7/17/2023 at 7:25 PM, nothus said:

I'm having the same webui access issue suddenly. No changes to the docker config but the webui ip won't connect anymore. I just tried the development-v6 branch and no luck.

 

Not sure what happened to the support here, but I just ran into this issue as well. The solution is to check Unraid -> Settings -> Docker and make sure "Host access to custom networks" is enabled.  Turning that on fixed it for me.

Link to comment
12 hours ago, TapRackBang said:

 

 

Not sure what happened to the support here, but I just ran into this issue as well. The solution is to check Unraid -> Settings -> Docker and make sure "Host access to custom networks" is enabled.  Turning that on fixed it for me.

Glad you sorted it.  Support is by the users. I just created the first template that wrapped the official docker. There are other templates available. 

I don't use it. I use ubound on opnsense under proxmox.

Link to comment
  • 4 weeks later...

Why is this container all of a sudden using more than 50% of CPU Usage and jacking up the processor temperature to 140F?
I've tried reinstalling, starting from scratch, same thing.

It used to be 2% max.
What am I missing here? Does anyone have any ideas?

edit: Immediately disabling it puts everything back to normal, but obviously I want to use it :(

 

edit2: "Not sure what happened to the support here, but I just ran into this issue as well. The solution is to check Unraid -> Settings -> Docker and make sure "Host access to custom networks" is enabled.  Turning that on fixed it for me." 
This didn't work for me.

Edited by eightysixed
Additions
Link to comment
  • 2 weeks later...
On 9/30/2023 at 11:52 PM, digital_billy said:

hi guys sorry for the newb question i have Pihole installed and its working but when i try to do gravity update i get a dns error... ive been searching but i cant seem to find a solution. must be a simple setting i am missing.

i followed the guide by spaceinvader 1 on youtube but video is already  kinda outdated.

 

 

image.thumb.png.73634c1a043d866eca38963ac1118288.png

 

On 7/23/2023 at 2:15 AM, nothus said:

I thought that was an issue too, but it's Docker's network DNS.

 

On 7/20/2023 at 3:40 AM, lucas.saraiva said:

 

Same problem , that problem on /etc/resolv.conf came back... 

127.0.0.11 it's not a valid nameserver soo webui doesn't work


For those who have the problem of "DNS resolution is currently unavailable", i found a solution
image.png.f50a42f0544420c38ca30d04e5ca4628.png

 

Add --dns=127.0.0.1 on extra-settings (don't forget to activate advanced interface).

Link to comment
  • 2 weeks later...
32 minutes ago, independence said:

Hi all,

 

when I´m trying to add a new adlist, there is an error:

"While executing: attempt to write a readonly database"

 

Do you already know what went wrong?

 

Thanks

 

using the built-in filemanager in unraid, try setting the permissions for the pihole file/directories to rw to all groups/users.

 

(I no longer use it, so I cant give you the filenames unfortunately)

Link to comment

Having an issue deploying this templated container. I am choosing to provide a Fixed IP (192.168.1.20) and setting the ServerIP to this Unraid server (192.168.1.1).

 

This choice allows me to leave the required default ports. Otherwise, my other configs would block this, such as Nginx Proxy Manager for routing of multiple domain traffic.

 

When I run this container and set my laptop's DNS manually to 192.168.1.20, the Bitwarden Safari extension (pointing to the Vaultwarden container on the same Unraid) no longer functions. The Unraid UI seems to change the server-side IP address, as in the screenshot below. It starts initially with

192.168.1.20:53/TCP <--> 192.168.1.1:53

and repeated for all rows.

 

And my only fix is to restart all networking services (reboot is simpler!)

 

What am I doing wrong?

 

SCR-20231129-ngxg.thumb.png.a24b1d5effe510be6a5321ac9e3d9e54.png

Link to comment
  • 2 weeks later...

Hi i have had pihole working for a long time, but i did do an update and it broke somehow.

I got the error "DNS resolution is not available" in the log and the blocking list stats is showing -2 in the dashboard.

 

The client resolution using pihole still works... any pointers? cant seem to find a solution that works

Edited by orlando500
Link to comment
  • 2 weeks later...

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.