Disregard

Edited October 15, 20205 yr by tucansam

Are you sure 192.168.1.100 is not assigned to an other device (by your router).

 

And the ServerIP variable should be the IP of your Unraid server

Can you ping the IP from within unraid? (Or an other docker container?)

On 10/25/2020 at 12:08 AM, Alex.b said:

Hello,

I don't understand what IP should I use. I run my unraid server on 192.168.1.9. I put a random address the for the pile-hole docker (.100), but I can't access to the addess :

 

For Pihole container find Spaceinvader One videos on YouTube and you will install it very easy.He explained very well everything.

 

I installed this a few weeks ago and it has been running well as far as I know, but in troubleshooting another issue I noticed that under the Docker tab > Log it was showing 'unhealthy'.  In the log it was showing the following messages over and over until I stopped it:

 

Stopping lighttpd
lighttpd: no process found
Starting pihole-FTL (no-daemon) as root
Starting lighttpd
Stopping pihole-FTL
Stopping lighttpd
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
lighttpd: no process found
Starting pihole-FTL (no-daemon) as root
Starting lighttpd
Stopping pihole-FTL
Stopping lighttpd
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
lighttpd: no process found
Starting lighttpd
Starting pihole-FTL (no-daemon) as root
Stopping pihole-FTL
Stopping lighttpd
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
lighttpd: no process found
Starting lighttpd
Starting pihole-FTL (no-daemon) as root
Stopping pihole-FTL
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
Stopping lighttpd
lighttpd: no process found
Starting lighttpd
Starting pihole-FTL (no-daemon) as root
Stopping pihole-FTL
Stopping lighttpd
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
lighttpd: no process found
Starting lighttpd
Starting pihole-FTL (no-daemon) as root
Stopping pihole-FTL
Stopping lighttpd
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
lighttpd: no process found
Starting lighttpd
Starting pihole-FTL (no-daemon) as root
Stopping pihole-FTL
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
Stopping lighttpd
lighttpd: no process found
Starting pihole-FTL (no-daemon) as root
Starting lighttpd
Stopping pihole-FTL
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
Stopping lighttpd
lighttpd: no process found
Stopping cron
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

 

Edited November 16, 20205 yr by Unraiding

