[SUPPORT] pihole for unRaid - Spants repo


Recommended Posts

tried to setup as in Video and comments - still can't access the WebUI (ERR_CONNECTION_TIMED_OUT). log looks okay to me. config as default as possible - only as main dns 1.1.1. (cloudflare) and timezone changed to Berlin for close match.

 

tried with unraid OS 6.4. / 6.5.1 rc6 + 6.5.1 and blank / new docker image. with same results.

 

eth0 is set to bridge (br0) and used in config

unraidIP = 192.168.178.99

br0 of pihole as well as variable in config is set to = 192.168.178.2

 

any hint / comment will be highly appreciated.

ErrorWarningSystemArrayLogin


[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 & permissions fixes...
[fix-attrs.d] 01-resolver-resolv: applying...
[fix-attrs.d] 01-resolver-resolv: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 20-start.sh: executing...
ARCH=amd64
BASH=/bin/bash
BASHOPTS=cmdhist:complete_fullquote:extquote:force_fignore:hostcomplete:interactive_comments:progcomp:promptvars:sourcepath
BASH_ALIASES=()
BASH_ARGC=()
BASH_ARGV=()
BASH_CMDS=()
BASH_LINENO=([0]="0")
BASH_SOURCE=([0]="/var/run/s6/etc/cont-init.d/20-start.sh")
BASH_VERSINFO=([0]="4" [1]="4" [2]="12" [3]="1" [4]="release" [5]="x86_64-pc-linux-gnu")
BASH_VERSION='4.4.12(1)-release'
CWD=/
DIRSTACK=()
DNS1=1.1.1.1
DNS2=8.8.8.8
DNSMASQ_LISTENING=all
EUID=0
FTL_CMD=no-daemon

)
HOME=/root
HOSTNAME=0237214d32ba
HOSTTYPE=x86_64
HOST_OS=unRAID
IFS=$' \t\n'
INTERFACE=br0
IPv6=False
MACHTYPE=x86_64-pc-linux-gnu
OPTERR=1
OPTIND=1
OSTYPE=linux-gnu
PATH=/opt/pihole:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
PHP_ENV_CONFIG=/etc/lighttpd/conf-enabled/15-fastcgi-php.conf
PHP_ERROR_LOG=/var/log/lighttpd/error.log

PIHOLE_INSTALL=/tmp/ph_install.sh
PPID=209
PS4='+ '
PWD=/
S6OVERLAY_RELEASE=https://github.com/just-containers/s6-overlay/releases/download/v1.21.2.2/s6-overlay-amd64.tar.gz
S6_KEEP_ENV=1
SHELL=/bin/bash
SHELLOPTS=braceexpand:hashall:interactive-comments
SHLVL=1
ServerIP=192.168.178.2
TAG=debian
TCP_PORT_53=53
TCP_PORT_80=80

b
TZ=Europe/Berlin
UDP_PORT_53=53
UID=0
WEBPASSWORD=admin
_=bash
setupVars=/etc/pihole/setupVars.conf
::: Starting docker specific setup for docker diginc/pi-hole
+ [[ admin == '' ]]
+ pihole -a -p admin admin
[✓] New password set
Using custom DNS servers: 1.1.1.1 & 8.8.8.8
DNSMasq binding to custom interface: br0
Added ENV to php:
"PHP_ERROR_LOG" => "/var/log/lighttpd/error.log",

"ServerIP" => "192.168.178.2",
"VIRTUAL_HOST" => "192.168.178.2",
Using IPv4
dnsmasq: syntax check OK.
::: Testing DNSmasq config: ::: Testing lighttpd config: Syntax OK
::: All config checks passed, starting ...
::: Docker start setup complete
[i] Neutrino emissions detected...

[i] Target: raw.githubusercontent.com (hosts)

[i] Target: mirror1.malwaredomains.com (justdomains)

[i] Target: sysctl.org (hosts)

[i] Target: zeustracker.abuse.ch (blocklist.php?download=domainblocklist)

[i] Target: s3.amazonaws.com (simple_tracking.txt)

[i] Target: s3.amazonaws.com (simple_ad.txt)

