Charlie_Croker

I've been able to successfully change from beta to latest without any issues, and it's now running as intended. Thanks very much ZappyZap for taking the time to troubleshoot this.

Thanks for continuing to look into this. I thought I'd try and install directly from GitHub using docker compose on Unraid instead, and it installs the latest image perfectly, including the DNSCrypt TOML file. So it does appear to be an issue with the Unraid CA. I'll keep an eye on the forum for updates. Cheers.

Any luck on fixing the latest image to include DNSCrypt-Proxy and its TOML file? I'm still running the beta, which is running great.

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 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.

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.

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?

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.

Thanks very much - I'll have a look at my Unifi console to see how I can achieve the same.

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.

Unfortunately not. I gave up on it in the end. I’m instead using GlueTun VPN, but that regularly needs restarting as the VPN drops out, which is annoying. I’m going to go back to my original solution, which is to use a container with VPN built in, and route everything through that instead. Not my preferred option. It could be so much easier and cleaner if the built in Unraid solution would just work.

Bump.

Hi. I've been trying to get this to work for some time without success, and through trial and error and scouring the forums here and on reddit, I have identified what the issue is. Many of the posts either haven't got this far, or have been able to do so but haven't posted a solution. I want to be able to send individual container traffic through VPN using the UnraidOS built in VPN Manager. The 'VPN Tunnelled Access for Docker' option can achieve this. I can set up a Mullvad Wireguard connection, and through the console of an added container I can see that 1.1.1.1 can be pinged, and the IP address through ifconfig.io comes back as the exit node for the VPN. So I know the connection itself works. The problem comes when trying to access the WebGUI of any connected container. It basically doesn't resolve, and I can't access the WebUI. I run a Unifi network, and have VLAN's segregating traffic. I have a 'default' VLAN which is the backbone, and my Unraid Server sits on that. I have a VLAN for trusted devices, and my MacBook sits on that. Ordinarily, the Unraid server and my MacBook sitting on different VLAN's doesn't cause any issues at all. I can access container WebUI's without a problem. But in the case of the VPN Manager, it doesn't work. But if I switch my MacBook over to the same VLAN as my Unraid server, I can access the WebUI no problem. I haven't tested this, but I suspect if I were to remote access into my network via Unifi's Teleport, I wouldn't be able to access the container WebUI either, as Unifi puts remote devices onto their own VLAN. I have tried adjusting the IP Tables in Networking, but I just caused myself more problems. So I'm interested to hear from anyone who has solved this problem. Judging by all the posts I have read, there will be many other people interested in a solution too. Thanks for your time.

This was also driving me crazy, and I now know what the issue is thanks to this post. Is there any way solve this with IP routing tables or something? I really want to use the feature, but am accessing using a laptop on a different VLAN/subnet. Given that this isn't a problem outside of using the built in VPN Manager for Docker routing, there must be a way?