Hello all!
I recently wanted to update my gravity list since I haven't in a very long time and I was struck with the error of "DNS resolution is currently unavailable" and then the "not available" after the try again period. I run this container in docker on my Unraid server and have followed the few video guides I can find about installing this on docker in Unraid. One video showed that they were immediately able to update gravity after the install but I was not (This was after I decided to uninstall then reinstall the docker container in an attempt to fix this issue).
I have all the ports set to their defaults, and made sure that no other dockers were using the same ports, and changed the following variables:
I set the fixed IP address to an IP inside the subnet it gave me (10.0.0.2)
network type set to "custom : br0"
Pihole_DNS_ is set to 1.1.1.1;1.0.0.1
and the serverIP to the same as the fixed IP from earlier
All of these are what the video guides showed to do.
In my attempts to fix this issue on my own, I saw several people saying something about a yaml but I do not know where to find that. I checked the install area for the docker container in my appdata folder and did not see anything. I also saw people talking about running pihole -r but I do not know where to run that command. I am very new to fiddling with errors like this.
What am I doing wrong😭
I generated a dubg log and the errors were: dig command failed - Unable to check OS
No IPv4 address(es) found on the br0
Failed to resolve doubleclick.com via a remote, public DNS server (2001:4860:4860::8888)
/etc/lighttpd/conf.d does not exist.
curl: (6) Could not resolve host: tricorder.pi-hole.net
Everything else seemed to check out. I noticed br0 was familiar, and I see that one of my virtual machines uses it (however that VM is currently shutdown). Maybe some of these would be useful?

Hello all!
I recently wanted to update my gravity list since I haven't in a very long time and I was struck with the error of "DNS resolution is currently unavailable" and then the "not available" after the try again period. I run this container in docker on my Unraid server and have followed the few video guides I can find about installing this on docker in Unraid. One video showed that they were immediately able to update gravity after the install but I was not (This was after I decided to uninstall then reinstall the docker container in an attempt to fix this issue).
I have all the ports set to their defaults, and made sure that no other dockers were using the same ports, and changed the following variables:
I set the fixed IP address to an IP inside the subnet it gave me (10.0.0.2)
network type set to "custom : br0"
Pihole_DNS_ is set to 1.1.1.1;1.0.0.1
and the serverIP to the same as the fixed IP from earlier
All of these are what the video guides showed to do.
In my attempts to fix this issue on my own, I saw several people saying something about a yaml but I do not know where to find that. I checked the install area for the docker container in my appdata folder and did not see anything. I also saw people talking about running pihole -r but I do not know where to run that command. I am very new to fiddling with errors like this.
What am I doing wrong😭
Edit:
I generated a dubg log and the errors were: dig command failed - Unable to check OS
No IPv4 address(es) found on the br0
Failed to resolve doubleclick.com via a remote, public DNS server (2001:4860:4860::8888)
/etc/lighttpd/conf.d does not exist.
curl: (6) Could not resolve host: tricorder.pi-hole.net
Everything else seemed to check out. I noticed br0 was familiar, and I see that one of my virtual machines uses it (however that VM is currently shutdown). Maybe some of these would be useful?