[i] Target: hosts-file.net (ad_servers.txt)

[i] Number of domains being pulled in by gravity: 144878
[i] Number of unique domains trapped in the Event Horizon: 121904
[i] Nothing to whitelist!

pihole-FTL: no process found
[✓] DNS service is running
[✓] Pi-hole blocking is Enabled
[cont-init.d] 20-start.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
Starting dnsmasq
[services.d] done.
Starting crond
Starting lighttpd
Starting pihole-FTL (no-daemon)
dnsmasq: started, version 2.76 cachesize 10000

dnsmasq: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify
dnsmasq: using nameserver 8.8.8.8#53
dnsmasq: using nameserver 1.1.1.1#53
dnsmasq: read /etc/hosts - 7 addresses
dnsmasq: read /etc/pihole/local.list - 2 addresses
dnsmasq: failed to load names from /etc/pihole/black.list: No such file or directory

dnsmasq: read /etc/pihole/gravity.list - 121904 addresses
dnsmasq: 1 127.0.0.1/49609 query[A] pi.hole from 127.0.0.1
dnsmasq: 1 127.0.0.1/49609 /etc/pihole/local.list pi.hole is 192.168.178.2
dnsmasq: 2 127.0.0.1/53311 query[A] pi.hole from 127.0.0.1
dnsmasq: 2 127.0.0.1/53311 /etc/pihole/local.list pi.hole is 192.168.178.2

 

Link to comment

I can't get pihole to resolve any DNS for clients that I've pointed directly at pihole.  I'm seeing the following in the logs.

 

Quote

dnsmasq: started, version 2.76 cachesize 10000
dnsmasq: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify
dnsmasq: warning: interface br0 does not currently exist
dnsmasq: using nameserver 208.67.220.220#53
dnsmasq: using nameserver 208.67.222.222#53
dnsmasq: read /etc/hosts - 7 addresses
dnsmasq: read /etc/pihole/local.list - 2 addresses
dnsmasq: read /etc/pihole/black.list - 0 addresses
dnsmasq: read /etc/pihole/gravity.list - 121904 addresses
dnsmasq: 1 127.0.0.1/45720 query[A] pi.hole from 127.0.0.1
dnsmasq: 1 127.0.0.1/45720 /etc/pihole/local.list pi.hole is 10.0.10.22
dnsmasq: 2 127.0.0.1/49691 query[A] pi.hole from 127.0.0.1
dnsmasq: 2 127.0.0.1/49691 /etc/pihole/local.list pi.hole is 10.0.10.22
dnsmasq: 3 127.0.0.1/40105 query[A] pi.hole from 127.0.0.1
dnsmasq: 3 127.0.0.1/40105 /etc/pihole/local.list pi.hole is 10.0.10.22
dnsmasq: 4 127.0.0.1/38969 query[A] pi.hole from 127.0.0.1
dnsmasq: 4 127.0.0.1/38969 /etc/pihole/local.list pi.hole is 10.0.10.22
dnsmasq: 4 127.0.0.1/38969 query[A] pi.hole from 127.0.0.1
dnsmasq: 4 127.0.0.1/38969 /etc/pihole/local.list pi.hole is 10.0.10.22
dnsmasq: 5 127.0.0.1/42667 query[A] pi.hole from 127.0.0.1
dnsmasq: 5 127.0.0.1/42667 /etc/pihole/local.list pi.hole is 10.0.10.22
dnsmasq: 6 127.0.0.1/59706 query[A] pi.hole from 127.0.0.1
dnsmasq: 6 127.0.0.1/59706 /etc/pihole/local.list pi.hole is 10.0.10.22
dnsmasq: 7 127.0.0.1/40340 query[A] pi.hole from 127.0.0.1
dnsmasq: 7 127.0.0.1/40340 /etc/pihole/local.list pi.hole is 10.0.10.22
dnsmasq: 8 127.0.0.1/51502 query[A] pi.hole from 127.0.0.1
dnsmasq: 8 127.0.0.1/51502 /etc/pihole/local.list pi.hole is 10.0.10.22
dnsmasq: 9 127.0.0.1/49791 query[A] pi.hole from 127.0.0.1
dnsmasq: 9 127.0.0.1/49791 /etc/pihole/local.list pi.hole is 10.0.10.22
dnsmasq: 10 127.0.0.1/34480 query[A] pi.hole from 127.0.0.1
dnsmasq: 10 127.0.0.1/34480 /etc/pihole/local.list pi.hole is 10.0.10.22
dnsmasq: 10 127.0.0.1/34480 query[A] pi.hole from 127.0.0.1
dnsmasq: 10 127.0.0.1/34480 /etc/pihole/local.list pi.hole is 10.0.10.22

 

