any idea why I am getting this error when trying to query the log dates? I have setup a new pihole, just modified the http and https ports to 6000

I am having this weird issue where if i start the pihole docker, it changes the ip address of my entire server which messes with the already established dhcp reservation that i had set for it before hand. I thought that the pihole would count as its own device but in my router settings it does not appear as such. a little help would be appreciated.

Anyone is able to reach Pihole through Unraid wireguard?

My pihole docker is getting quite large - the container is 9.2 GB and the Writable column is 8.89GB.  How do I troubleshoot this and see what the cause is?  The pihole-FTL.db file is about 3.4GB but that appears to be in appdata.

 

What could be causing this?

 

edit - I updated the pihole docker and that fixed the problem.  The size fell by over 95% to 328MB.  Leaving this comment here in case it helps someone in the future.

Edited May 14, 20242 yr by wayner

On 5/14/2024 at 11:28 PM, wayner said:

My pihole docker is getting quite large - the container is 9.2 GB and the Writable column is 8.89GB.  How do I troubleshoot this and see what the cause is?  The pihole-FTL.db file is about 3.4GB but that appears to be in appdata.

 

What could be causing this?

 

edit - I updated the pihole docker and that fixed the problem.  The size fell by over 95% to 328MB.  Leaving this comment here in case it helps someone in the future.

Thanks for this! Force update the container shrunk the container size from 5GB to 300MB.  It must be a log file or something that should be mapped to the appdata dir instead of inside the container.  

I have an older unRAID server that was also getting the docker partition full problem.  I found a way to fix it on these forums - edit your docker and go into extra parameters.  Put this in --log-opt max-size=50m --log-opt max-file=1 as extra parameters and that is supposed to limit your logs to 50 MB each.

 

edit - Make sure that you have advanced mode turned on to see the extra parameters button.

Edited June 11, 20242 yr by wayner

All 4 of these issues are the same, and I am having this issue also. Can anyone help at all? I have seem many on Reddit also.

 

  

On 3/18/2023 at 6:29 PM, onesterkin said:

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

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

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

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

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

Thus DNS resolving is not available, etc.

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

 

  

On 11/22/2023 at 9:21 AM, independence said:

Hi all,

 

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

"While executing: attempt to write a readonly database"

 

Do you already know what went wrong?

 

Thanks

 

  

On 12/12/2023 at 1:28 PM, orlando500 said:

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

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

 

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

 

Edited September 20, 20241 yr by chrisp7

Aaand the solution was right in front of me in this post thank you (will spread this far and wide!)
 

 

Edited September 20, 20241 yr by chrisp7

On 6/11/2024 at 4:23 PM, wayner said:

I have an older unRAID server that was also getting the docker partition full problem.  I found a way to fix it on these forums - edit your docker and go into extra parameters.  Put this in --log-opt max-size=50m --log-opt max-file=1 as extra parameters and that is supposed to limit your logs to 50 MB each.

 

edit - Make sure that you have advanced mode turned on to see the extra parameters button.

I had that setting, yet my piHole had grown to 22+GB's. 

I removed it entirely and fixed the issue. 

 

I did, as I mentioned, have that log max-size setting enabled.. I have it for all my docker containers actually since Plex misbehaved one time. 

Anyone actually investigate the root cause? I have been noticing that piHole has essentially been blocking nothing in the WebUI. Updated configuration instructions or something, maybe? 

I agree in that the log max size is not working.  My log size got up to 4.6GB.  It seems like logs are being written to somewhere in the docker rather than the appdata folder.  This sure seems to be a bug to me.

2 hours ago, wayner said:

I agree in that the log max size is not working.  My log size got up to 4.6GB.  It seems like logs are being written to somewhere in the docker rather than the appdata folder.  This sure seems to be a bug to me.

Hi all

 

I created this template many years ago as a wrapper for the offical pihole docker and I am not surpised that a number of items may not work correctly. I changed my setup to use opnsense/adguard hence I have not seen the problems myself as I dont use it.