@Unraiding Both of my Piholes are running ok (sorry, but I know that doesn't help you!). There seems to be a number of people using pihole that have had similar messages in the past with pihole. Most just reinstall.

I guess the easiest way is to use the SETTINGS/teleporter function to save your settings, stop pihole, delete files in the data directory, reinstall and load settings back in using teleporter.

 

The docker is the official one from Pihole with no changes - so you can also post on their github page. (there does seem to be similar messages there https://github.com/pi-hole/docker-pi-hole)

Unrelated to any problems for the official pihole docker (my template has no tweaks, its just vanilla), @testdasi has produced a nice version with DOT/DOH baked in. It is worth a try for more security & piece of mind.

10 hours ago, spants said:

@Unraiding Both of my Piholes are running ok (sorry, but I know that doesn't help you!). There seems to be a number of people using pihole that have had similar messages in the past with pihole. Most just reinstall.

I guess the easiest way is to use the SETTINGS/teleporter function to save your settings, stop pihole, delete files in the data directory, reinstall and load settings back in using teleporter.

 

The docker is the official one from Pihole with no changes - so you can also post on their github page. (there does seem to be similar messages there https://github.com/pi-hole/docker-pi-hole)

Thanks.  It ended up falling apart completely when I stopped it and got stuck in a 'dead' status.   I had to delete my docker image and reinstall everything to get it running again.  I decided not to reinstall PiHole for now...

ok, thats a shame. If you did not have any extra rules setup then it is easy to reinstall. I couldn't operate without it now!.

Is there a way to view the query log by device (either MAC or IP)? My kids are getting older and while I mostly trust them, I would like the option to view sites they go to on their devices.

Hi, i dont know if I am right here,

i dont know why but my oihole stopped working with this strange message in settings.

I dont know what to do. Even reinstalling does not do anything.

 

 

 

Edited December 8, 20205 yr by zw3ist3in

I try to follow the video but i cant choose Custum br0: in the list and therefore cant assign the ip..

I think i'm getting more and more confused as I try to figure it out.

Has it something to do with the routing table? (bridging is enabled)

 

 

Edited December 21, 20205 yr by BrianK

On 11/24/2020 at 4:48 PM, thunderclap said:

Is there a way to view the query log by device (either MAC or IP)? My kids are getting older and while I mostly trust them, I would like the option to view sites they go to on their devices.

"I mostly trust my kids, but I actually don't and want to be Big Brother"

Dude, what?

 

No you can't. Pihole can only resolve and log DNS requests, it doesn't track any more information that what is already shown. DNS requests don't give the entire url of websites you visit. There are ways to do what you want but not with Pihole.

So, maybe Im loosing my mind as I just got to this docker plug.. but I cant even change the password. Ideas?

On 12/24/2020 at 10:10 PM, HarshReality said:

So, maybe Im loosing my mind as I just got to this docker plug.. but I cant even change the password. Ideas?

Password randomly created on install.  Go to the docker page, click on the Pihole item and select "Console".

 

From that pop-up, run the following command:

pihole -a -p

You can then reset (or remove) the password.

I've been running pi-hole for years mostly issue free but yesterday it died on me. I've had some recent disk errors that were traced back to SATA controller issues and hopefully were resolved with the last beta but this seems to be something new.

 

Whenever I start the docker I get the following in the log and then it just keeps restarting. I've tried removing the docker and starting over but no luck so far and a google search has only turned up people having OS issues on raspbian when running on a pi.

 

[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...
::: Starting docker specific checks & setup for docker pihole/pihole
[✗] Aborting installation: iproute2 and iproute packages were not found in APT repository.
[cont-init.d] 20-start.sh: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

On 7/28/2020 at 1:44 AM, eubbenhadd said:

Argh. Ran through the excellent tutorial and had no success. Can not access the webUI. Got the following log. Have tried setting key 5 (interface) to both eth0 and br0, no luck. Have bonded interface (active balanced 1) with bridging enabled. Docker is set up with separate IP (different from server). Any help GREATLY appreciated!

 

EDIT: I notice on some other startups (from other people), there's this line but it doesn't show up on my install (which I've now tried re-installing, no difference)

Pi-hole blocking is enabled

 

LOG

------------------

 

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...
::: Starting docker specific checks & setup for docker pihole/pihole
WARNING Misconfigured DNS in /etc/resolv.conf: Two DNS servers are recommended, 127.0.0.1 and any backup server
WARNING Misconfigured DNS in /etc/resolv.conf: Primary DNS should be 127.0.0.1 (found 127.0.0.11)

nameserver 127.0.0.11
options ndots:0
Existing PHP installation detected : PHP version 7.0.33-0+deb9u8

Installing configs from /etc/.pihole...
Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
chown: cannot access '': No such file or directory
chmod: cannot access '': No such file or directory
chown: cannot access '/etc/pihole/dhcp.leases': No such file or directory
::: Pre existing WEBPASSWORD found
Using custom DNS servers: 1.1.1.1 & 1.0.0.1
DNSMasq binding to default interface: eth0
Added ENV to php:
"PHP_ERROR_LOG" => "/var/log/lighttpd/error.log",
"ServerIP" => "192.168.15.2",
"VIRTUAL_HOST" => "192.168.15.2",
Using IPv4
::: Preexisting ad list /etc/pihole/adlists.list detected ((exiting setup_blocklists early))
https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
https://mirror1.malwaredomains.com/files/justdomains
::: Testing pihole-FTL DNS: FTL started!
::: Testing lighttpd config: Syntax OK
::: All config checks passed, cleared for startup ...
::: Docker start setup complete
::: Pre existing WEBPASSWORD found
Using custom DNS servers: 1.1.1.1 & 1.0.0.1
DNSMasq binding to default interface: eth0
Added ENV to php:
"PHP_ERROR_LOG" => "/var/log/lighttpd/error.log",
"ServerIP" => "192.168.15.2",
"VIRTUAL_HOST" => "192.168.15.2",
Using IPv4
::: Preexisting ad list /etc/pihole/adlists.list detected ((exiting setup_blocklists early))
https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
https://mirror1.malwaredomains.com/files/justdomains
::: Testing pihole-FTL DNS: FTL started!
::: Testing lighttpd config: Syntax OK
::: All config checks passed, cleared for startup ...
::: Docker start setup complete
[✗] DNS resolution is currently unavailable
[✗] DNS resolution is currently unavailable

Hi! Did you manage to resolve this issue? I happen to be in the same boat, unfortunately...

Hi all! I have tried installing the pihole-template docker app, following along with the tutorial of Spaceinvader One.

 

All is well until I try to access the WebUI, which throws a timeout error! Has anyone else experienced similar difficulties and managed to resolve this? Any help is much appreciated!

 

I have already tried:

• Rebooting
• Reinstalling the pihole-template app
• Different static IP addresses
• Different DNS's

 

Below / attached you'll find a screenshot of my config, along with the output of the docker run command and the log.

 

Output docker run command:

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='pihole-template' --net='br0' --ip='192.168.0.30' -e TZ="Europe/Berlin" -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'='1.1.1.1' -e 'DNS2'='1.0.0.1' -e 'TZ'='Europe/Amsterdam' -e 'WEBPASSWORD'='admin' -e 'INTERFACE'='br0' -e 'ServerIP'='192.168.0.30' -e 'ServerIPv6'='' -e 'IPv6'='False' -e 'DNSMASQ_LISTENING'='all' -v '/mnt/user/appdata/pihole/pihole/':'/etc/pihole/':'rw' -v '/mnt/user/appdata/pihole/dnsmasq.d/':'/etc/dnsmasq.d/':'rw' --cap-add=NET_ADMIN --dns 127.0.0.1 --dns 1.1.1.1 --restart=unless-stopped 'pihole/pihole:latest'

WARNING: Localhost DNS setting (--dns=127.0.0.1) may fail in containers.
ce5b4d51962bd9dc4406debf9500f5b2f3aac685513104ab3a34b3af5a86e4d3

The command finished successfully!

 

Log:

[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...
::: Starting docker specific checks & setup for docker pihole/pihole
[i] Existing PHP installation detected : PHP version 7.3.19-1~deb10u1

[i] Installing configs from /etc/.pihole...
[i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
chown: cannot access '': No such file or directory
chmod: cannot access '': No such file or directory
chown: cannot access '/etc/pihole/dhcp.leases': No such file or directory
Converting DNS1 to PIHOLE_DNS_
Converting DNS2 to PIHOLE_DNS_
Setting DNS servers based on PIHOLE_DNS_ variable
::: Pre existing WEBPASSWORD found
DNSMasq binding to custom interface: br0
Added ENV to php:
"PHP_ERROR_LOG" => "/var/log/lighttpd/error.log",
"ServerIP" => "192.168.0.30",
"VIRTUAL_HOST" => "192.168.0.30",
Using IPv4
::: Preexisting ad list /etc/pihole/adlists.list detected ((exiting setup_blocklists early))
::: Testing pihole-FTL DNS: FTL started!
::: Testing lighttpd config: Syntax OK
::: All config checks passed, cleared for startup ...
::: Enabling Query Logging
[i] Enabling logging...
::: Docker start setup complete
[i] Neutrino emissions detected...

[i] Using libz compression

[i] Target: https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
[i] Received 58866 domains

[i] Number of gravity domains: 58866 (58866 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

[✓] DNS service is listening
[✓] UDP (IPv4)
[✓] TCP (IPv4)
[✓] UDP (IPv6)
[✓] TCP (IPv6)

[✓] Pi-hole blocking is enabled
Pi-hole version is v5.2.3 (Latest: v5.2.3)
AdminLTE version is v5.3 (Latest: v5.3)
FTL version is v5.4 (Latest: v5.4)
[cont-init.d] 20-start.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
Starting crond
Starting lighttpd
Starting pihole-FTL (no-daemon) as root
[services.d] done.

 

Edited January 17, 20215 yr by sgraaf

11 hours ago, SoCold said:

I've been running pi-hole for years mostly issue free but yesterday it died on me. I've had some recent disk errors that were traced back to SATA controller issues and hopefully were resolved with the last beta but this seems to be something new.

 

Whenever I start the docker I get the following in the log and then it just keeps restarting. I've tried removing the docker and starting over but no luck so far and a google search has only turned up people having OS issues on raspbian when running on a pi.

 

[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...
::: Starting docker specific checks & setup for docker pihole/pihole
[✗] Aborting installation: iproute2 and iproute packages were not found in APT repository.
[cont-init.d] 20-start.sh: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

 

Getting same error, i revert back to v5.3.4 for now

 

Did you manage to solve the issue?

...add/replace "--dns=8.8.8.8" (or any real DNS, not localhost/loopback/127.0.0.1) to the "Extra Parameters" in the Docker template.

That issue is stated/resolved here: https://github.com/pi-hole/docker-pi-hole/issues/762

5 hours ago, Ford Prefect said:

...add/replace "--dns=8.8.8.8" (or any real DNS, not localhost/loopback/127.0.0.1) to the "Extra Parameters" in the Docker template.

That issue is stated/resolved here: https://github.com/pi-hole/docker-pi-hole/issues/762

 

Found the issue, my firewall is blocking the traffic to public DNS

Edited January 18, 20215 yr by Kira

On 1/18/2021 at 1:32 AM, Kira said:

 

Getting same error, i revert back to v5.3.4 for now

 

Did you manage to solve the issue?

 

Looks like they updated, just had to reinstall last night and it works again now

 

On 1/18/2021 at 1:51 AM, Ford Prefect said:

...add/replace "--dns=8.8.8.8" (or any real DNS, not localhost/loopback/127.0.0.1) to the "Extra Parameters" in the Docker template.

That issue is stated/resolved here: https://github.com/pi-hole/docker-pi-hole/issues/762

 

Thanks for pointing me to that

I changed my subnet on my router, and it seems to have broken pihole. I've tried uninstalling and reinstalling, but I keep getting this message:

 

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='pihole-template' --net='br0' --ip='10.10.20.25' -e TZ="Australia/Sydney" -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'='Europe/London' -e 'WEBPASSWORD'='admin' -e 'INTERFACE'='br0' -e 'ServerIP'='10.10.20.25' -e 'ServerIPv6'='' -e 'IPv6'='False' -e 'DNSMASQ_LISTENING'='all' -v '/mnt/user/appdata/pihole/pihole/':'/etc/pihole/':'rw' -v '/mnt/user/appdata/pihole/dnsmasq.d/':'/etc/dnsmasq.d/':'rw' --cap-add=NET_ADMIN --dns 127.0.0.1 --dns 1.1.1.1 --restart=unless-stopped 'pihole/pihole:latest'
WARNING: Localhost DNS setting (--dns=127.0.0.1) may fail in containers.
df4349633b734a0d00ee1a35028a4a2510d00d911d3fbfbbfff49a169ad5641a
/usr/bin/docker: Error response from daemon: Invalid address 10.10.20.25: It does not belong to any of this network's subnets.

The command failed.

 

I am 100% sure I have entered the correct subnet. It's working for literally everything except for this container.

On 5/10/2020 at 2:32 PM, Armed Ferret said:

I ended up fixing it.  I had to do the following:

Bridge mode was enabled but in Settings > Docker "Host Access to custom networks" was disabled.  

So I needed to stop the docker service and enable that.  

.....

After that I was able to see the br0 interface. 

This was the key for me.  THANK YOU!  Docker is up and running successfully now.

How do I configure pi-hole on docker to accept incoming ssh connections?