Link to comment
1 hour ago, twok said:

 

looks like your eth0 is not set to bridge. there is a comment about that from page 1 or 2.

 

I don't see any comments in the first few pages about this.  Could this be because my eth0 is bonded?   See my network settings page below:

 

EDIT:  Nvmd I decided to use pfBlockerNG in pfsense instead of Pihole.  Much simpler for my needs.

Edited by IamSpartacus
Link to comment
On 4/24/2018 at 7:32 PM, IamSpartacus said:

 

I don't see any comments in the first few pages about this.  Could this be because my eth0 is bonded?   See my network settings page below:

 

EDIT:  Nvmd I decided to use pfBlockerNG in pfsense instead of Pihole.  Much simpler for my needs.

 

I used a raspberry pi for mine, not that I had any issues with this container when I was running it, just it was sometimes a bit of a pain when my array was stopped that I lost my DNS.

Link to comment
On 4/24/2018 at 1:32 PM, IamSpartacus said:

 

I don't see any comments in the first few pages about this.  Could this be because my eth0 is bonded?   See my network settings page below:

 

EDIT:  Nvmd I decided to use pfBlockerNG in pfsense instead of Pihole.  Much simpler for my needs.

How easy was pfblockerNG?

Link to comment
25 minutes ago, IamSpartacus said:

Super easy if you already have pfSense setup.  I used this guide.  Used the pihole lists and more.

 

The main reason to go with pfBlockerNG over pihole if you already have pfSense as your router/firewall is it removes a point of failure for your network's DNS.

 

 

 

 

 

 

 

 

Yep I got already will give it a look.

Link to comment

Has anyone has any issues with PiHole taking up an insane amount of space for the Docker disk image? With PiHole enabled, it quickly eats up my Docker disk image space. It's set to 40GB, and after removing PiHole just now the usage went from 76% down to 22%. I have no idea what is causing it - I set it up following SpaceInvaderOnes guide. It works great otherwise - just destroys the space and I need to remove it to clear it up again.

 

Setup below, am I missing something?

 

image.thumb.png.51a87e2669253a0c5f05d02132b9c3b5.png

 

 

Link to comment
Yep I got already will give it a look.




Has anyone has any issues with PiHole taking up an insane amount of space for the Docker disk image? With PiHole enabled, it quickly eats up my Docker disk image space. It's set to 40GB, and after removing PiHole just now the usage went from 76% down to 22%. I have no idea what is causing it - I set it up following SpaceInvaderOnes guide. It works great otherwise - just destroys the space and I need to remove it to clear it up again.
 
Setup below, am I missing something?
 
image.thumb.png.51a87e2669253a0c5f05d02132b9c3b5.png
 
 


Yes, for some reason this container logs every single dns request to the container log and keeps it. Stop your entire docker service and turn on the log rotation and limits in the unRaid docker settings. It will keep the problem at bay.
Link to comment
4 hours ago, digiblur said:

Yes, for some reason this container logs every single dns request to the container log and keeps it. Stop your entire docker service and turn on the log rotation and limits in the unRaid docker settings. It will keep the problem at bay.

 

 

 

 

 

 

I've already got log rotation on. Here's my docker settings:

 

image.thumb.png.5a7c2e1f3657fafc75c2947570d82d4e.png

Link to comment

I installed this no problem. The only thing I had to check was the 'enable requests from all interfaces' to get it to work.

 

This is a long shot, but does anyone have both this docker and plex docker running concurrently? Now Plex won't search metadata or make matches. I am trying to watch the log, but the damn thing goes so fast I can't see any blocks. It does ask for dns to plex.tv but those are all fine. Not sure which ones its blocking that is stopping Plex from updating.