Regarding the logs, try creating a log directory in the pihole appdata directory and add the following path:

(run the docker for a while and see if the logs are written to the host instead of the container)

 

Thanks - I just did that and I see that the docker created a pihole folder off of my /appdata/pihole/log folder, as in /appdata/pihole/log/pihole,  and it has created two files so far - pihole.log and FTL.log.

 

So it seems to have worked. I will keep an eye on the docker size.

 

Thanks!

FYI, there seems to be another similar issue.  The pihole-FTL.db file also gets very large.  Currently this file is in /appdata/pihole/pihole on my server.

 

Apparently you can limit the amount of logging that goes to this database in the pihole-FTL.conf file.  I have to figure out how to do this.

@spants I believe one other action is needed - you need to create a lighttpd folder under the logs folder in appdata.

 

I noticed that pihole wasn't running so I checked the logs which showed the text below.  I manually created a /appdata/pihole/log/lighttpd folder and now it seems to work ok.  When the docker restarted it created files in that lighttpd folder.

 

install: cannot create regular file '/var/log/lighttpd/access-pihole.log': No such file or directory
install: cannot create regular file '/var/log/lighttpd/error-pihole.log': No such file or directory
chown: cannot access '/var/log/lighttpd': No such file or directory
chmod: cannot access '/var/log/lighttpd/access-pihole.log': No such file or directory
chmod: cannot access '/var/log/lighttpd/error-pihole.log': No such file or directory
2024-12-30 17:17:53: configfile.c.1290) opening errorlog '/var/log/lighttpd/error-pihole.log' failed: No such file or directory
2024-12-30 17:17:53: server.c.1509) Opening errorlog failed. Going down.
Stopping lighttpd
lighttpd: no process found

 

Edited December 30, 20241 yr by wayner
fix typo

well spotted - I dont run any install scripts in the template as it just uses the official docker image. With unraid, you may have to do these tweaks!....

 

I want to use pihole as a dns server together with npm in order to use local domain. I want to redirect 192.168.178.45:5055 to jellyseerr.local. To do so i followed this tutorial.

 

I created a new host in npm which use jellyseerr.local and points it to 192.168.178.45:5055. NPM itself is reachable under 192.168.178.2. After that i created a dns record in pihole which is jellyseerr.local -> 192.168.178.2. So i would guess, if a user tries to access jellyseerr.local, the network will look into npm because 192.168.178.2 and npm redirects to 192.168.178.45:5055. In reality nothing happens, jellyseerr.local is not reachable. I also added the ip of pihole (which is 192.168.178.45 as it runs on my unraid) in my FritzBox under network > network settings > ip v4 > local dns server.

 

What did i miss?

Unraid 7, pihole, tailscale

 

Hello all,

 

I tried to activate the new Tailscale support for my pihole container. Upon applying and restarting the container, it seems to be running but I cannot display the logfile or the console of the container. A window briefly pops up but closes immediately. Upon deactivating the tailscale feature in the container configuration, all is well again.

 

Has anyone had success with this so far?

 

Many thanks.

6 hours ago, AlainF said:

Unraid 7, pihole, tailscale

 

Hello all,

 

I tried to activate the new Tailscale support for my pihole container. Upon applying and restarting the container, it seems to be running but I cannot display the logfile or the console of the container. A window briefly pops up but closes immediately. Upon deactivating the tailscale feature in the container configuration, all is well again.

 

Has anyone had success with this so far?

 

Many thanks.

Same issue.

 

Tried with custom:br0 network, fixed serverIp. But it apparently can't download some of the tailscale packages needed...

 

 

  Temporary failure resolving 'deb.debian.org'
Err:3 http://deb.debian.org/debian bullseye-updates InRelease
  Temporary failure resolving 'deb.debian.org'