I've been trying to get pihole to work with docker but it just isn't working. here are the logs:
"VIRTUAL_HOST" => "archlinuxserver",
[i] Using IPv4 and IPv6
[i] Installing latest Cron script...
[✓] Installing latest Cron script
[i] Preexisting ad list /etc/pihole/adlists.list detected (exiting setup_blocklists early)
[i] Existing DNS servers detected in setupVars.conf. Leaving them alone
[i] Applying pihole-FTL.conf setting LOCAL_IPV4=0.0.0.0
[i] FTL binding to default interface: eth0
[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
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
Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf
s6-rc: info: service legacy-services successfully started
[i] Neutrino emissions detected...
​
[✓] Pulling blocklist source list into range
[i] Preparing new gravity database...
[✓] Preparing new gravity database
[i] Creating new gravity databases...
[✓] Creating new gravity databases
Stopping pihole-FTL
pihole-FTL: no process found
[i] Using libz compression
[i] Target: https://raw.githubusercontent.com/StevenBlack/hosts/mastehosts
[i] Status: Pending...
[✓] Status: Retrieval successful
Stopping pihole-FTL
pihole-FTL: no process found
Stopping pihole-FTL
Terminated
[i] List stayed unchanged
[i] Building tree...
[✓] Building tree
[i] Swapping databases...
[✓] Swapping databases
[✓] The old database remains available
[i] Number of gravity domains: 0 (0 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
/bin/bash: line 1: 344 Hangup /usbin/pihole-FTL no-daemon > /dev/null 2>&1
[i] Cleaning up stray matter...
[✓] Cleaning up stray matter
Stopping pihole-FTL
pihole-FTL: no process found
[✓] FTL is listening on port
[✓] UDP (IPv4)
[✓] TCP (IPv4)
[✓] UDP (IPv6)
[✓] TCP (IPv6)
[✓] Pi-hole blocking is enabled
Stopping pihole-FTL
pihole-FTL: no process found
Stopping pihole-FTL
pihole-FTL: no process found
Stopping pihole-FTL
pihole-FTL: no process found
Pi-hole version is v5.17.3 (Latest: v5.17.3)
web version is v5.21 (Latest: v5.21)
FTL version is v5.24 (Latest: v5.24)
Container tag is: 2024.01.0
Stopping pihole-FTL
pihole-FTL: no process found
I tried adding PIHOLE_UID = 0 and DNSMASQ_USER = root without success. I am using the latest image. Any idea ?

me@jupiter:~$ lsblk -o MODEL,SERIAL,SIZE,STATE --nodeps MODEL SERIAL SIZE STATE 73.9M 152.1M 40.9M CT250MX500SSD1 2219E6302473 232.9G running P3-1TB 0010159006480 953.9G running P3-1TB 0010159006489 953.9G running NX-2TB 2280 0010174003295 1.9T live me@jupiter:~$ zfs list NAME USED AVAIL REFER MOUNTPOINT backup-pool 291G 631G 26K /backup-pool backup-pool/computers 121G 631G 121G /backup-pool/computers backup-pool/documents 24K 631G 24K /backup-pool/documents backup-pool/photos 166G 631G 166G /backup-pool/photos backup-pool/servers 4.36G 631G 4.36G /backup-pool/servers data-pool 520G 1.29T 26K /data-pool data-pool/apps 6.90G 1.29T 6.90G /data-pool/apps data-pool/home 27.6G 1.29T 27.6G /home data-pool/media 486G 1.29T 486G /data-pool/media me@jupiter:~$ docker ps --format "table {{.ID}}\t{{.Image}}\t{{.Size}}" CONTAINER ID IMAGE SIZE 46ffbe41beee ghcr.io/flaresolverflaresolverr:latest 16.1MB (virtual 618MB) 9c6eb995b729 lscr.io/linuxservejackett:latest 106MB (virtual 277MB) ffe5ccd4aae1 portaineportainer-ce:latest 0B (virtual 294MB) b28afe33a106 lscr.io/linuxserveradarr:latest 23.6kB (virtual 196MB) 0f7744daf9d6 lscr.io/linuxservesonarr:latest 35.6MB (virtual 335MB) 574c625933b1 binhex/arch-delugevpn:latest 16.5MB (virtual 1.29GB) 8a7f84e40f84 lscr.io/linuxserveplex:latest 24.3kB (virtual 340MB) 37e8580600ef lscr.io/linuxservebazarr:latest 23.2kB (virtual 422MB) 

I have setup the Pi-Hole admin console behind an Nginx proxy, and both are running in Docker containers. Any time I try to load a page that includes some kind of data table, I get the following error (this one from the DNS page, but it happens in most pages):

DataTables warning: table id=customDNSTable - Invalid JSON response. For more information about this error, please see http://datatables.net/tn/1 

In searching for a solution, I read a lot of suggestions to clear my browser cache. This did not work, and the issue exists in a brand new browser having never visited the Pi-Hole admin console.
This only happens when I visit the admin console by HTTPS+domain and NOT HTTP+IP ( https://pihole.mydomain.foo/admin/ versus http://ip.ad.dadmin/ ).
So with that, I found another suggestion to create /etc/lighttpd/external.conf and add the line:

setenv.add-environment = ( "VIRTUAL_HOST" => "pihole.mydomain.foo" ) 

But this also did not work. No change.
There's something simple I'm missing about the proxy setup and how Pi-Hole loads its data tables. Any suggestions?
Debug token: pwqawFNp

EDIT - I switched to AdGuard Home and never looked back. I set up Pihole per the official guide, with a few adjustments (see below). I attached USB SSD to the RB5009 to use with the containers. Running latest stable ROS 7.10.2.Sometimes, it runs perfectly fine - start within ~15 seconds, web gui is snappy and responsive, DNS resolution works without noticeable lag, Gravity update takes ~5 seconds.
However, in most cases the start is extremely slow - I'm talking 20+ minutes (see example log below) to just start, the webgui takes ages to load, each operation is very slow there as well, DNS resolution lagging or not working at all... Recreating the container fixes it but usually I have to recreate the container multiple times (success rate about 1 in 5).
In both cases (good and bad), CPU load on the router is always very low, at max 8 %.
Any idea why this might be happening?
/container export:

/container mounts add dst=/etc/pihole name=etc_pihole src=/usb1/mounts/pihole/etc add dst=/etc/dnsmasq.d name=dnsmasq_pihole src=/usb1/mounts/pihole/dnsmasq.d /container add envlist=pihole_envs interface=veth1-pihole logging=yes mounts=etc_pihole,dnsmasq_pihole root-dir=usb1/pihole start-on-boot=yes /container config set ram-high=512 registry-url=https://registry-1.docker.io tmpdir=usb1/pull /container envs add key=WEBPASSWORD name=pihole_envs value=mysecurepassword add key=DNSMASQ_USER name=pihole_envs value=root add key=TZ name=pihole_envs value=Europe/Prague add key=PIHOLE_DOCKER_TAG name=pihole_envs value=lates 

Example log:

 12:22:47 container,info,debug s6-rc: info: service s6rc-oneshot-runner: starting 12:22:55 container,info,debug s6-rc: info: service s6rc-oneshot-runner successfully started 12:22:55 container,info,debug s6-rc: info: service fix-attrs: starting 12:23:03 container,info,debug s6-rc: info: service fix-attrs successfully started 12:23:03 container,info,debug s6-rc: info: service legacy-cont-init: starting 12:23:14 container,info,debug s6-rc: info: service legacy-cont-init successfully started 12:23:14 container,info,debug s6-rc: info: service cron: starting 12:23:18 container,info,debug s6-rc: info: service cron successfully started 12:23:18 container,info,debug s6-rc: info: service _uid-gid-changer: starting 12:23:28 container,info,debug s6-rc: info: service _uid-gid-changer successfully started 12:23:28 container,info,debug s6-rc: info: service _startup: starting 12:23:49 container,info,debug [i] Starting docker specific checks & setup for docker pihole/pihole 12:23:49 container,info,debug [i] Setting capabilities on pihole-FTL where possible 12:24:02 container,info,debug [i] Applying the following caps to pihole-FTL: 12:24:04 container,info,debug * CAP_CHOWN 12:24:04 container,info,debug * CAP_NET_BIND_SERVICE 12:24:04 container,info,debug * CAP_NET_RAW 12:24:04 container,info,debug * CAP_NET_ADMIN 12:24:04 container,info,debug * CAP_SYS_NICE 12:24:14 container,info,debug [i] Ensuring basic configuration by re-running select functions from basic-install.sh 12:24:14 container,info,debug 12:24:14 container,info,debug [i] Installing configs from /etc/.pihole... 12:24:20 container,info,debug [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone! 12:24:27 container,info,debug [i] Installing /etc/dnsmasq.d/01-pihole.conf...r1B[K [E29C93] Installed /etc/dnsmasq.d/01-pihole.conf 12:24:43 container,info,debug [i] Installing /etc/.pihole/advanced/06-rfc6761.conf...r1B[K [E29C93] Installed /etc/dnsmasq.d/06-rfc6761.conf 12:26:07 container,info,debug 12:26:13 container,info,debug [i] Installing latest logrotate script... 12:26:13 container,info,debug t[i] Existing logrotate file found. No changes made. 12:26:50 container,info,debug [i] Assigning password defined by Environment Variable 12:27:28 container,info,debug [E29C93] New password set 12:28:18 container,info,debug [i] Added ENV to php: 12:28:20 container,info,debug "TZ" => "Europe/Prague", 12:28:20 container,info,debug "PIHOLE_DOCKER_TAG" => "latest", 12:28:20 container,info,debug "PHP_ERROR_LOG" => "/valog/lighttpd/error-pihole.log", 12:28:20 container,info,debug "CORS_HOSTS" => "", 12:28:20 container,info,debug "VIRTUAL_HOST" => "RB5009UPrS", 12:28:30 container,info,debug [i] Using IPv4 and IPv6 12:28:34 container,info,debug 12:28:47 container,info,debug [i] Installing latest Cron script...r1B[K [E29C93] Installing latest Cron script 12:28:47 container,info,debug [i] Preexisting ad list /etc/pihole/adlists.list detected (exiting setup_blocklists early) 12:28:59 container,info,debug [i] Existing DNS servers detected in setupVars.conf. Leaving them alone 12:29:07 container,info,debug [i] Applying pihole-FTL.conf setting LOCAL_IPV4=0.0.0.0 12:29:47 container,info,debug [i] FTL binding to default interface: eth0 12:30:16 container,info,debug [i] Enabling Query Logging 12:39:01 container,info,debug [i] Testing lighttpd config: Syntax OK 12:39:05 container,info,debug [i] All config checks passed, cleared for startup ... 12:39:07 container,info,debug [i] Docker start setup complete 12:39:07 container,info,debug 12:39:07 container,info,debug [i] pihole-FTL (no-daemon) will be started as root 12:39:07 container,info,debug 12:39:07 container,info,debug s6-rc: info: service _startup successfully started 12:39:07 container,info,debug s6-rc: info: service pihole-FTL: starting 12:39:09 container,info,debug s6-rc: info: service pihole-FTL successfully started 12:39:09 container,info,debug s6-rc: info: service lighttpd: starting 12:39:15 container,info,debug s6-rc: info: service lighttpd successfully started 12:39:15 container,info,debug s6-rc: info: service _postFTL: starting 12:39:17 container,info,debug s6-rc: info: service _postFTL successfully started 12:39:17 container,info,debug s6-rc: info: service legacy-services: starting 12:39:17 container,info,debug Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf 12:39:34 container,info,debug s6-rc: info: service legacy-services successfully started 12:40:13 container,info,debug [i] Neutrino emissions detected... 12:40:40 container,info,debug r1B[K [E29C93] Pulling blocklist source list into range 12:40:40 container,info,debug 12:40:57 container,info,debug [i] Preparing new gravity database...r1B[K [E29C93] Preparing new gravity database 12:41:06 netwatch,info event up [ type: tcp_conn, host: 172.17.0.2 ] 12:41:06 system,info dns changed 12:41:06 system,info nat rule changed 12:41:06 script,info set DNS to PiHole, because it came up 12:41:10 container,info,debug [i] Creating new gravity databases...r1B[K [E29C93] Creating new gravity databases 12:43:14 container,info,debug [i] Using libz compression 12:43:14 container,info,debug 12:43:14 container,info,debug [i] Target: https://raw.githubusercontent.com/StevenBlack/hosts/mastehosts 

​

This is fixed now but I'm wondering "why?".
Running Pihole Docker on Ubuntu. Had to reboot ubuntu a few times troubleshooting something else (not working with HDMI KVM) and Pihole would not restart.
Had this line in my previously working Dockerfile:
INTERFACE: enp4s0
Had to replace with this:
INTERFACE: enp4s0f0
which now works.
Any idea why Ubunutu would do this to me and should I expect it to happen again?
I do have to run network_mode: host since I am using the host's IPv6.
​
Here is my docker file:

services: pihole: cpus: 4 container_name: pihole image: pihole/pihole:latest network_mode: host environment: TZ: 'America/New_York' PIHOLE_DNS_: x.x.x.x WEBPASSWORD: '' FTLCONF_LOCAL_IPV6: fd53::1 FTLCONF_LOCAL_IPV4: 10.0.0.53 WEBTHEME: default-auto VIRTUAL_HOST: ubuntu DNS_BOGUS_PRIV: "false" DNS_FQDN_REQUIRED: "false" DNSMASQ_LISTENING: single FTLCONF_BLOCK_ICLOUD_PR: "false" DNSMASQ_USER: root FTLCONF_DBFILE: /valog/pihole-FTL.db INTERFACE: enp4s0f0 volumes: - '/share/Dockepihole/etc-pihole/:/etc/pihole/' - '/share/Dockepihole/etc-dnsmasq.d/:/etc/dnsmasq.d/' - type: tmpfs target: /valog/lighttpd tmpfs: size: 10000000 mode: 750 - type: tmpfs target: /valog tmpfs: size: 100000000 dns: - 127.0.0.1 restart: always 

​

I have been running PiHole on a Rpi for several years. The Rpi is slow and clunky, but it works. I have a dedicated server that I run all my services on. Over the years, my experience with docker usually ends with me pulling my hair out over the networking, after several hours or days, I end up removing it completely. In concept, it's amazing, but I have never been able to get it to work for the things I have tried to use it for. Here I am back at it again. I have installed portainer and that works as expected. I managed to get a docker image of Ubiquiti's Unifi software and that works as expected (finally). Now I'm trying to consolidate my Rpi functions into a container as well. I put in all of the information from here into portainer as a new container: https://github.com/pi-hole/docker-pi-hole/blob/masteexamples/docker_run.sh
I'm not wanting to use the DHCP functions, so I do not enable the port 67. I also already have a web server on my host taking up port 80, so I have that instead set to 8082 -> 80. I passthrough the recommended variables, TZ and WEBPASSWORD, as well as FTLCONF_LOCAL_IPV4, which I set to my host IP address. In the networking tab, I leave it set to bridge (and I even created a new network using the bridge type) and set the two DNS entries there (127.0.0.1, 1.1.1.1). I've passed through variables of DNS1 = 127.0.0.1, DNS2 = 1.1.1.1.
All of this ends in the same result, container fails to initialize. Here is a full log:

s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started 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 [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 [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! [i] Installing /etc/dnsmasq.d/01-pihole.conf... [✓] Installed /etc/dnsmasq.d/01-pihole.conf [i] Installing /etc/.pihole/advanced/06-rfc6761.conf... [✓] Installed /etc/dnsmasq.d/06-rfc6761.conf [i] Installing latest logrotate script... [i] Existing logrotate file found. No changes made. [i] Pre existing WEBPASSWORD found [i] Added ENV to php: "TZ" => "America/Boise", "PIHOLE_DOCKER_TAG" => "", "PHP_ERROR_LOG" => "/valog/lighttpd/error-pihole.log", "CORS_HOSTS" => "", "VIRTUAL_HOST" => "ce5347e30171", [i] Using IPv4 [i] Preexisting ad list /etc/pihole/adlists.list detected (exiting setup_blocklists early) [i] Existing DNS servers detected in setupVars.conf. Leaving them alone [i] Applying pihole-FTL.conf setting LOCAL_IPV4=10.5.21.252 [i] FTL binding to default interface: eth0 [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 pihole 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 Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf s6-rc: info: service legacy-services successfully started [✗] DNS resolution is currently unavailable 

The "DNS resolution is currently unavailable" is what I'm met with each time. Searches for this turn up a few solutions, all of them I performed above and do not change the outcome. I even tried to make the container using a macvlan network to bridge through my host adapter and utilize one of my LAN network addresses, but that container won't even initialize period. I get an error 403 when I try to deploy it.
Does anyone know of the solution here before I reach my screw-it moment and delete it all again?
Just for reference, my host is a Debian linux, no gui setup: Linux zion 5.10.0-21-amd64 #1 SMP Debian 5.10.162-1 (2023-01-21) x86_64 GNU/Linux
​
Edit:
I was able to get this working using a macvlan network. I noticed creating the macvlan in Portainer, it was not assigning the correct driver. It assigned it as null, even though I selected the macvlan option and input the parent interface. I instead created the macvlan on the server directly using the docker command. After that, I assigned it to the container and it fires right up and works as expected. Still don't understand why the standard bridge does not do it, but this at least works.

(Duplicate config variable in conditional 3 global / $HTTP["url"] == "/" / $HTTP["host"] == "192.168.1.10": url.redirect 2023-02-06 20:26:01: configfile.c.1970) source: /etc/lighttpd/conf-enabled/15-pihole-admin-redirect-docker.conf line: 7 pos: 9 parser failed somehow near here: (EOL) 2023-02-06 20:26:01: configfile.c.1970) source: /etc/lighttpd/lighttpd.conf line: 51 pos: 15 parser failed somehow near here: (EOL) Stopping lighttpd lighttpd: no process found 

version: "3" services: pihole: image: pihole/pihole:latest container_name: pihole hostname: nas-pihole restart: always ports: - "53:53/tcp" - "53:53/udp" - "67:67/udp" - "80:80/tcp" environment: TZ: $TZ WEBPASSWORD: $PIHOLE_PASSWORD FTLCONF_REPLY_ADDR4: $SERVER_ADDRESS VIRTUAL_HOST: $SERVER_ADDRESS PIHOLE_DNS_: 1.1.1.1;1.0.0.1;9.9.9.9;9.9.9.11;149.112.112.112;149.112.112.11 networks: qnet-static-eth1-79e6cc: ipv4_address: $PIHOLE_ADDRESS volumes: - $MOUNT_POINT_CONFIG/pihole:/etc/pihole - $MOUNT_POINT_CONFIG/pihole/dnsmasq:/etc/dnsmasq.d dns: - 127.0.0.1 - 1.1.1.1 cap_add: - NET_ADMIN networks: qnet-static-eth1-79e6cc: external: true 

$HTTP["url"] == "/" { $HTTP["host"] == "192.168.1.10" { url.redirect = ("" => "/admin/") } $HTTP["host"] == "192.168.1.10" { url.redirect = ("" => "/admin/") } } 

docker compose file :

version: "3" # More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/ services: pihole: container_name: pihole image: pihole/pihole:latest # For DHCP it is recommended to remove these ports and instead add: #network_mode: "host" ports: - "53:53/tcp" - "53:53/udp" - "67:67/udp" # Only required if you are using Pi-hole as your DHCP server - "8008:80/tcp" environment: TZ: 'America/Sao_Paulo' WEBPASSWORD: 'my-password' # Volumes store your data between container upgrades volumes: - './etc-pihole:/etc/pihole' - './etc-dnsmasq.d:/etc/dnsmasq.d' # https://github.com/pi-hole/docker-pi-hole#note-on-capabilities cap_add: - NET_ADMIN # Required if you are using Pi-hole as your DHCP server, else not needed restart: unless-stopped 

container log with timestamp :

orangepi3-lts:~:% docker logs --follow pihole s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started 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 [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 [✓] Installing latest logrotate script [i] Creating empty /etc/pihole/setupVars.conf file. [i] Assigning password defined by Environment Variable [✓] New password set [i] Added ENV to php: "TZ" => "America/Sao_Paulo", "PIHOLE_DOCKER_TAG" => "", "PHP_ERROR_LOG" => "/valog/lighttpd/error-pihole.log", "CORS_HOSTS" => "", "VIRTUAL_HOST" => "0.0.0.0", [i] Using IPv4 and IPv6 [i] setup_blocklists now setting default blocklists up: [i] TIP: Use a docker volume for /etc/pihole/adlists.list if you want to customize for first boot [i] Blocklists (/etc/pihole/adlists.list) now set to: https://raw.githubusercontent.com/StevenBlack/hosts/mastehosts [i] Configuring default DNS servers: 8.8.8.8, 8.8.4.4 [i] Applying pihole-FTL.conf setting LOCAL_IPV4=0.0.0.0 [i] FTL binding to default interface: eth0 [i] Enabling Query Logging [i] Testing lighttpd config: Syntax OK [i] All config checks passed, cleared for startup ... [i] Docker start setup complete Pi-hole version is v5.13 (Latest: v5.13) AdminLTE version is v5.16 (Latest: v5.16) FTL version is v5.18.2 (Latest: v5.18.2) Container tag is: [i] pihole-FTL (no-daemon) will be started as pihole 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 _gravityonboot: starting s6-rc: info: service _gravityonboot successfully started s6-rc: info: service legacy-services: starting Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf s6-rc: info: service legacy-services successfully started [i] Creating new gravity database [i] Migrating content of /etc/pihole/adlists.list into new database [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/mastehosts [✓] Status: Retrieval successful [i] Analyzed 159591 domains [✓] 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: 159591 (159591 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) [i] Pi-hole blocking will be enabled [i] Enabling blocking [✓] Pi-hole Enabled 2022-11-08T00:46:21.802844464Z Stopping pihole-FTL 2022-11-08T00:59:04.523516933Z Stopping pihole-FTL 2022-11-08T01:08:17.666724676Z Stopping pihole-FTL 2022-11-08T01:08:35.735864305Z Stopping pihole-FTL 2022-11-08T01:08:51.689637873Z Stopping pihole-FTL 2022-11-08T01:09:03.965183690Z Stopping pihole-FTL 2022-11-08T01:16:57.869213747Z Stopping pihole-FTL 2022-11-08T01:17:14.231555164Z Stopping pihole-FTL 2022-11-08T01:49:34.148447075Z Stopping pihole-FTL 2022-11-08T01:49:52.781461089Z Stopping pihole-FTL 2022-11-08T02:01:04.232287807Z Stopping pihole-FTL 2022-11-08T02:01:22.533014533Z Stopping pihole-FTL 2022-11-08T02:01:49.945796609Z Stopping pihole-FTL 2022-11-08T02:02:14.359106019Z Stopping pihole-FTL 2022-11-08T02:03:02.383652632Z Stopping pihole-FTL 2022-11-08T02:03:33.119317140Z Stopping pihole-FTL 2022-11-08T02:03:53.235973154Z Stopping pihole-FTL 

I am an idiot and should be stoned by the community. I copied an old backup. With the current data its working fine.
Hey,
I want to move my pihole from one system to another. I have shutdown the old instance and copied everything into a new folder on the new system that lies under /etc/pihole but when I open the webinterface of the new instance the query history is empty. Both are the same pihole container version.
My new compose file:

 pi.hole: container_name: pihole.home image: pihole/pihole:2022.02.1 hostname: pihole domainname: pihole.home # <-- Update mac_address: d0:ca:ab:cd:ef:80 cap_add: - NET_ADMIN volumes: - C:\Docker\Data\PiHole\etc:/etc/pihole/:rw - C:\Docker\Data\PiHole\dnsmasq:/etc/dnsmasq.d/:rw environment: ServerIP: 192.168.***.** # <-- Update (match ipv4_address) VIRTUAL_HOST: pihole.home # <-- Update (match hostname + domainname) WEBPASSWORD: "" # <-- Add password (if required) restart: unless-stopped networks: - home_network - ReverseProxyNetwork 

everything in C:\Docker\Data\PiHole\etc and C:\Docker\Data\PiHole\dnsmasq are byte by byte the same but it does not display anything. The only thing that "should" be different is the serverIP and VirtualHost variables.
As I moved the config as well as the pihole-FTL.db it should display everything but it does not. No error log:

[s6-init] making user provided files available at /varun/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] 05-changer-uid-gid.sh: executing... [cont-init.d] 05-changer-uid-gid.sh: exited 0. [cont-init.d] 20-start.sh: executing... ::: Starting docker specific checks & setup for docker pihole/pihole [i] Installing configs from /etc/.pihole... [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone! [i] Installing /etc/dnsmasq.d/01-pihole.conf... [✓] Installed /etc/dnsmasq.d/01-pihole.conf [i] Installing /etc/.pihole/advanced/06-rfc6761.conf... [✓] Installed /etc/dnsmasq.d/06-rfc6761.conf Existing DNS servers detected in setupVars.conf. Leaving them alone ::: Pre existing WEBPASSWORD found DNSMasq binding to default interface: eth0 Added ENV to php: "TZ" => "", "PIHOLE_DOCKER_TAG" => "2022.02.1", "PHP_ERROR_LOG" => "/valog/lighttpd/error.log", "ServerIP" => "192.168.***.**", "CORS_HOSTS" => "", "VIRTUAL_HOST" => "pihole.home", Using IPv4 and IPv6 ::: Preexisting ad list /etc/pihole/adlists.list detected ((exiting setup_blocklists early)) https://raw.githubusercontent.com/StevenBlack/hosts/mastehosts ::: Testing lighttpd config: Syntax OK ::: All config checks passed, cleared for startup ... ::: Enabling Query Logging [i] Enabling logging... [✓] Logging has been enabled! ::: Docker start setup complete Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf Pi-hole version is v5.9 (Latest: v5.11.4) AdminLTE version is v5.11 (Latest: v5.13) FTL version is v5.14 (Latest: v5.16.1) Container tag is: 2022.02.1 [cont-init.d] 20-start.sh: exited 0. [cont-init.d] done. [services.d] starting services Starting pihole-FTL (no-daemon) as pihole Starting crond Starting lighttpd [services.d] done. 

Why does the new Pihole not display any historical data?

I am trying to get pihole running in docker on my synology and even though it looks like the container is running I can't reach pihole. I'm not sure how to track down the issue and am hoping someone can point me in the right direction.
Settings

docker run --name=pihole --hostname=pihole --env=PATH=/opt/pihole:/uslocal/sbin:/uslocal/bin:/ussbin:/usbin:/sbin:/bin --env=phpver=php --env=PIHOLE_DOCKER_TAG=2022.07.1 --env=S6_OVERLAY_VERSION=v2.1.0.2 --env='PIHOLE_INSTALL=/etc/.pihole/automated install/basic-install.sh' --env=PHP_ENV_CONFIG=/etc/lighttpd/conf-enabled/15-fastcgi-php.conf --env=PHP_ERROR_LOG=/valog/lighttpd/error-pihole.log --env=IPv6=True --env=S6_LOGGING=0 --env=S6_KEEP_ENV=1 --env=S6_BEHAVIOUR_IF_STAGE2_FAILS=2 --env=ServerIP=192.168.179.2 --env=FTL_CMD=no-daemon --env=DNSMASQ_USER=root --env=WEBPASSWORD=redacted --env=TZ=America/Los_Angeles --env=DNSMASQ_LISTENING=local --volume=/volume1/dockepihole/pihole:/etc/pihole:rw --volume=/volume1/dockepihole/dnsmasq.d:/etc/dnsmasq.d:rw --network=PurplePi -p 53 -p 53/udp -p 67/udp -p 80 --restart=always --label='org.opencontainers.image.version=2022.07.1' --label='org.opencontainers.image.created=2022-07-10T13:08:55.626Z' --label='org.opencontainers.image.description=Pi-hole in a docker container' --label='org.opencontainers.image.revision=7e69551be1b76d175fffc1b8c53733e74ee82520' --label='org.opencontainers.image.source=https://github.com/pi-hole/docker-pi-hole' --label='org.opencontainers.image.licenses=' --label='org.opencontainers.image.title=docker-pi-hole' --label='org.opencontainers.image.url=https://github.com/pi-hole/docker-pi-hole' --log-driver=db --runtime=runc --detach=true -t pihole/pihole:latest 

Log file

2022-07-23 22:40:21stdoutStarting lighttpd2022-07-23 22:40:21stdoutStarting crond2022-07-23 22:40:21stdoutStarting pihole-FTL (no-daemon) as root2022-07-23 22:40:21stdout[services.d] done.2022-07-23 22:40:21stdout[services.d] starting services2022-07-23 22:40:21stdout[cont-init.d] done.2022-07-23 22:40:21stdout[cont-init.d] 20-start.sh: exited 0.2022-07-23 22:40:21stdout Container tag is: 2022.07.12022-07-23 22:40:20stdout FTL version is v5.16.1 (Latest: v5.16.1)2022-07-23 22:40:20stdout AdminLTE version is v5.13 (Latest: v5.13)2022-07-23 22:40:18stdout Pi-hole version is v5.11.4 (Latest: v5.11.4)2022-07-23 22:40:09stdout Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf2022-07-23 22:40:09stdout ::: Docker start setup complete2022-07-23 22:40:09stdout[K [[32m✓[0m] Logging has been enabled!2022-07-23 22:40:09stdout [i] Restarting DNS server... [K [[32m✓[0m] Restarting DNS server2022-07-23 22:40:08stdout [i] Enabling logging...2022-07-23 22:40:08stdout::: Enabling Query Logging2022-07-23 22:40:07stdout::: All config checks passed, cleared for startup ...2022-07-23 22:40:07stdout::: Testing lighttpd config: Syntax OK2022-07-23 22:40:05stdouthttps://raw.githubusercontent.com/StevenBlack/hosts/mastehosts2022-07-23 22:40:05stdout::: Blocklists (/etc/pihole/adlists.list) now set to:2022-07-23 22:40:05stdout::: TIP: Use a docker volume for /etc/pihole/adlists.list if you want to customize for first boot2022-07-23 22:40:05stdout::: setup_blocklists now setting default blocklists up: 2022-07-23 22:40:05stdoutUsing IPv4 and IPv62022-07-23 22:40:05stdout"VIRTUAL_HOST" => "192.168.179.2",2022-07-23 22:40:05stdout"CORS_HOSTS" => "",2022-07-23 22:40:05stdout"ServerIP" => "192.168.179.2",2022-07-23 22:40:05stdout"PHP_ERROR_LOG" => "/valog/lighttpd/error-pihole.log",2022-07-23 22:40:05stdout"PIHOLE_DOCKER_TAG" => "2022.07.1",2022-07-23 22:40:05stdout"TZ" => "America/Los_Angeles",2022-07-23 22:40:05stdoutAdded ENV to php:2022-07-23 22:40:01stdoutDNSMasq binding to default interface: eth02022-07-23 22:40:01stdout [[32m✓[0m] New password set2022-07-23 22:40:01stdout::: Assigning password defined by Environment Variable2022-07-23 22:40:00stdoutConfiguring default DNS servers: 8.8.8.8, 8.8.4.42022-07-23 22:39:56stdoutCreating empty /etc/pihole/setupVars.conf file.2022-07-23 22:39:55stdout [i] Installing /etc/.pihole/advanced/06-rfc6761.conf... [K [[32m✓[0m] Installed /etc/dnsmasq.d/06-rfc6761.conf2022-07-23 22:39:54stdout [i] Installing /etc/dnsmasq.d/01-pihole.conf... [K [[32m✓[0m] Installed /etc/dnsmasq.d/01-pihole.conf2022-07-23 22:39:54stdout [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!2022-07-23 22:39:54stdout [i] Installing configs from /etc/.pihole...2022-07-23 22:39:54stdout2022-07-23 22:39:54stdoutThe value of the capability argument is not permitted for a file. Or the file is not a regular (non-symlink) file2022-07-23 22:39:54stdoutFailed to set capabilities on file `/usbin/pihole-FTL' (Operation not supported)2022-07-23 22:39:53stdout ::: Starting docker specific checks & setup for docker pihole/pihole2022-07-23 22:39:52stdout[cont-init.d] 20-start.sh: executing... 2022-07-23 22:39:52stdout[cont-init.d] 05-changer-uid-gid.sh: exited 0.2022-07-23 22:39:51stdout[cont-init.d] 05-changer-uid-gid.sh: executing... 2022-07-23 22:39:51stdout[cont-init.d] executing container initialization scripts...2022-07-23 22:39:51stdout[fix-attrs.d] done.2022-07-23 22:39:51stdout[fix-attrs.d] 01-resolver-resolv: exited 0.2022-07-23 22:39:51stdout[fix-attrs.d] 01-resolver-resolv: applying... 2022-07-23 22:39:51stdout[fix-attrs.d] applying ownership & permissions fixes...2022-07-23 22:39:51stdout[s6-init] ensuring user provided files have correct perms...exited 0.2022-07-23 22:39:50stdout[s6-init] making user provided files available at /varun/s6/etc...exited 0.2022-07-23 22:37:59stdout[cont-init.d] 05-changer-uid-gid.sh: executing... 2022-07-23 22:37:59stdout[cont-init.d] executing container initialization scripts...2022-07-23 22:37:59stdout[fix-attrs.d] done.2022-07-23 22:37:58stdout[fix-attrs.d] 01-resolver-resolv: exited 0.2022-07-23 22:37:58stdout[fix-attrs.d] 01-resolver-resolv: applying... 2022-07-23 22:37:58stdout[fix-attrs.d] applying ownership & permissions fixes...2022-07-23 22:37:58stdout[s6-init] ensuring user provided files have correct perms...exited 0.2022-07-23 22:37:57stdout[s6-init] making user provided files available at /varun/s6/etc...exited 0.2022-07-23 22:37:35stdout[s6-finish] sending all processes the KILL signal and exiting.2022-07-23 22:37:32stdout[s6-finish] sending all processes the TERM signal.2022-07-23 22:37:32stdout[s6-finish] waiting for services.2022-07-23 22:37:32stdout[cont-finish.d] done.2022-07-23 22:37:32stdout[cont-finish.d] executing container finish scripts...2022-07-23 22:37:32stdout[cont-init.d] 20-start.sh: exited 1.2022-07-23 22:37:32stdout If you are seeing this error, please set the environment variable 'DNSMASQ_USER' to the value 'root'2022-07-23 22:37:32stdoutERROR: Unable to set capabilities for pihole-FTL. Cannot run as non-root.2022-07-23 22:37:32stdoutThe value of the capability argument is not permitted for a file. Or the file is not a regular (non-symlink) file2022-07-23 22:37:32stdoutFailed to set capabilities on file `/usbin/pihole-FTL' (Operation not supported)2022-07-23 22:37:32stdout ::: Starting docker specific checks & setup for docker pihole/pihole2022-07-23 22:37:31stdout[cont-init.d] 20-start.sh: executing... 2022-07-23 22:37:31stdout[cont-init.d] 05-changer-uid-gid.sh: exited 0.2022-07-23 22:37:31stdout[cont-init.d] 05-changer-uid-gid.sh: executing... 2022-07-23 22:37:31stdout[cont-init.d] executing container initialization scripts...2022-07-23 22:37:31stdout[fix-attrs.d] done.2022-07-23 22:37:31stdout[fix-attrs.d] 01-resolver-resolv: exited 0.2022-07-23 22:37:31stdout[fix-attrs.d] 01-resolver-resolv: applying... 2022-07-23 22:37:31stdout[fix-attrs.d] applying ownership & permissions fixes...2022-07-23 22:37:30stdout[s6-init] ensuring user provided files have correct perms...exited 0.2022-07-23 22:37:30stdout[s6-init] making user provided files available at /varun/s6/etc...exited 0.2022-07-23 22:37:04stdout[s6-finish] sending all processes the KILL signal and exiting.2022-07-23 22:37:01stdout[s6-finish] sending all processes the TERM signal.2022-07-23 22:37:01stdout[s6-finish] waiting for services.2022-07-23 22:37:01stdout[cont-finish.d] done.2022-07-23 22:37:01stdout[cont-finish.d] executing container finish scripts...2022-07-23 22:37:01stdout[cont-init.d] 20-start.sh: exited 1.2022-07-23 22:37:01stdout If you are seeing this error, please set the environment variable 'DNSMASQ_USER' to the value 'root'2022-07-23 22:37:01stdoutERROR: Unable to set capabilities for pihole-FTL. Cannot run as non-root.2022-07-23 22:37:01stdoutThe value of the capability argument is not permitted for a file. Or the file is not a regular (non-symlink) file2022-07-23 22:37:01stdoutFailed to set capabilities on file `/usbin/pihole-FTL' (Operation not supported)2022-07-23 22:37:00stdout ::: Starting docker specific checks & setup for docker pihole/pihole2022-07-23 22:37:00stdout[cont-init.d] 20-start.sh: executing... 2022-07-23 22:37:00stdout[cont-init.d] 05-changer-uid-gid.sh: exited 0.2022-07-23 22:36:59stdout[cont-init.d] 05-changer-uid-gid.sh: executing... 2022-07-23 22:36:59stdout[cont-init.d] executing container initialization scripts...2022-07-23 22:36:59stdout[fix-attrs.d] done.2022-07-23 22:36:59stdout[fix-attrs.d] 01-resolver-resolv: exited 0.2022-07-23 22:36:59stdout[fix-attrs.d] 01-resolver-resolv: applying... 2022-07-23 22:36:59stdout[fix-attrs.d] applying ownership & permissions fixes...2022-07-23 22:36:59stdout[s6-init] ensuring user provided files have correct perms...exited 0.2022-07-23 22:36:59stdout[s6-init] making user provided files available at /varun/s6/etc...exited 0.2022-07-23 22:36:37stdout[s6-finish] sending all processes the KILL signal and exiting.2022-07-23 22:36:34stdout[s6-finish] sending all processes the TERM signal.2022-07-23 22:36:34stdout[s6-finish] waiting for services.2022-07-23 22:36:34stdout[cont-finish.d] done.2022-07-23 22:36:34stdout[cont-finish.d] executing container finish scripts...2022-07-23 22:36:34stdout[cont-init.d] 20-start.sh: exited 1.2022-07-23 22:36:34stdout If you are seeing this error, please set the environment variable 'DNSMASQ_USER' to the value 'root'2022-07-23 22:36:34stdoutERROR: Unable to set capabilities for pihole-FTL. Cannot run as non-root.2022-07-23 22:36:34stdoutThe value of the capability argument is not permitted for a file. Or the file is not a regular (non-symlink) file2022-07-23 22:36:34stdoutFailed to set capabilities on file `/usbin/pihole-FTL' (Operation not supported)2022-07-23 22:36:33stdout ::: Starting docker specific checks & setup for docker pihole/pihole2022-07-23 22:36:32stdout[cont-init.d] 20-start.sh: executing... 2022-07-23 22:36:32stdout[cont-init.d] 05-changer-uid-gid.sh: exited 0.2022-07-23 22:36:31stdout[cont-init.d] 05-changer-uid-gid.sh: executing... 2022-07-23 22:36:31stdout[cont-init.d] executing container initialization scripts...2022-07-23 22:36:31stdout[fix-attrs.d] done.2022-07-23 22:36:31stdout[fix-attrs.d] 01-resolver-resolv: exited 0.2022-07-23 22:36:30stdout[fix-attrs.d] 01-resolver-resolv: applying... 2022-07-23 22:36:30stdout[fix-attrs.d] applying ownership & permissions fixes...2022-07-23 22:36:30stdout[s6-init] ensuring user provided files have correct perms...exited 0.2022-07-23 22:36:30stdout[s6-init] making user provided files available at /varun/s6/etc...exited 0. 

I just tried updating my months old install I have on a pi 3 B+ but it didn't seem to finish. I ran the commands the official documentation listed, first I ran docker pull pihole/pihole. Once that was done I ran docker rm -f pihole, and then I ran docker run pihole/pihole. it mentioned but I had no idea what to put so I ignored it. It seemed to run fine but then it just stopped. This is what it output before stopping:

[s6-init] making user provided files available at /varun/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] 05-changer-uid-gid.sh: executing... [cont-init.d] 05-changer-uid-gid.sh: exited 0. [cont-init.d] 20-start.sh: executing... ::: Starting docker specific checks & setup for docker pihole/pihole cap[cap_net_admin] not permitted cap[cap_sys_nice] not permitted Assigning random password: [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 Existing DNS servers detected in setupVars.conf. Leaving them alone [✓] New password set DNSMasq binding to default interface: eth0 Added ENV to php: "TZ" => "", "PIHOLE_DOCKER_TAG" => "2022.05", "PHP_ERROR_LOG" => "/valog/lighttpd/error.log", "ServerIP" => "0.0.0.0", "CORS_HOSTS" => "", "VIRTUAL_HOST" => "0.0.0.0", Using IPv4 and IPv6 ::: setup_blocklists now setting default blocklists up: ::: TIP: Use a docker volume for /etc/pihole/adlists.list if you want to customize for first boot ::: Blocklists (/etc/pihole/adlists.list) now set to: https://raw.githubusercontent.com/StevenBlack/hosts/mastehosts ::: Testing lighttpd config: Syntax OK ::: All config checks passed, cleared for startup ... ::: Enabling Query Logging [i] Enabling logging... [✓] Logging has been enabled! ::: Docker start setup complete Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf Pi-hole version is v5.10 (Latest: v5.10) AdminLTE version is v5.12 (Latest: v5.12) FTL version is v5.15 (Latest: v5.15) Container tag is: 2022.05 [cont-init.d] 20-start.sh: exited 0. [cont-init.d] done. [services.d] starting services Starting crond Starting pihole-FTL (no-daemon) as pihole Starting lighttpd [services.d] done. 

It's been sitting like that for 20 minutes now. I can't access the webui not surprisingly. What do I do? I've never been comfortable with command line interfaces.

The Issue: My pi-hole web interface spits out the following error when opening certain menus, such as the "Local DNS" and "DNS Records" Tab:
DataTables warning: table id=customDNSTable - Invalid JSON response. For more information about this error, please see http://datatables.net/tn/1
​
The Reason: Pi-hole does something wacky with the way the proxy is set up. I'm not quite sure I understand the issue fully, but the following fix should resolve the issue. For more information, see the credit link below to get a more detailed explanation on the fix.
​
Credit: https://www.dataone.nz/2022/01/17/invalid-json-response-nginx-docke
​
The Fix: This fix assumes you are running a docker instance of pi-hole. But don't worry. If not, the same fix can be applied to your regular installation, just skip the first step, and continue.
​
Step 1 (If using docker only):
Step 1 is to get access to a terminal inside of your docker container. If you aren't using docker for your installation, you can skip this step. Execute the following commands to do so:
sudo docker ps
Note the docker container name that is running pi-hole. Use the container name in the following command:
docker exec -it /bin/bash
You should now be running a terminal inside of your docker container.
Step 2 (For all types of installations):
Once in the proper terminal, go ahead and update your apt repositories. Then, install nano to edit a file later on. Do this using:
apt update
apt install nano
Then, use nano to edit a lighttpd file that is a part of your pi-hole installation. If this file is empty, do not worry, as it is most likely devoid of text by default. Do this using the following command:
nano /etc/lighttpd/external.conf
Inside of this now opened file, add the following line. Replace with your fully qualified domain name that you use to access the pi-hole web interface.
setenv.add-environment = ( "VIRTUAL_HOST" => "" )
Save this file by hitting ctrl + x, and then Enter.
Step 3 (For all types of installations):
While remaining in the same terminal you are working in, type the following command to restart the lighttpd service:
service lighttpd restart
Now, you're all set.
This should hopefully fix your issue if your pi-hole web interface is behind a proxy service.
​
For any additional questions, please don't hesitate to ask in the comments, or to send a direct message. I will attempt to get back to you as soon as possible, but I am just a simple man, so times may vary.

Everything was working fine, but this morning I ran updates on my Pi 400 and one of these included a docker update. All my other Docker containers are fine, only the pihole one is having problems.
I have tried creating a new container and redownloading the latest image, but it's doing the exact same thing. Set up different volumes to make sure it's not using any old data as well, again same thing.
New temporary yaml setup, super basic. Network mode host because I want to use DHCP on it.

version: "3" services: pihole: container_name: pihole2basic image: pihole/pihole:latest network_mode: "host" environment: TZ: 'Europe/London' volumes: - '/dockepihole2basic/config:/etc/pihole' - '/dockepihole2basic/dnsmasq.d:/etc/dnsmasq.d' cap_add: - NET_ADMIN restart: unless-stopped 

Logs from docker shows FTL having problems

[s6-init] making user provided files available at /varun/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] 05-changer-uid-gid.sh: executing... [cont-init.d] 05-changer-uid-gid.sh: exited 0. [cont-init.d] 20-start.sh: executing... ::: Starting docker specific checks & setup for docker pihole/pihole Assigning random password: Vy3QxonJ [i] Installing configs from /etc/.pihole... [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone! [i] Installing /etc/dnsmasq.d/01-pihole.conf... [✓] Installed /etc/dnsmasq.d/01-pihole.conf [i] Installing /etc/.pihole/advanced/06-rfc6761.conf... [✓] Installed /etc/dnsmasq.d/06-rfc6761.conf Configuring default DNS servers: 8.8.8.8, 8.8.4.4 [✓] New password set DNSMasq binding to default interface: eth0 Added ENV to php: "TZ" => "Europe/London", "PIHOLE_DOCKER_TAG" => "2022.02.1", "PHP_ERROR_LOG" => "/valog/lighttpd/error.log", "ServerIP" => "0.0.0.0", "CORS_HOSTS" => "", "VIRTUAL_HOST" => "0.0.0.0", Using IPv4 and IPv6 ::: setup_blocklists now setting default blocklists up: ::: TIP: Use a docker volume for /etc/pihole/adlists.list if you want to customize for first boot ::: Blocklists (/etc/pihole/adlists.list) now set to: https://raw.githubusercontent.com/StevenBlack/hosts/mastehosts ::: Testing lighttpd config: Syntax OK ::: All config checks passed, cleared for startup ... ::: Enabling Query Logging [i] Enabling logging... [✓] Logging has been enabled! ::: Docker start setup complete Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf Pi-hole version is v5.9 (Latest: v5.9) AdminLTE version is v5.11 (Latest: v5.11) FTL version is v5.14 (Latest: v5.14) Container tag is: 2022.02.1 [cont-init.d] 20-start.sh: exited 0. [cont-init.d] done. [services.d] starting services Starting crond Starting pihole-FTL (no-daemon) as pihole Starting lighttpd [services.d] done. Stopping pihole-FTL pihole-FTL: no process found Starting pihole-FTL (no-daemon) as pihole Stopping pihole-FTL pihole-FTL: no process found Starting pihole-FTL (no-daemon) as pihole Stopping pihole-FTL Starting pihole-FTL (no-daemon) as pihole Stopping pihole-FTL pihole-FTL: no process found Starting pihole-FTL (no-daemon) as pihole Stopping pihole-FTL pihole-FTL: no process found Starting pihole-FTL (no-daemon) as pihole Stopping pihole-FTL pihole-FTL: no process found Starting pihole-FTL (no-daemon) as pihole Stopping pihole-FTL pihole-FTL: no process found Starting pihole-FTL (no-daemon) as pihole Stopping pihole-FTL pihole-FTL: no process found Starting pihole-FTL (no-daemon) as pihole Stopping pihole-FTL pihole-FTL: no process found 

Ağ Web Sunucusu Nedir? İnternet Sunucuları Nelerdir?
​
İnternetin ortaya her türlü bilgiyi web sitelerinden elde ediyoruz sadece bilgi değil video, görsel ve ses gibi pek çok dokümandan faydalanıyoruz fakat bu dokümanları internet siteleri nasıl saklıyor ve ağ sunucusu ile web sunucusu nedir diye merak ediyor olabilirsiniz.
​
Hazırladığımız bu yazımızda ağ sunucusu ve internet sunucuları üzerine detaylı bir yazı hazırladık bu yazımızda web sunucusu seçerken dikkat etmeniz gerekenler, web sunucusu ne demek, web sunucusu nasıl çalışır gibi pek çok sorunun cevabını bulabileceksiniz.
​
Web Sunucusu Fiziksel Görünümü
Web Sunucusu Nedir?
​
Web sunucusu veya ağ sunucusu, web sitelerin barındırılabilmesi için internet protokolünü kullanarak barındırma ve hosting hizmeti vermektedir. Web sunucusu veya hosting internet sitelerinin yayına alınıp ve barındırılabilmesi için sunucu firmaları tarafından kiralanmaktadır.
​
İstemci tarafından web sitelere yapılan tıklamalar doğrultusunda buna cevap veren ağ sunucuları web sitede yer alan dosyaları kullanıcılara yani istemciye http (hyper text transfer protocol) protokül dizisi kurallarına uygun olarak gönderir.
​
Tarayıcı, internet ve web sunucusu arasındaki ilişki
​
Ağ sunucuları, pek çok farklı işletim sistemlerinin yer aldığı bilgisayar içerisinde bulunan programlar tarafından çalışmaktadır. Ağ sunucuları yazılım programlarıdır. Yazılım olarak kullanılan ağ sunucuları bilgisayarların sahip olduğu cpu ve donanımlar tarafından yönetilmektedir.
​
Ağ sunucusu, web site içerisinde yayınlanan görsel ve yazılı dokümanların internette yer alabilmesi ve ziyaretçilerin ulaşabilmesi için bir sunucu firmasında yer alan bilgisayar içerisinde yer almasıdır.
​
Ağ sunucusu, internette yer alan sitelerin yayınlarını barındırdıkları hosting hizmeti veren firmalar tarafından karşılanmaktadır. Web sunucusu, ağ sunucusu, hosting veya server olarak isimlendirilmektedir.
​
Web Sunucusu Kapalı Ne Demek?
​
Bir web sitesini ziyaret ettiğiniz de karşınıza "Cloudflare Hatası 521" çıkabilir bu web sunucusu kapalı demektir. Bu hata sunucu tarafından kaynaklanmaktadır.
​
Cloudflare size yanıt vermediğinde karşınıza çıkmaktadır. Tarayıcı bağlanmaya çalışıyor fakat içerik dağıtıcı yani cloudflare veya wordpress web sunucunuz tarafından kabul edilmiyor.
​
Kaç Çeşit Web Sunucusu Vardır?
​
Web sunucuları yani hosting çeşitleri birden fazladır. Bu hosting çeşitleri genellikle kullanıcının ihtiyaçlarına ve kullanım şekline göre farklılık değiştirir.
​
Kiralık sunucu (dedicated server)
Bulut sunucu (cloud server)
Paylaşımlı Hosting Sunucu
Sanal Özel Sunucu VPS (virtual private server)
Web Sunucusu ve Hosting Çeşitleri
Kiralık Sunucu Nedir? (dedicated server)
​
Kiralık sunucu, diğer sunuculara kıyasla daha fazla maliyetli olan ve tamamen kontrolünün size ait olduğu bir sunucu çeşididir. Kiralık sunucuları genellikle büyük web siteler kullanmaktadır. Özel isteklere göre tasarlanır ve ram gücü daha fazladır.
​
Güvenilirdir.
Hızlıdır.
Kapsamlı Kontrol
Tasarım imkanı.
Bulut Sunucu Nedir? (Cloud Server)
​
Bulut sunucu, kullanıcının istediği zaman da ve istediği yerde sahip olduğu sunucuya ulaşabilme ve doküman yükleyip paylaşabilme imkanı sunmaktadır. Fiziksel olarak çalışan sunucuların sanal olarak çalışması mantığı uygulanmaktadır. Kolay olmasından dolayı daha çok tercih edilmektedir.
​
Rahat Yönetim.
Hızlı Ulaşım.
Kolay Kullanım.
Paylaşımlı Hosting Nedir?
​
Paylaşımlı hosting, birden fazla web sitesinin ortak şekilde bir sunucuyu kullanmasıdır. Sunucuyu birden fazla kullanan web sitelerin ne kadar sunucunun kaynaklarını kullandığı bilinmez. Fakat kullanıcıların hepsi sunucudan belirli sınırda faydalanma hakkına sahiptir.
​
Ucuzdur.
Güvenilirdir.
Sanal Özel Sunucu Nedir?
​
Sanal Özel Sunucu VPS, Çok büyük bir sunucu içerisinde yer alan başka bir sunucudur. Sanal özel sunucularda web site sunucu imkanlarını diğer siteler ile paylaşmaz. Bunu genellikle büyük kurumlar kullanmaktadır. En çok kullanılan sunucular arasında yer almaktadır.
​
Maliyeti Fazladır.
Güvenilirdir.
Kalitelidir.
Tasarım İmkanı Sunar.
​
​
​
​
Ağ Web Sunucusu Nasıl Çalışır?
​
Web sunucular bilgisayarlara kıyasla daha gelişmiş ve daha hızlı bir yapıya sahiptir. Web sunucuların çalışması için CPU genellikle çok daha büyüktür.
​
Web sunucusu içerisinde yer alan internet sitelerine erişim imkanı sağlanabilmesi için her siteye benzersiz bir IP Adresi atanır.
​
IP Adreslerinin rakamları çok uzun olduğunda domain seçimi yapılır. IP adresleri domainin karşılığıdır. 0 ve 255 arasında kalan dört sayının bir araya gelmesiyle oluşan IP Adresleri bir siteye atanır.
​
İnternette dolaşım yapan ziyaretçiler bir web sitesine ulaşabilmek için web sitenin domaini yani ıp adresini arama çubuğuna yazıp tıklayarak ulaşmaktadır. IP Adresleri ile DNS sistemi birbirlerine bağlı olarak çalışmaktadır. Arama çubuğuna ister IP ister Domain adını yazın ulaşacağınız site aynı olacaktır.
​
DNS ve IP adreslerinin birbirlerine bağlı olmasından dolayı kullanıcı arama yaptığında web sunucusu içerisinde depolanan web sitenin verileri sunucunun karşısına görsel olarak çıkacaktır.
​
Web sunucusu yani server kullanıcıya site ile ilgili görseller, dokümanlar ve canlı kullanım imkanını sunmaktadır. Web sunucusu ziyaretçilere web sitenin canlı halini sunabilmek için Ngnix ve apachi gibi yazılımları kullanmaktadır.
​
​
​
​
Web Sunucu Programları
​
Web sitelerin internet içerisinde yer alabilmesi için server yani internet ağ sunucularına ihtiyaçları vardır. Web sitenin yer alacağı internet sunucusu yazılımı markalara ve ihtiyaçlara göre farklılık göstermektedir.
​
Web sunucusu seçerken hangi yazılımı kullandığını incelemek için ne işe yaradığı ve ne gibi özelliklere sahip olduğu hakkında bilgi sahibi olmanız gerekmektedir. Aşağı da yer alan web sunucu programları inceleyerek kendi ihtiyaçlarınıza uygun olarak web sunucusu programları seçebilirsiniz.
​
1- Apache HTTP Server
​
Apache, en çok bilinen internet sunucuları arasında yer almaktadır. Herkes tarafından bilinmesi ve geçmişten beri kullanması bu sektörde %40'lık bir pay sahibi olmasını sağlıyor. Apache programını sektörde yer alan herkes genellikle httpd olarak bilmektedir.
​
Apache programı güçlü bir web sunucu programları arasında yer alır. C ile yazılmış ve özel tasarımlara uygun bir programdır. Apache; IPv4, IPv6 ile HTTP, HTTP/2, HTTPS desteklemektedir.
​
2- Ngnix
​
Ngnix, internet sunucusu tıpkı diğer web sunucusu programları gibi geçmişten beri kullanılmakta ve güvenilir olduğunu kanıtlamıştır. Ngnix programı hızlı ve güvenilirdir kullanılması kolay olduğundan daha sık tercih edilen bir internet sunucusu yazılımıdır. Yük dengeleme özelliği ve ters apı desteği özelliğine sahiptir.
​
Dünyanın en büyük sosyal medya platformları olan twitter, facebook, linkedin gibi platformlara hizmet vermektedir.
​
3 – Lighttpd Web Server
​
Lighttpd, web sunucu programları arasında en az yer kaplayan ve kaynakları en tasarruflu şekilde kullanılması ve hızlı ücretsiz olmasından dolayı tercih edilmektedir. Açık kaynaklı bir yazılımdır. Windows ve linus, unix gibi platformlarda desteklenmektedir. Büyük bağlantıları işlemek için kullanılmaktadır. Çok büyük sunucularda çalışmak için tasarlanmıştır.
​
4 – Caddy Web Server
​
Caddy web server, programlama dili olarak "go" kullanmaktadır. Web sunucu programları arasında caddy web server hızlı ve dengeleyici özelliğine sahiptir. ek paket alma gibi imkanlardan kurtulma imkanı sunduğu için önemli bir yazılım programıdır.
​
Go programlama dili kullanılarak yazılan Caddy Web Server; hız ve çoklu platform desteğinin yanı sıra yük dengeleyici, API gateway ve ters proxy sunuyor. İhtiyaç duyduğu tüm paketleri içerisinde bulunduran bu web sunucusu, ek paket yükleme derdinden kurtarıp kurulumu oldukça kolay kılıyor.
​
5 – OpenLiteSpeed Web Server
​
Litespeed, web sunucu programı açık kaynaklı bir yazılımdır. Hızlı ve basit olmasından dolayı herkes tarafından tercih edilmektedir. Basit ve kolay kullanımından dolayı kullanım oranları artmaktadır.
​
İlginizi Çekebilecek İçeriklerimiz
​
Backlink Analiz Aracı
​
SEO title nedir
​
Sosyal İmleme Siteleri
​
Ağ Sunucuları ve SEO İlişkisi Nedir?
​
Ağ sunucuları web siteleri barındırmaları ve ziyaretçilere web site ile ilgili dokümanları sunmaları açısından önemli olduğu gibi SEO açısından da oldukça önemlidir.
​
Ağ sunucularının web siteleri hızlı yüklemesi ve kullanıcı isteklerine hızlı cevap verebilmesi sitenin hızlı yüklenmesini sağlar. Sitenin hızlı yüklenmesini sağlayan ağ sunucusu kullanıcı deneyimini de arttıracaktır.
​
SEO açısından ağ sunucusunun hızlı çalışması dışında güvenilir olması ve herhangi bir saldırıya karşı güvenli olması gerekmektedir. SEO açısından içeriklerimizi video ve görsel ile kurguladığımız için saklama alanı her zaman önemlidir bu yüzden saklama alanı açısından size geniş imkan sunan bir ağ sunucusu her zaman faydalıdır.
​
Web Sunucusu ile mobil telefon ve bilgisayar arasındaki ilişki
​
Kaynak
​
Wikipedi Web Sunucusu Nedir?
​
Developer Mozilla Web Sunucusu Nedir?

When pulling the latest docker release (2022.02.1), pihole will not start.

[s6-init] making user provided files available at /varun/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] 05-changer-uid-gid.sh: executing... [cont-init.d] 05-changer-uid-gid.sh: exited 0. [cont-init.d] 20-start.sh: executing... ::: Starting docker specific checks & setup for docker pihole/pihole [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 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 default interface: eth0 Added ENV to php: "TZ" => ""America/New_York"", "PIHOLE_DOCKER_TAG" => "2022.02.1", "PHP_ERROR_LOG" => "/valog/lighttpd/error.log", "ServerIP" => "10.0.0.25", "CORS_HOSTS" => "", "VIRTUAL_HOST" => "pihole", Using IPv4 and IPv6 ::: Preexisting ad list /etc/pihole/adlists.list detected ((exiting setup_blocklists early)) https://raw.githubusercontent.com/StevenBlack/hosts/mastehosts https://mirror1.malwaredomains.com/files/justdomains ::: Testing lighttpd config: 2022-02-14 13:46:06: (configfile.c.1238) source: /etc/lighttpd/conf-enabled/15-fastcgi-php.conf line: 12 pos: 19 invalid character in variable name 2022-02-14 13:46:06: (configfile.c.1293) configfile parser failed at: America 2022-02-14 13:46:06: (configfile.c.1296) source: find /etc/lighttpd/conf-enabled -name '*.conf' -a ! -name 'letsencrypt.conf' -printf 'include "%p"\n' 2>/dev/null line: 3 pos: 8 parser failed somehow near here: (EOL) 2022-02-14 13:46:06: (configfile.c.1296) source: /etc/lighttpd/lighttpd.conf line: 75 pos: 1 parser failed somehow near here: (EOL) [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. 

I temporarily fixed the issue by manually pulling and using 2022.01.1
I don't quite understand this error message if anyone could help.

I have an issue I would like some help with please. I've been banging my head against this for a while, but the only solution I can figure out is to specify the IP of the pihole container as the dns for the service in docker-compose.yml, but then I ran into issues with errors about the address already being in use when re-running docker-compose up, and pihole still having this issue. I'm trying to avoid specifying any IPs so that Docker can handle all of that.
​
THE PROBLEM:
From what I can tell, when I try to perform a DNS query from within a container the container never receives a response. Weirdly, this also applies if I try to run a query from within the pihole container. I can see in the pihole logs that the queries reach pihole, pihole is able to look up the DNS record, and then replies, but the container always times out. However, all queries from clients on my LAN 192.168.0.0/23 are able to resolve queries fine. In the pihole GUI it also shows -2 in the Domains on Blocklist area, which I assume is because the container cannot query something it needs to set up initially.
​
THE ENVIRONMENT:
My Docker host is a Ubuntu 21.10 machine at 192.168.1.10 with ufw. The router and firewall for the LAN is a Ubiquiti UDM-PRO at 192.168.1.1. There are no firewall rules beyond the default configured on the UDM-PRO. The ufw rules are below:

$ sudo ufw status numbered Status: active To Action From -- ------ ---- [ 1] 22/tcp ALLOW IN Anywhere [ 2] 192.168.1.10 53 ALLOW IN 192.168.0.0/23 [ 3] 192.168.1.10 53 ALLOW IN 172.16.0.0/12 [ 4] 22/tcp (v6) ALLOW IN Anywhere (v6) 

If I disable ufw there is no change in behavior:

$ sudo ufw disable [sudo] password for user: Firewall stopped and disabled on system startup user@host:/directory/$ docker exec -it pihole bash root@270330f4cca6:/# nslookup abc.com ;; connection timed out; no servers could be reached 

​
Per pihole's documentation I ran the following commands on my Docker host:

sudo sed -r -i.orig 's/#?DNSStubListener=yes/DNSStubListener=no/g' /etc/systemd/resolved.conf sudo sh -c 'rm /etc/resolv.conf && ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf' systemctl restart systemd-resolved 

And also configured pihole's upstream DNS to 192.168.1.1 and my UDM-PRO's DHCP Name Server to 192.168.1.10 per their other documentation.
Here is my docker-compose.yml:

networks: br0: driver: bridge services: ddclient: container_name: ddclient environment: - PUID=1001 - PGID=1002 - TZ=America/Chicago image: lscr.io/linuxserveddclient networks: - br0 restart: unless-stopped volumes: - '/directory/:/config' pihole: cap_add: - CAP_NET_BIND_SERVICE container_name: pihole env_file: /directory/pihole.env image: pihole/pihole:latest networks: - br0 ports: - "53:53/tcp" - "53:53/udp" - "80:80/tcp" restart: unless-stopped volumes: - '/directory/etc-pihole:/etc/pihole/' - '/directory/etc-dnsmasq:/etc/dnsmasq.d/' 

​
Here are the logs from the ddclient container:

$ docker logs -f ddclient [s6-init] making user provided files available at /varun/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] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 01-envfile: executing... [cont-init.d] 01-envfile: exited 0. [cont-init.d] 01-migrations: executing... [migrations] started [migrations] no migrations found [cont-init.d] 01-migrations: exited 0. [cont-init.d] 02-tamper-check: executing... [cont-init.d] 02-tamper-check: exited 0. [cont-init.d] 10-adduser: executing... ------------------------------------- _ () ___ _ __ / __ / \ \__ \ () _ ___/ _ \__/ Brought to you by linuxserver.io ------------------------------------- To support LSIO projects visit: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 1001 User gid: 1002 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30-config: executing... [cont-init.d] 30-config: exited 0. [cont-init.d] 90-custom-folders: executing... [cont-init.d] 90-custom-folders: exited 0. [cont-init.d] 99-custom-files: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-files: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. Setting up watches. Watches established. CONNECT: ipinfo.io WARNING: cannot connect to ipinfo.io:80 socket: IO::Socket::INET: Bad hostname 'ipinfo.io' WARNING: found neither ipv4 nor ipv6 address WARNING: unable to determine IP address WARNING: file /vacache/ddclient/ddclient.cache, line 3: Invalid Value for keyword 'ip' = '' 

​
Here are the logs from the pihole container:

$ docker logs -f pihole [s6-init] making user provided files available at /varun/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 1. [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] 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 chmod: cannot access '/etc/pihole/pihole-FTL.db': No such file or directory Setting DNS servers based on PIHOLE_DNS_ variable Setting Web Theme based on WEBTHEME variable, using value default-dark [✓] New password set [✓] Set temperature unit to F DNSMasq binding to default interface: eth0 Added ENV to php: "PIHOLE_DOCKER_TAG" => "2022.01.1", "PHP_ERROR_LOG" => "/valog/lighttpd/error.log", "ServerIP" => "192.168.1.10", "CORS_HOSTS" => "", "VIRTUAL_HOST" => "192.168.1.10", Using IPv4 and IPv6 ::: setup_blocklists now setting default blocklists up: ::: TIP: Use a docker volume for /etc/pihole/adlists.list if you want to customize for first boot ::: Blocklists (/etc/pihole/adlists.list) now set to: https://raw.githubusercontent.com/StevenBlack/hosts/mastehosts ::: Testing pihole-FTL DNS: FTL started! ::: Testing lighttpd config: Syntax OK ::: All config checks passed, cleared for startup ... ::: Enabling Query Logging [i] Enabling logging... [✓] Logging has been enabled! ::: Docker start setup complete Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf Pi-hole version is v5.8.1 (Latest: ERROR) AdminLTE version is v5.10.1 (Latest: ERROR) FTL version is v5.13 (Latest: ERROR) Container tag is: 2022.01.1 [cont-init.d] 20-start.sh: exited 0. [cont-init.d] done. [services.d] starting services Starting pihole-FTL (no-daemon) as pihole Starting lighttpd Starting crond [services.d] done. 

​
Here is some useful info from the ddclient container:

user@host:/directory/$ docker exec -it ddclient bash root@ede82f10c712:/# ping pihole PING pihole (172.18.0.3): 56 data bytes 64 bytes from 172.18.0.3: seq=0 ttl=64 time=0.181 ms 64 bytes from 172.18.0.3: seq=1 ttl=64 time=0.087 ms ^C --- pihole ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max = 0.087/0.134/0.181 ms root@ede82f10c712:/# nslookup ipinfo.io ;; connection timed out; no servers could be reached root@ede82f10c712:/# cat /etc/resolv.conf search localdomain nameserver 127.0.0.11 options ndots:0 

​
Here is some useful info from the pihole container:

user@host:/directory/$ docker exec -it pihole bash root@270330f4cca6:/# ping ddclient PING ddclient (172.18.0.2) 56(84) bytes of data. 64 bytes from ddclient.homelab_br0 (172.18.0.2): icmp_seq=1 ttl=64 time=0.148 ms 64 bytes from ddclient.homelab_br0 (172.18.0.2): icmp_seq=2 ttl=64 time=0.053 ms 64 bytes from ddclient.homelab_br0 (172.18.0.2): icmp_seq=3 ttl=64 time=0.067 ms ^C --- ddclient ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 48ms rtt min/avg/max/mdev = 0.053/0.089/0.148/0.042 ms root@270330f4cca6:/# nslookup ipinfo.io ;; connection timed out; no servers could be reached root@270330f4cca6:/# cat /etc/resolv.conf search localdomain nameserver 127.0.0.11 options ndots:0 

Here's the rundown on how I got here.

Using port 81:80 in yml file, pihole web interface works Switches to network_mode: host on the yml file to enable dchp on pihole Realize network_mode doesn't support Windows, open ports back to what it was before which was 81:80 Realize I suddenly can't access web interface, but pihole still is running Set port to 82:80 in yml file, now can access web interface. 

Whenever I connect to pihole interface with port 81, I get an error in all my browsers saying ERR_SSL_PROTOCOL_ERROR.
I checked my used ports in windows with resource monitor and port 81 wasn't used. And no other docker container is running except pihole.
I even reinstalled docker and nothing, same problem.

Here's my yml file that I'm currently using for pihole.

version: "3" # More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/ services: pihole: container_name: pihole image: pihole/pihole:latest ports: - "53:53/tcp" - "53:53/udp" - "67:67/udp" - "82:80/tcp" environment: ServerIP: '192.168.0.25' TZ: 'America/New_York' WEBPASSWORD: 'lol no' # Volumes store your data between container upgrades volumes: - './etc-pihole/:/etc/pihole/' - './etc-dnsmasq.d/:/etc/dnsmasq.d/' # Recommended but not required (DHCP needs NET_ADMIN) # https://github.com/pi-hole/docker-pi-hole#note-on-capabilities cap_add: - NET_ADMIN restart: unless-stopped 

Here's the logs from docker.

[s6-init] making user provided files available at /varun/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 1. [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] 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 Existing DNS servers detected in setupVars.conf. Leaving them alone ::: Pre existing WEBPASSWORD found DNSMasq binding to default interface: eth0 Added ENV to php: "PIHOLE_DOCKER_TAG" => "2022.01.1", "PHP_ERROR_LOG" => "/valog/lighttpd/error.log", "ServerIP" => "192.168.0.25", "CORS_HOSTS" => "", "VIRTUAL_HOST" => "192.168.0.25", Using IPv4 and IPv6 ::: Preexisting ad list /etc/pihole/adlists.list detected ((exiting setup_blocklists early)) https://raw.githubusercontent.com/StevenBlack/hosts/mastehosts ::: Testing pihole-FTL DNS: FTL started! ::: Testing lighttpd config: Syntax OK ::: All config checks passed, cleared for startup ... ::: Enabling Query Logging [i] Enabling logging... [✓] Logging has been enabled! ::: Docker start setup complete Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf Pi-hole version is v5.8.1 (Latest: v5.8.1) AdminLTE version is v5.10.1 (Latest: v5.10.1) FTL version is v5.13 (Latest: v5.13) Container tag is: 2022.01.1 [cont-init.d] 20-start.sh: exited 0. [cont-init.d] done. [services.d] starting services Starting lighttpd Starting crond Starting pihole-FTL (no-daemon) as pihole [services.d] done. Stopping pihole-FTL kill: usage: kill [-s sigspec -n signum -sigspec] pid jobspec ... or kill -l [sigspec] Starting pihole-FTL (no-daemon) as pihole 

Hi everyone,
i've a problem with hosting PiHole with docker on my machine. I'm running OpenMediaVault with docker installed. Via portainer i'm using below stack:

 pihole: container_name: pihole image: pihole/pihole:latest ports: - "53:53/tcp" - "53:53/udp" - "67:67/udp" - "83:80/tcp" environment: - PUID=0 - PGID=0 - TZ=${TZ} - WEBPASSWORD=${PIHOLE_WEBPASSWORD} volumes: - ${config_storage_path}pihole/etc-pihole/:/etc/pihole/ - ${config_storage_path}pihole/etc-dnsmasq.d/:/etc/dnsmasq.d/ - ${config_storage_path}pihole/var-log/pihole.log:/valog/pihole.log networks: - infrastructure_default cap_add: - NET_ADMIN restart: unless-stopped 

Starting the container is working fine:

2022-02-04T10:27:47.615889685Z Stopping cron 2022-02-04T10:27:47.615940525Z Stopping pihole-FTL 2022-02-04T10:27:47.616013726Z Stopping lighttpd 2022-02-04T10:27:47.621227944Z [cont-finish.d] executing container finish scripts... 2022-02-04T10:27:47.621677634Z [cont-finish.d] done. 2022-02-04T10:27:47.621909625Z [s6-finish] waiting for services. 2022-02-04T10:27:47.827837594Z [s6-finish] sending all processes the TERM signal. 2022-02-04T10:27:50.841922516Z [s6-finish] sending all processes the KILL signal and exiting. 2022-02-04T10:27:51.663657512Z [s6-init] making user provided files available at /varun/s6/etc...exited 0. 2022-02-04T10:27:51.681753435Z [s6-init] ensuring user provided files have correct perms...exited 0. 2022-02-04T10:27:51.682584459Z [fix-attrs.d] applying ownership & permissions fixes... 2022-02-04T10:27:51.683495139Z [fix-attrs.d] 01-resolver-resolv: applying... 2022-02-04T10:27:51.684227453Z [fix-attrs.d] 01-resolver-resolv: exited 1. 2022-02-04T10:27:51.684675796Z [fix-attrs.d] done. 2022-02-04T10:27:51.685253695Z [cont-init.d] executing container initialization scripts... 2022-02-04T10:27:51.686113540Z [cont-init.d] 20-start.sh: executing... 2022-02-04T10:27:51.715317210Z ::: Starting docker specific checks & setup for docker pihole/pihole 2022-02-04T10:27:51.724937180Z 2022-02-04T10:27:51.724944793Z [i] Installing configs from /etc/.pihole... 2022-02-04T10:27:51.726098647Z [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone! 2022-02-04T10:27:51.726689083Z [i] Installing /etc/dnsmasq.d/01-pihole.conf... [✓] Installed /etc/dnsmasq.d/01-pihole.conf 2022-02-04T10:27:51.759143051Z [i] Installing /etc/.pihole/advanced/06-rfc6761.conf... [✓] Installed /etc/dnsmasq.d/06-rfc6761.conf 2022-02-04T10:27:51.791543926Z Existing DNS servers detected in setupVars.conf. Leaving them alone 2022-02-04T10:27:51.792209537Z ::: Pre existing WEBPASSWORD found 2022-02-04T10:27:51.792324118Z DNSMasq binding to default interface: eth0 2022-02-04T10:27:51.811588148Z Added ENV to php: 2022-02-04T10:27:51.812127278Z "PIHOLE_DOCKER_TAG" => "2022.01.1", 2022-02-04T10:27:51.812134525Z "PHP_ERROR_LOG" => "/valog/lighttpd/error.log", 2022-02-04T10:27:51.812136682Z "ServerIP" => "0.0.0.0", 2022-02-04T10:27:51.812138414Z "CORS_HOSTS" => "", 2022-02-04T10:27:51.812140020Z "VIRTUAL_HOST" => "0.0.0.0", 2022-02-04T10:27:51.815555598Z Using IPv4 and IPv6 2022-02-04T10:27:51.816300337Z ::: Preexisting ad list /etc/pihole/adlists.list detected ((exiting setup_blocklists early)) 2022-02-04T10:27:51.816669050Z https://raw.githubusercontent.com/StevenBlack/hosts/mastehosts 2022-02-04T10:27:51.986691983Z ::: Testing pihole-FTL DNS: FTL started! 2022-02-04T10:27:51.997300220Z ::: Testing lighttpd config: Syntax OK 2022-02-04T10:27:51.997483252Z ::: All config checks passed, cleared for startup ... 2022-02-04T10:27:51.998509643Z ::: Enabling Query Logging 2022-02-04T10:27:52.001949308Z [i] Enabling logging... 2022-02-04T10:27:52.003066307Z [✓] Logging has been enabled! 2022-02-04T10:27:52.003186207Z ::: Docker start setup complete 2022-02-04T10:27:52.003493142Z Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf 2022-02-04T10:27:52.010743967Z Pi-hole version is v5.8.1 (Latest: v5.8.1) 2022-02-04T10:27:52.014076873Z AdminLTE version is v5.10.1 (Latest: v5.10.1) 2022-02-04T10:27:52.016491012Z FTL version is v5.13 (Latest: v5.13) 2022-02-04T10:27:52.016628811Z Container tag is: 2022.01.1 2022-02-04T10:27:52.017062880Z [cont-init.d] 20-start.sh: exited 0. 2022-02-04T10:27:52.017586991Z [cont-init.d] done. 2022-02-04T10:27:52.018285739Z [services.d] starting services 2022-02-04T10:27:52.021548317Z Starting lighttpd 2022-02-04T10:27:52.021554872Z Starting pihole-FTL (no-daemon) as pihole 2022-02-04T10:27:52.021578763Z Starting crond 2022-02-04T10:27:52.022984996Z [services.d] done. 2022-02-04T10:27:52.251999907Z Stopping pihole-FTL 2022-02-04T10:27:53.022840014Z Starting pihole-FTL (no-daemon) as pihole 

While accessing the WebInterface there is no passward check and when i go to setting i find a red banner on top with the message:

 Error There was a problem applying your settings. Debugging information: PHP error (2): parse_ini_file(/etc/pihole/setupVars.conf): failed to open stream: Permission denied in /vawww/html/admin/settings.php:12 

I've tried to re-install with a completly empty mount, during container startup all files are recreating but issue persists.
Any idea how i can resolve this permission issue?
​
Thanks a lot!

I am running pihole in docker compse file as shown below:

 pihole: image: pihole/pihole:latest hostname: "pihole" user: "root:root" ports: - target: 53 published: 5300 mode: host protocol: udp - target: 80 published: 8085 mode: host volumes: - /etc/pihole:/etc/pihole - "/home/ansible/stacks/lighttpd/external.conf:/etc/lighttpd/external.conf" - dnsmasq:/etc/dnsmasq.d depends_on: - cloudflared - dnsmasq environment: - "DNS1=1.1.1.1" - "DNS2=8.8.4.4" - "REV_SERVER=true" - "REV_SERVER_CIDR=192.168.1.0/24" #Update these fields to match your environment - "REV_SERVER_TARGET=192.168.1.1" - "REV_SERVER_DOMAIN=home.local" - "WEBPASSWORD=secret" networks: - web deploy: labels: - "traefik.http.routers.pihole-http.rule=Host(`pihole.home.local`)" - "traefik.http.routers.pihole-http.entrypoints=web" - "traefik.http.middlewares.add-admin-prefix.addprefix.prefix=/admin" - "traefik.http.routers.pihole-http.middlewares=add-admin-prefix" - "traefik.http.services.pihole-http.loadbalancer.server.port=80" - "traefik.http.services.pihole-http.loadbalancer.passhostheader=true" - "traefik.http.services.pihole-http.loadbalancer.healthcheck.scheme=http" mode: replicated replicas: 1 placement: constraints: - "node.hostname==swarm-master" 

it runs fine, and if I use nmap I can see port 5300 is open:

$ sudo nmap -sU -p5300 10.100.192.200 Starting Nmap 7.01 ( https://nmap.org ) at 2022-01-03 22:34 UTC Nmap scan report for 10.100.192.200 Host is up (0.0021s latency). PORT STATE SERVICE 5300/udp openfiltered hacl-hb MAC Address: 08:00:27:AF:61:D3 (Oracle VirtualBox virtual NIC) Nmap done: 1 IP address (1 host up) scanned in 0.52 seconds 

But if I try nslookup on pihole server at port 5300 O get

$ nslookup google.com -port=5300 10.100.192.200 ;; connection timed out; no servers could be reached 

I can even ping from the swarm-node-1 which is running DNSMasq which has the pihole as first priority

$ ping 10.100.192.200 PING 10.100.192.200 (10.100.192.200) 56(84) bytes of data. 64 bytes from 10.100.192.200: icmp_seq=1 ttl=64 time=3.00 ms 64 bytes from 10.100.192.200: icmp_seq=2 ttl=64 time=1.19 ms ^C --- 10.100.192.200 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1003ms rtt min/avg/max/mdev = 1.199/2.100/3.002/0.902 ms 

I don't understand what has gone wrong here, that it cannot use the DNS service of this pihole running on 10.100.192.200
I am able to ping and resolve domain name when I enter the pihole container
this is from the mounted /etc/pihole volume:

# cat /etc/pihole/setupVars.conf BLOCKING_ENABLED=true INSTALL_WEB_SERVER=true INSTALL_WEB_INTERFACE=true REV_SERVER=true REV_SERVER_DOMAIN=home.local REV_SERVER_TARGET=192.168.1.1 REV_SERVER_CIDR=192.168.1.0/24 PIHOLE_DNS_1=1.1.1.1 PIHOLE_DNS_2=8.8.4.4 PIHOLE_INTERFACE=eth0 QUERY_LOGGING=true 

and

# cat pihole-FTL.conf REPLY_ADDR4=0.0.0.0 

any help will be greatly appreciated with awards.