Link to comment
1 minute ago, RonUSMC said:

I installed this no problem. The only thing I had to check was the 'enable requests from all interfaces' to get it to work.

 

This is a long shot, but does anyone have both this docker and plex docker running concurrently? Now Plex won't search metadata or make matches. I am trying to watch the log, but the damn thing goes so fast I can't see any blocks. It does ask for dns to plex.tv but those are all fine. Not sure which ones its blocking that is stopping Plex from updating.

 

Yep I however do not have my unRAID using my pilhole for its DNS. Just in case you are. 

  • Like 1
Link to comment
31 minutes ago, RonUSMC said:

 

This is a long shot, but does anyone have both this docker and plex docker running concurrently?

 

Yes, I do and I see none of the Plex problems you see.  However, like kizer, I do not point unRAID to Pihole for DNS.  It is pointing straight to Cloudflare DNS whereas Pihole is the DNS for all other clients connected to the router.

  • Like 1
Link to comment
23 hours ago, kizer said:

 

Yep I however do not have my unRAID using my pilhole for its DNS. Just in case you are. 

 

I think it should be pointed out this is because if you're assigning IPs to your dockers, then UnRaid can't talk to the dockers and would not have DNS, as talked about here:

If you want Plex to talk to PiHole, you can set the DNS in the docker config. Under extra parameters, you can put in

--dns={PiHole_Address}

And that would adjust the DNS settings for Plex.

Edited by peteknot
Link to comment

Totally get it. I personally just use my PiHole Docker to serve everything else on my Network. Aka all of my other devices. 

My unRAID machine just routes straight thru and I did that to insure if any list ever gets changed that anything running on my unRAID machine never gets blocked. I thought at one time that docker updates was being blocked until I remembered I'm not using PiHole for DNS routing for my unRAID machine. :$

Link to comment

I use this docker since some weeks/months. No problems so far.

 

But since some days i noticed that if i login to the admin, it doesnt show any information.. 

 

Hows that possible? Seems to work just fine?

 

Ive read somewhere that it might be that the logs are full, but where are they? If i "console" into pi hole, i cant "move" into directorys or use vim or tail or anything.

 

Incase anyoen wonders, b efore pi hole i have another dns cache (for serving windows updates/steam and so on)

 

Is the block list too big?

1.jpg

2.jpg

Edited by nuhll
Link to comment
20 hours ago, nuhll said:

I use this docker since some weeks/months. No problems so far.

 

But since some days i noticed that if i login to the admin, it doesnt show any information.. 

 

Hows that possible? Seems to work just fine?

 

Ive read somewhere that it might be that the logs are full, but where are they? If i "console" into pi hole, i cant "move" into directorys or use vim or tail or anything.

 

Incase anyoen wonders, b efore pi hole i have another dns cache (for serving windows updates/steam and so on)

 

Is the block list too big?

1.jpg

2.jpg


I believe that I'm having the same problem. I was recently ready to burn my new unraid install because I couldn't figure this out. I previously had the stats updating but pihole itself wasn't able to update the blocklists. I deleted the docker and recreated it, now everything seems to work.. I.e. ads are being blocked, but the query #s aren't updating. i thought it was broken until I saw your post and decided to double check. At first I thought I was having network issues.. 

dnsmasq: warning: interface br0 does not currently exist

^^ Is this a problem? I'm pretty sure br0 does exist.. it's in my routing table in unraid.. Maybe the docker doesn't see it as br0?


dnsmasq: 26 127.0.0.1/51118 query[A] pi.hole from 127.0.0.1
dnsmasq: 26 127.0.0.1/51118 /etc/pihole/local.list pi.hole is 192.168.1.2

Link to comment
On 5/10/2018 at 5:49 AM, nuhll said:

From my point, if query[a] is shown, its working.

 

Its just not updating GUI (but i might bewrong)


I also have this br0 "error" in log...


After further testing.. my pihole doesn't appear to be working at all. Which additional logs should I provide? This is a brand new install following the spaceinvaderone video, same settings. 

Link to comment

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.