Reading package lists...
W: Failed to fetch http://deb.debian.org/debian/dists/bullseye/InRelease  Temporary failure resolving 'deb.debian.org'
W: Failed to fetch http://deb.debian.org/debian-security/dists/bullseye-security/InRelease  Temporary failure resolving 'deb.debian.org'
W: Failed to fetch http://deb.debian.org/debian/dists/bullseye-updates/InRelease  Temporary failure resolving 'deb.debian.org'
W: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package wget
ERROR: Unraid Docker Hook script throw an error!
       Starting container without Tailscale!

 

ok got it working by specifying dns for the container: --dns=8.8.8.8

Edited January 13, 20251 yr by nabbl

How can I have it so I don’t have to reset the web UI password every day please?

Pihole showing as unhealthy and I can't access the gui. Logs show no errors though. It's been working for over a year now

 

Was this template updated to support PiHole 6? The Docker environment variable names have all changed between 5.x and 6.x:

https://docs.pi-hole.net/docker/upgrading/v5-v6/

On 3/29/2025 at 9:50 AM, TalkiToaster said:

Was this template updated to support PiHole 6? The Docker environment variable names have all changed between 5.x and 6.x:

https://docs.pi-hole.net/docker/upgrading/v5-v6/

This template was removed for some reason. If you look at Spants' templates by way of pulling up his user in CA, Pi-Hole isn't listed anymore.

11 hours ago, UnInfamous said:

This template was removed for some reason. If you look at Spants' templates by way of pulling up his user in CA, Pi-Hole isn't listed anymore.

This was a very old (> 4years) template that I put together as one didnt exist. I have marked it as depreciated as there are many others now

@spants , and which one do you recommend to use these days?

Hoping you guys can help me with a problem I'm having. We had a power outage at our house a couple of days ago. Ever since then, my pihole isn't working correctly. If I restart it, it will work for a little awhile, and then we lose internet. Checking the logs this is what shows up.

text error warn system array login

tail: /var/log/pihole/FTL.log: file truncated

2025-11-19 19:15:20.476 UTC [57M] INFO: Reading certificate from /etc/pihole/tls.pem ...

2025-11-19 19:15:20.476 UTC [57M] INFO: Using SSL/TLS certificate file /etc/pihole/tls.pem

2025-11-19 19:15:20.476 UTC [57M] INFO: Web server ports:

2025-11-19 19:15:20.476 UTC [57M] INFO: - 0.0.0.0:80 (HTTP, IPv4, optional)

2025-11-19 19:15:20.476 UTC [57M] INFO: - 0.0.0.0:443 (HTTPS, IPv4, optional)

2025-11-19 19:15:20.476 UTC [57M] INFO: - [::]:80 (HTTP, IPv6, optional)

2025-11-19 19:15:20.476 UTC [57M] INFO: - [::]:443 (HTTPS, IPv6, optional)

2025-11-19 19:15:20.478 UTC [57M] INFO: Restored 0 API sessions from the database

2025-11-19 19:15:20.479 UTC [57M] INFO: Blocking status is enabled

2025-11-19 19:15:20.578 UTC [57/T154] INFO: Compiled 0 allow and 0 deny regex for 53 clients in 0.2 msec

2025-11-19 19:16:10.061 UTC [57/T186] INFO: Wrote config file:

2025-11-19 19:16:10.061 UTC [57/T186] INFO: - 153 total entries

2025-11-19 19:16:10.061 UTC [57/T186] INFO: - 145 entries are default

2025-11-19 19:16:10.061 UTC [57/T186] INFO: - 8 entries are modified

2025-11-19 19:16:10.061 UTC [57/T186] INFO: - 0 entries are forced through environment

2025-11-19 19:16:10.073 UTC [57/T186] INFO: Config file written to /etc/pihole/pihole.toml

2025-11-19 19:16:10.073 UTC [57/T186] INFO: Restarting FTL: dnsmasq config changed

2025-11-19 19:16:10.073 UTC [57M] INFO: Asked to terminate by "/usr/bin/pihole-FTL no-daemon" (PID 57, user pihole UID 1000)

