On 3/19/2026 at 3:40 PM, ZappyZap said:

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

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.

16 minutes ago, Charlie_Croker said:

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.

I can assure you the toml is included as you can chek on github : https://github.com/devzwf/pihole-dot-doh
and i am running latest and many as well without any issue, i am tried to understand where the discrepency come from.

i can still see the template on unraid did not updated correctly , i DM some administrator and waiting on their input.

i am still investigationg to see where is the issue on your instance

6 hours ago, ZappyZap said:

i can still see the template on unraid did not updated correctly , i DM some administrator and waiting on their input.

Looking around the only reason I can see is that you have your default container name set as "Pihole-DoT-DoH" so CA probably sets the main appdata folder as "/mnt/user/appdata/Pihole-DoT-DoH" to match the name.

May or may not be considered a bug in CA but I guess you should be able to circumvent it by just not messing with case in the container name.

Edited March 25Mar 25 by Kilrah

25 minutes ago, Kilrah said:

Looking around the only reason I can see is that you have your default container name set as "Pihole-DoT-DoH" so CA probably sets the main appdata folder as "/mnt/user/appdata/Pihole-DoT-DoH" to match the name.

May or may not be considered a bug in CA but I guess you should be able to circumvent it by just not messing with case in the container name.

@Kilrah

once again thanks for the suggestion, i will try update that and see if it fix the issue

19 hours ago, ZappyZap said:

I can assure you the toml is included as you can chek on github : https://github.com/devzwf/pihole-dot-doh
and i am running latest and many as well without any issue, i am tried to understand where the discrepency come from.

i can still see the template on unraid did not updated correctly , i DM some administrator and waiting on their input.

i am still investigationg to see where is the issue on your instance

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.

I update the template as suggest by Kilrah let see.
as i am travelling i will look at the result wednesday

Looks OK

Switching from Beta to Latest for me worked without any issues.

Really fantastic work ZappyZap, thank you for your contributions to the FOSS ecosystem.

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.