4 minutes ago, ZappyZap said:

pushed.
hopefully this will end up the saga with cloudflared.
let me know
still need to update Overviewa nd others.....

I just updated and 127.1.1.1#5153 looks like it's working on "latest" with no errors. I'll keep an eye on it though. https://1.1.1.1/help is also showing I'm using DoH.

No issues after 24 hours of heavy network traffic using the most recent update on the "latest" tag. 127.1.1.1#5153, 127.2.2.2#5253, and cache are all working as expected. Thank you for all of your work on this.

Edited February 9Feb 9 by Zilonis
Corrected "5135" and "5235" to "5153" and "5253".

10 minutes ago, Zilonis said:

No issues after 24 hours of heavy network traffic using the most recent update on the "latest" tag. 127.1.1.1#5135, 127.2.2.2#5235, and cache are all working as expected. Thank you for all of your work on this.

you mean 127.1.1.1#5153. and 127.2.2.2#5253. right ?

Yes, sorry.

Latest still broken for me.

2026-02-10 00:12:42.698 CET [106M] INFO: Parsed config file /etc/pihole/pihole.toml successfully
2026-02-10 00:12:42.698 CET [106M] INFO: PID file does not exist or not readable
2026-02-10 00:12:42.698 CET [106M] INFO: No other running FTL process found.
2026-02-10 00:12:42.698 CET [106M] WARNING: Insufficient permissions to set process priority to -10 (CAP_SYS_NICE required), process priority remains at 0
2026-02-10 00:12:42.700 CET [106M] INFO: PID of FTL process: 106
2026-02-10 00:12:42.702 CET [106M] INFO: listening on 0.0.0.0 port 53
2026-02-10 00:12:42.702 CET [106M] INFO: listening on :: port 53
2026-02-10 00:12:42.703 CET [106M] INFO: PID of FTL process: 106
2026-02-10 00:12:42.705 CET [106M] ERROR: SQLite3: recovered 325 frames from WAL file /etc/pihole/pihole-FTL.db-wal (283)
2026-02-10 00:12:42.705 CET [106M] INFO: Database version is 21
2026-02-10 00:12:42.720 CET [106M] INFO: Database successfully initialized
2026-02-10 00:12:43.472 CET [106M] INFO: Imported 54688 queries from the on-disk database (it has 1463656 rows)
2026-02-10 00:12:43.472 CET [106M] INFO: Parsing queries in database
2026-02-10 00:12:43.494 CET [106M] INFO:   10000 queries parsed...
2026-02-10 00:12:43.517 CET [106M] INFO:   20000 queries parsed...
2026-02-10 00:12:43.541 CET [106M] INFO:   30000 queries parsed...
2026-02-10 00:12:43.560 CET [106M] INFO:   40000 queries parsed...
2026-02-10 00:12:43.579 CET [106M] INFO:   50000 queries parsed...
2026-02-10 00:12:43.590 CET [106M] INFO: Imported 54688 queries from the long-term database
2026-02-10 00:12:43.590 CET [106M] INFO:  -> Total DNS queries: 54688
2026-02-10 00:12:43.590 CET [106M] INFO:  -> Cached DNS queries: 38195
2026-02-10 00:12:43.591 CET [106M] INFO:  -> Forwarded DNS queries: 4786
2026-02-10 00:12:43.591 CET [106M] INFO:  -> Blocked DNS queries: 10992
2026-02-10 00:12:43.591 CET [106M] INFO:  -> Unknown DNS queries: 0
2026-02-10 00:12:43.591 CET [106M] INFO:  -> Unique domains: 1621
2026-02-10 00:12:43.591 CET [106M] INFO:  -> Unique clients: 19
2026-02-10 00:12:43.591 CET [106M] INFO:  -> DNS cache records: 303
2026-02-10 00:12:43.591 CET [106M] INFO:  -> Known forward destinations: 1
2026-02-10 00:12:43.699 CET [106M] WARNING: Insufficient permissions to set system time (CAP_SYS_TIME required), NTP client not available
2026-02-10 00:12:43.699 CET [106/T179] INFO: NTP server listening on 0.0.0.0:123 (IPv4)
2026-02-10 00:12:43.699 CET [106/T180] INFO: NTP server listening on :::123 (IPv6)
2026-02-10 00:12:43.699 CET [106M] INFO: FTL is running as user pihole (UID 1000)
2026-02-10 00:12:43.699 CET [106M] INFO: Reading certificate from /etc/pihole/tls.pem ...
2026-02-10 00:12:43.699 CET [106M] INFO: Using SSL/TLS certificate file /etc/pihole/tls.pem
2026-02-10 00:12:43.700 CET [106M] INFO: Web server ports:
2026-02-10 00:12:43.700 CET [106M] INFO:   - 0.0.0.0:80 (HTTP, IPv4, optional, OK)
2026-02-10 00:12:43.700 CET [106M] INFO:   - 0.0.0.0:443 (HTTPS, IPv4, optional, OK)
2026-02-10 00:12:43.700 CET [106M] INFO:   - [::]:80 (HTTP, IPv6, optional, OK)
2026-02-10 00:12:43.700 CET [106M] INFO:   - [::]:443 (HTTPS, IPv6, optional, OK)
2026-02-10 00:12:43.700 CET [106M] INFO: Restored 0 API sessions from the database
2026-02-10 00:12:43.704 CET [106M] INFO: Blocking status is enabled
2026-02-10 00:12:43.832 CET [106/T181] INFO: Compiled 0 allow and 2 deny regex for 19 clients in 32.2 msec
2026-02-10 00:12:44.954 CET [232/F106] WARNING: Connection error (127.1.1.1#5153): TCP connection failed (Connection refused)
2026-02-10 00:12:44.954 CET [233/F106] WARNING: Connection error (127.1.1.1#5153): TCP connection failed (Connection refused)
2026-02-10 00:12:44.957 CET [234/F106] WARNING: Connection error (127.1.1.1#5153): TCP connection failed (Connection refused)
2026-02-10 00:12:44.959 CET [235/F106] WARNING: Connection error (127.1.1.1#5153): TCP connection failed (Connection refused)
2026-02-10 00:12:45.615 CET [236/F106] WARNING: Connection error (127.1.1.1#5153): TCP connection failed (Connection refused)
2026-02-10 00:12:45.618 CET [237/F106] WARNING: Connection error (127.1.1.1#5153): TCP connection failed (Connection refused)
2026-02-10 00:12:45.618 CET [238/F106] WARNING: Connection error (127.1.1.1#5153): TCP connection failed (Connection refused)
2026-02-10 00:12:45.619 CET [239/F106] WARNING: Connection error (127.1.1.1#5153): TCP connection failed (Connection refused)
2026-02-10 00:12:45.619 CET [240/F106] WARNING: Connection error (127.1.1.1#5153): TCP connection failed (Connection refused)
2026-02-10 00:12:45.619 CET [241/F106] WARNING: Connection error (127.1.1.1#5153): TCP connection failed (Connection refused)
2026-02-10 00:12:45.623 CET [242/F106] WARNING: Connection error (127.1.1.1#5153): TCP connection failed (Connection refused)
2026-02-10 00:12:45.626 CET [243/F106] WARNING: Connection error (127.1.1.1#5153): TCP connection failed (Connection refused)

@kilrah i cant reproduce
can you please provide the output of :
cat /build_date.info
ps auxww |grep -i dnscrypt

Thanks

Sorry it was me, I forgot to delete the broken "latest" image before switching back to it so it reused the local one instead of pulling the new

4 hours ago, Kilrah said:

Sorry it was me, I forgot to delete the broken "latest" image before switching back to it so it reused the local one instead of pulling the new

No worries
Thanks

Hello,

the description in unraid says, “You must set FTLCONF_dns_upstreams variables to 127.1.1.1#5153 (DoH) and/or 127.2.2.2#5335 (DoT).”

Shouldn't it be "#5235 (DoT)" instead?

14 hours ago, FailX said:

Hello,

the description in unraid says, “You must set FTLCONF_dns_upstreams variables to 127.1.1.1#5153 (DoH) and/or 127.2.2.2#5335 (DoT).”

Shouldn't it be "#5235 (DoT)" instead?

sorry but where do you see this ?

In the docker help section

You seem to have an old version of the template .

Hi. First of all, thanks for these docker pihole containers. Up until the Cloudflare change, they were working brilliantly. I'm now trying to fix them, but without success. I've updated my containers, but they still contain the Cloudlfare yaml. So instead, I've installed a fresh container using the beta tag, which has worked. The next problem I've run into, is getting Mullvad DNS to work, which I was using before for both DoH and DoT. Stubby isn't working with the same settings as before which worked, so I need to take a look at that. The dnscrypt-proxy.toml file is problematic, as it needs a stamp. I've used AI to try and help me build a config file for Mullvad, but without success. I'm getting errors regarding invalid stamps. AI has been unsuccessful, and I don't know where to find or generate the correct stamp. Any help or pointers would be very much appreciated.

2 minutes ago, Charlie_Croker said:

Hi. First of all, thanks for these docker pihole containers. Up until the Cloudflare change, they were working brilliantly. I'm now trying to fix them, but without success. I've updated my containers, but they still contain the Cloudlfare yaml. So instead, I've installed a fresh container using the beta tag, which has worked. The next problem I've run into, is getting Mullvad DNS to work, which I was using before for both DoH and DoT. Stubby isn't working with the same settings as before which worked, so I need to take a look at that. The dnscrypt-proxy.toml file is problematic, as it needs a stamp. I've used AI to try and help me build a config file for Mullvad, but without success. I'm getting errors regarding invalid stamps. AI has been unsuccessful, and I don't know where to find or generate the correct stamp. Any help or pointers would be very much appreciated.

I am not using Mullvad so i could not test this one.
the beta tag work but not latest ? is that's what i am understanding ?

2 hours ago, ZappyZap said:

I am not using Mullvad so i could not test this one.
the beta tag work but not latest ? is that's what i am understanding ?

Yes, that's right. I updated my pre-existing containers to the latest version, but they still run the Cloudflare config. I tried installing a new container, but get the same. But if I change the latest tag to beta, I get the new version with the dnscrypt-proxy.

Regarding the dnscrypt config, where did you get the stamp for Cloudflare? I need to work out where to get, or how to generate a stamp for the Mullvad DNS IP/URL.

2 minutes ago, Charlie_Croker said:

Yes, that's right. I updated my pre-existing containers to the latest version, but they still run the Cloudflare config. I tried installing a new container, but get the same. But if I change the latest tag to beta, I get the new version with the dnscrypt-proxy.

Let me check that
i am really surprise
can you provide the output of : cat /build_date.info

2 minutes ago, Charlie_Croker said:

Regarding the dnscrypt config, where did you get the stamp for Cloudflare? I need to work out where to get, or how to generate a stamp for the Mullvad DNS IP/URL.

from dns-crypt repo themself.

Edited March 16Mar 16 by ZappyZap

15 hours ago, ZappyZap said:

Let me check that
i am really surprise
can you provide the output of : cat /build_date.info

from dns-crypt repo themself.

Here is the output:

pihole1:/# cat /build_date.info

09.03.2026 13:33:07 DNSCrypt-proxy 2.1.15 installed for x86_64

09.03.2026 13:33:09 Stubby 0.4.3 installed for x86_64

09.03.2026 13:33:10 Unbound Version 1.24.2 installed for x86_64

09.03.2026 13:33:11 Core version is v6.4 (Latest: v6.4) installed

09.03.2026 13:33:11 Web version is v6.4.1 (Latest: v6.4.1) installed

09.03.2026 13:33:11 FTL version is v6.5 (Latest: v6.5) installed

09.03.2026 13:33:11 Built from pihole/pihole with tag latest

So from looking at this, it looks like DNSCrypt-proxy is installed. But what I didn't get was a dnscrypt-proxy TOML file. I was still left with just the Cloudflared YML after the update which is what confused me.

There are two containers on the Unraid App Store; Pihole-DoT-DoH and Pihole-DoT-DoH-V6. They are both V6 and appear to be the same. Are there any differences? I've done fresh installs of both with the latest tag, and both images have the Cloudflared YML, and no DNSCrypt-Proxy TOML file. I tried inserting my own DNSCrypt-Proxy TOML file, but it doesn't work as Cloudflared interferes. But installing the beta does give the correct DNSCrypt-Proxy TOML file instead of the Cloudflared YML. I cannot get the latest versions working with DNSCrypt, but I have the beta working really nicely with Mullvad DNS on both DoH (DNSCrypt) and DoT (Stubby).

So I guess the latest image needs to work in the same was as the beta, by having no Cloudflared installed and having a DNSCrypt-Proxy TOML file for editing?

Edited March 17Mar 17 by Charlie_Croker
Additional info

In addition to the post above, I also have some general suggestions:

--dns 9.9.9.9 could be added to the extra parameters so that the Pihole gravity database can be built on first startup even if there are DoH/DoT configuration issues.

The configuration files currently save to appdata in two different folders due to uppercase and lowercase letters being used in one of the container paths -

Pihole config container path: /mnt/user/appdata/pihole-dot-doh/pihole/

dnsmasq config container path: /mnt/user/appdata/pihole-dot-doh/dnsmasq.d/

DoT DoH config container path: /mnt/user/appdata/Pihole-DoT-DoH

Can I suggest the following changes to get all the configuration files in one appdata folder -

Pihole config container path: /mnt/user/appdata/pihole-dot-doh/pihole/

dnsmasq config container path: /mnt/user/appdata/pihole-dot-doh/dnsmasq.d/

DoT DoH config container path: /mnt/user/appdata/pihole-dot-doh/dotdoh/

Thanks again for a great Unraid app container.

I will check this, and test fresh install, i am pretty sure when i test those the toml was there

2 minutes ago, ZappyZap said:

I will check this, and test fresh install, i am pretty sure when i test those the toml was there

Thanks very much. I've tried both of your latest v6 containers on the Unraid App Store a few times, and I can't get them to work like the beta. If I make a fresh install of latest-v6, I get the Cloudflared file. But if I then change that to beta, the DNSCrypt file appears. Appreciate you looking at this.

Edited March 18Mar 18 by Charlie_Croker
Additional info

For anyone looking to populate their DNSCrypt TOML file, you can use the calculator here to create your own stamp: https://dnscrypt.info/stamps/

Or, you can find preconfigured stamps for many popular resolvers here: https://github.com/DNSCrypt/dnscrypt-resolvers/blob/master/v3/public-resolvers.md

13 hours ago, Charlie_Croker said:

For anyone looking to populate their DNSCrypt TOML file, you can use the calculator here to create your own stamp: https://dnscrypt.info/stamps/

Or, you can find preconfigured stamps for many popular resolvers here: https://github.com/DNSCrypt/dnscrypt-resolvers/blob/master/v3/public-resolvers.md

Thanks for those links
i should probably add them somewhere

On 3/17/2026 at 8:42 AM, Charlie_Croker said:

In addition to the post above, I also have some general suggestions:

--dns 9.9.9.9 could be added to the extra parameters so that the Pihole gravity database can be built on first startup even if there are DoH/DoT configuration issues.

The configuration files currently save to appdata in two different folders due to uppercase and lowercase letters being used in one of the container paths -

Pihole config container path: /mnt/user/appdata/pihole-dot-doh/pihole/

dnsmasq config container path: /mnt/user/appdata/pihole-dot-doh/dnsmasq.d/

DoT DoH config container path: /mnt/user/appdata/Pihole-DoT-DoH

Can I suggest the following changes to get all the configuration files in one appdata folder -

Pihole config container path: /mnt/user/appdata/pihole-dot-doh/pihole/

dnsmasq config container path: /mnt/user/appdata/pihole-dot-doh/dnsmasq.d/

DoT DoH config container path: /mnt/user/appdata/pihole-dot-doh/dotdoh/

Thanks again for a great Unraid app container.

I have review all that , and there is something wrong ,
i cannot found those dir in the template : https://github.com/devzwf/unraid-docker-templates/blob/main/pihole-dot-doh.xml

I message squid to see what's wrong

1 hour ago, ZappyZap said:

I message squid to see what's wrong

AFAIK CA takes any xml in the repo whatever the folder, you kept your old ones in a "deprecated" folder so they might still be found first and supersede the intended one, they should be outright deleted if not valid anymore. You can add a tag to deprecate a template but I'm not sure how that works if it refers to the same repo as an active one.

Edited March 19Mar 19 by Kilrah

1 hour ago, Kilrah said:

AFAIK CA takes any xml in the repo whatever the folder, you kept your old ones in a "deprecated" folder so they might still be found first and supersede the intended one, they should be outright deleted if not valid anymore. You can add a tag to deprecate a template but I'm not sure how that works if it refers to the same repo as an active one.

Thanks @Kilrah
i will do that and delete all the xml in deprecated forlder