2025-11-19 19:16:10.082 UTC [57/T154] INFO: Terminating database thread

2025-11-19 19:16:10.135 UTC [57/T157] INFO: Terminating timer thread

2025-11-19 19:16:10.481 UTC [57/T155] INFO: Terminating GC thread

2025-11-19 19:16:10.661 UTC [57/T156] INFO: Terminating resolver thread

2025-11-19 19:16:10.715 UTC [57M] INFO: Finished final database update

2025-11-19 19:16:10.715 UTC [57M] INFO: Waiting for threads to join

2025-11-19 19:16:10.715 UTC [57M] INFO: All threads joined

2025-11-19 19:16:10.716 UTC [57M] INFO: PID file emptied

2025-11-19 19:16:10.716 UTC [57M] INFO: Stored 1 API session in the database

2025-11-19 19:16:11.500 UTC [57M] INFO: ########## FTL terminated after 53s (internal restart)! ##########

2025-11-19 19:16:11.503 UTC [57M] INFO: ########## FTL started on e4bd632d253d! ##########

2025-11-19 19:16:11.503 UTC [57M] INFO: FTL branch: master

2025-11-19 19:16:11.503 UTC [57M] INFO: FTL version: v6.0.3

2025-11-19 19:16:11.503 UTC [57M] INFO: FTL commit: 37f9a96e

2025-11-19 19:16:11.503 UTC [57M] INFO: FTL date: 2025-02-28 09:26:27 +0000

2025-11-19 19:16:11.503 UTC [57M] INFO: FTL user: pihole

2025-11-19 19:16:11.503 UTC [57M] INFO: Compiled for linux/amd64 (compiled on CI) using cc (Alpine 14.2.0) 14.2.0

2025-11-19 19:16:11.508 UTC [57M] INFO: Wrote config file:

2025-11-19 19:16:11.508 UTC [57M] INFO: - 153 total entries

2025-11-19 19:16:11.508 UTC [57M] INFO: - 145 entries are default

2025-11-19 19:16:11.508 UTC [57M] INFO: - 8 entries are modified

2025-11-19 19:16:11.508 UTC [57M] INFO: - 0 entries are forced through environment

2025-11-19 19:16:11.511 UTC [57M] INFO: Parsed config file /etc/pihole/pihole.toml successfully

2025-11-19 19:16:11.512 UTC [57M] INFO: PID file does not exist or not readable

2025-11-19 19:16:11.512 UTC [57M] INFO: No other running FTL process found.

2025-11-19 19:16:11.512 UTC [57M] WARNING: Insufficient permissions to set process priority to -10 (CAP_SYS_NICE required), process priority remains at 0

2025-11-19 19:16:11.513 UTC [57M] INFO: PID of FTL process: 57

2025-11-19 19:16:11.513 UTC [57M] INFO: listening on 0.0.0.0 port 53

2025-11-19 19:16:11.513 UTC [57M] INFO: listening on :: port 53

2025-11-19 19:16:11.513 UTC [57M] INFO: PID of FTL process: 57

2025-11-19 19:16:11.529 UTC [57M] INFO: Database version is 21

2025-11-19 19:16:11.530 UTC [57M] INFO: Database successfully initialized

2025-11-19 19:16:12.709 UTC [57M] INFO: Imported 5925 queries from the on-disk database (it has 6222964 rows)

2025-11-19 19:16:12.709 UTC [57M] INFO: Parsing queries in database

2025-11-19 19:16:12.788 UTC [57M] INFO: Imported 5925 queries from the long-term database

2025-11-19 19:16:12.788 UTC [57M] INFO: -> Total DNS queries: 5925

2025-11-19 19:16:12.788 UTC [57M] INFO: -> Cached DNS queries: 2643

2025-11-19 19:16:12.788 UTC [57M] INFO: -> Forwarded DNS queries: 2776

2025-11-19 19:16:12.788 UTC [57M] INFO: -> Blocked DNS queries: 425

2025-11-19 19:16:12.788 UTC [57M] INFO: -> Unknown DNS queries: 1

2025-11-19 19:16:12.788 UTC [57M] INFO: -> Unique domains: 810

2025-11-19 19:16:12.788 UTC [57M] INFO: -> Unique clients: 53

2025-11-19 19:16:12.788 UTC [57M] INFO: -> DNS cache records: 70

2025-11-19 19:16:12.788 UTC [57M] INFO: -> Known forward destinations: 4

2025-11-19 19:16:12.871 UTC [57M] WARNING: Insufficient permissions to set system time (CAP_SYS_TIME required), NTP client not available

2025-11-19 19:16:12.871 UTC [57/T199] INFO: NTP server listening on 0.0.0.0:123 (IPv4)

2025-11-19 19:16:12.871 UTC [57/T200] INFO: NTP server listening on :::123 (IPv6)

2025-11-19 19:16:12.871 UTC [57M] INFO: FTL is running as user pihole (UID 1000)

2025-11-19 19:16:12.872 UTC [57M] INFO: Reading certificate from /etc/pihole/tls.pem ...

2025-11-19 19:16:12.872 UTC [57M] INFO: Using SSL/TLS certificate file /etc/pihole/tls.pem

2025-11-19 19:16:12.872 UTC [57M] INFO: Web server ports:

2025-11-19 19:16:12.872 UTC [57M] INFO: - 0.0.0.0:80 (HTTP, IPv4, optional)

2025-11-19 19:16:12.872 UTC [57M] INFO: - 0.0.0.0:443 (HTTPS, IPv4, optional)

2025-11-19 19:16:12.872 UTC [57M] INFO: - [::]:80 (HTTP, IPv6, optional)

2025-11-19 19:16:12.872 UTC [57M] INFO: - [::]:443 (HTTPS, IPv6, optional)

2025-11-19 19:16:12.873 UTC [57M] INFO: Restored 1 API session from the database

2025-11-19 19:16:12.874 UTC [57M] INFO: Blocking status is enabled

2025-11-19 19:16:12.975 UTC [57/T201] INFO: Compiled 0 allow and 0 deny regex for 53 clients in 0.2 msec

2025-11-20 00:00:03.017 UTC [57/T203] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server

2025-11-20 00:00:03.017 UTC [57/T203] INFO: Tried to resolve PTR "1.1.1.1.in-addr.arpa" on 127.0.0.1#53 (UDP)

2025-11-20 00:00:05.064 UTC [57/T203] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server

2025-11-20 00:00:05.064 UTC [57/T203] INFO: Tried to resolve PTR "1.0.0.1.in-addr.arpa" on 127.0.0.1#53 (UDP)

2025-11-20 00:05:24.386 UTC [57/T201] INFO: Optimized database in 1.354 seconds

2025-11-20 01:00:02.633 UTC [57/T203] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server

2025-11-20 01:00:02.633 UTC [57/T203] INFO: Tried to resolve PTR "1.1.1.1.in-addr.arpa" on 127.0.0.1#53 (UDP)

2025-11-20 01:00:04.680 UTC [57/T203] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server

2025-11-20 01:00:04.680 UTC [57/T203] INFO: Tried to resolve PTR "1.0.0.1.in-addr.arpa" on 127.0.0.1#53 (UDP)

2025-11-20 02:00:02.441 UTC [57/T203] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server

2025-11-20 02:00:02.441 UTC [57/T203] INFO: Tried to resolve PTR "1.1.1.1.in-addr.arpa" on 127.0.0.1#53 (UDP)

2025-11-20 02:00:04.488 UTC [57/T203] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server

2025-11-20 02:00:04.488 UTC [57/T203] INFO: Tried to resolve PTR "1.0.0.1.in-addr.arpa" on 127.0.0.1#53 (UDP)

No idea what's going on. Nothing changed. All that happened was our server was powered off for a couple of hours. Everything else is working perfectly.