March 4, 20251 yr Author 45 minutes ago, bmartino1 said: ? 2025.03.0-v6dev i'm on and running 2025.02.6-v6dev01 atm with out issues. the dev image : devzwf/pihole-dot-doh:2025.03.0-0.v6dev pihole update to : Pi-hole FTL v6.0.4, Web v6.0.2 and Core v6.0.5 few hours ago https://pi-hole.net/blog/2025/03/04/pi-hole-ftl-v6-0-4-web-v6-0-2-and-core-v6-0-5-released/#page-content and the docker image as well : Edited March 4, 20251 yr by ZappyZap
March 9, 20251 yr So I switched from “2024.07.0” to “2025.03.0-0.v6dev” and I have to say that everything is running great, I have no problems and everything looks fine in the logs. Best thanks for the work.
April 4, 20251 yr For some reason, v6 does not seem accept some of the settings from Unraid UI. My instance complains that parameters are empty, even though I have set them in user interface. Parameters also do appear to be set correctly when starting the container: Command execution docker run -d --name='Pihole-DoT-DoH' --net='br0' --ip='192.168.50.8' --pids-limit 2048 -e TZ="Europe/Kiev" -e HOST_OS="Unraid" -e HOST_HOSTNAME="cs381" -e HOST_CONTAINERNAME="Pihole-DoT-DoH" -e 'TCP_PORT_53'='53' -e 'UDP_PORT_53'='53' -e 'UDP_PORT_67'='67' -e 'TCP_PORT_80'='80' -e 'TCP_PORT_443'='443' -e 'FTLCONF_dns_upstreams'='127.1.1.1#5153;127.0.0.1#5335' -e 'TZ'='Europe/Helsinki' -e 'FTLCONF_webserver_api_password'='xxxxxxx' -e 'INTERFACE'='eth0' -e 'ServerIP'='192.168.50.8' -e 'ServerIPv6'='' -e 'IPv6'='False' -e 'FTLCONF_dns_listeningMode'='ALL' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:80]/admin' -l net.unraid.docker.icon='https://raw.githubusercontent.com/devzwf/unraid-docker-templates/main/images/pihole-logo-bw.png' -v '/mnt/user/appdata/pihole-dot-doh/pihole/':'/etc/pihole/':'rw,slave' -v '/mnt/user/appdata/pihole-dot-doh/dnsmasq.d/':'/etc/dnsmasq.d/':'rw,slave' -v '/mnt/user/appdata/pihole-dot-doh':'/config':'rw,slave' --cap-add=NET_ADMIN --restart=unless-stopped --hostname ns 'devzwf/pihole-dot-doh:latest-v6' 756158ef570af095cb3a34e7d07485135066fefbe495ec6b45815710c974efe2 The command finished successfully! But in log I get warnings and error: 2025-04-04 12:49:57.326 EEST [104M] INFO: ########## FTL started on ns! ########## 2025-04-04 12:49:57.326 EEST [104M] INFO: FTL branch: master 2025-04-04 12:49:57.326 EEST [104M] INFO: FTL version: v6.1 2025-04-04 12:49:57.326 EEST [104M] INFO: FTL commit: a3313229 2025-04-04 12:49:57.327 EEST [104M] INFO: FTL date: 2025-03-30 17:53:24 +0100 2025-04-04 12:49:57.327 EEST [104M] INFO: FTL user: pihole 2025-04-04 12:49:57.327 EEST [104M] INFO: Compiled for linux/amd64 (compiled on CI) using cc (Alpine 14.2.0) 14.2.0 2025-04-04 12:49:57.327 EEST [104M] WARNING: Environment variable FTLCONF_webserver_api_password has no value, substituting with empty string 2025-04-04 12:49:57.327 EEST [104M] WARNING: Environment variable FTLCONF_dns_listeningMode has no value, substituting with empty string 2025-04-04 12:49:57.337 EEST [104M] INFO: 3 FTLCONF environment variables found (2 used, 1 invalid, 0 ignored) 2025-04-04 12:49:57.337 EEST [104M] ERROR: [✗] FTLCONF_dns_listeningMode = "" is invalid, allowed options are: ["LOCAL","SINGLE","BIND","ALL","NONE"], using default instead 2025-04-04 12:49:57.337 EEST [104M] INFO: [✓] FTLCONF_webserver_api_password is used 2025-04-04 12:49:57.337 EEST [104M] INFO: [✓] FTLCONF_dns_upstreams is used Anybody got any idea what could be the issue?
April 24, 20251 yr So I just realized I haven't been getting an update for this container for a bit, I'm still on v5. To upgrade to v6, do I need to do anything more than change the repository to devzwf/pihole-dot-doh:2025.04.0-1.v6dev? I think I did a little custom config on which DoT server at quad9 to use and added a dnsmasq.d file for my internal domain servers (windows, I know, I know) resolution. Sorry for the dumb question, I go long stretches in between server re-configurations and seem to forget a lot with age...
April 24, 20251 yr Author Hello, ther eis a 'latest-v6' tag available with V6 but make sure you understand the difference between V5 and V6 before upgrading.... there is no going back unless you take a backup , what you should do any way
April 26, 20251 yr Today finally I changed from PiHole with TLS over Fritzbox to this docker build with everything included. The Fritzbox was not working well with dot on ipv4 only. There where connection faults and errors. (ipv4+ipv6 together works without problems, who knows why AVM?) Pihole v6 works perfect together with doh. excellent! The only critical thing is the template with the two folders pihole-dot-doh and Pihole-Dot-DoH. For backups on win systems this causes errors and data loss! This really needs to be changed. Thanks for this helpful support thread!
April 26, 20251 yr 4 hours ago, NoRaid99 said: Today finally I changed from PiHole with TLS over Fritzbox to this docker build with everything included. The Fritzbox was not working well with dot on ipv4 only. There where connection faults and errors. (ipv4+ipv6 together works without problems, who knows why AVM?) Pihole v6 works perfect together with doh. excellent! The only critical thing is the template with the two folders pihole-dot-doh and Pihole-Dot-DoH. For backups on win systems this causes errors and data loss! This really needs to be changed. Thanks for this helpful support thread! you can chage the fodler names and move them. the tempalte that paths them can be where every you wnat them. I would recomend making a pihole folder and insde that folder make 3 folders. dnsmask, pihole and config copy the muti path location to there corsponding folder.. then chmod 777 and chown nobody:users and edit teh template to point to that folder to keep current data. the tempalte is for easeir 1 click install but you can place the folder anywhere... for assistance with unriad docker and the use of ipv6 I recomend running this script which will allow ipv6 to cross and forward across the bridge... #!/bin/bash # Delay before starting sleep 10 # Apply sysctl settings apply_sysctl_settings() { echo "Applying sysctl settings..." sysctl -w net.ipv6.conf.all.forwarding=1 sysctl -w net.ipv6.conf.br0.accept_ra=2 sysctl -w net.ipv6.conf.br0.accept_ra_rt_info_max_plen=64 sysctl -w vm.overcommit_memory=1 echo "Verifying sysctl settings..." sysctl net.ipv6.conf.all.forwarding sysctl net.ipv6.conf.br0.accept_ra sysctl net.ipv6.conf.br0.accept_ra_rt_info_max_plen sysctl vm.overcommit_memory } apply_sysctl_settings -note br0 if your using bond or eth0 unriad network settings off then br0 needs chagned to your interface name.. unraid v7 has changed how the default network bridges work and using the docker inspect comands yo can see that ipv4 is true and ipv6 is false meaning the docker network bridge will not use nor asign a ipv6... withthe host systemctl using ipv4 tap to ipv6 we can still use ipv6 cross talk over the ip[v4 netowrk... the issue of making a tunnel and useing it scenario... Unriad/Limethc did this to gurantee ipv4 comunications to the dockers. some home assistan docker need this to use ipv6
April 28, 20251 yr On 4/23/2025 at 10:14 PM, ZappyZap said: Hello, ther eis a 'latest-v6' tag available with V6 but make sure you understand the difference between V5 and V6 before upgrading.... there is no going back unless you take a backup , what you should do any way Thanks @ZappyZap. I do understand it's a one-way migration (though I do have my appdata/config files separated into datasets so fairly easy to snapshot), but I'm not sure of the exact specifics between the two that I need to look out for or may need to manually adjust. Any easy-to-pass-on gotchas or prep I should be checking for?
April 28, 20251 yr 13 minutes ago, Alyred said: Thanks @ZappyZap. I do understand it's a one-way migration (though I do have my appdata/config files separated into datasets so fairly easy to snapshot), but I'm not sure of the exact specifics between the two that I need to look out for or may need to manually adjust. Any easy-to-pass-on gotchas or prep I should be checking for? https://docs.pi-hole.net/docker/upgrading/v5-v6/ all need updated to the new correct env... as shown in the compose file... environment: # Set the appropriate timezone for your location (https://en.wikipedia.org/wiki/List_of_tz_database_time_zones) TZ: "America/Chicago" # Set a password to access the web interface. Not setting one will result in a random password being assigned FTLCONF_webserver_api_password: "test" # DoT: unbound (127.0.0.1#5335), DoH: cloudflared (127.1.1.1#5153) FTLCONF_dns_upstreams: "127.1.1.1#5153;127.0.0.1#5335" FTLCONF_dns_listeningMode: "all" Edited April 28, 20251 yr by bmartino1 Data
April 28, 20251 yr Author 1 minute ago, bmartino1 said: Thought Zapyzap would have made a v6 template by now... I am preping this should be available tomorow.
April 30, 20251 yr Thanks. I'll wait for @ZappyZap's new template. I saw the env updates in the docker compose file and TBH, don't have time or energy lately to hunt down any additional env variables and change them manually. With that said, will I be able to overlay the new template on the old appdata folder, or should I back it up and re-create it fresh? I think I only need to transfer over some DNSMASQ settings for my internal Windows domain DNS and then copy over any Gravity settings....
May 2, 20251 yr A few issues i see: DoT DoH config path defaults to /mnt/cache, should be /mnt/user TZ shouldn't be there, unraid adds it on its own Web API Password isn't set as password type
May 2, 20251 yr Author 4 minutes ago, Kilrah said: A few issues i see: DoT DoH config path defaults to /mnt/cache, should be /mnt/user TZ shouldn't be there, unraid adds it on its own Web API Password isn't set as password type Thanks @Kilrah i will update it
May 2, 20251 yr Sorry to say something because I'm a beginner in these things and I could be totally wrong, but I tested the new template from ZappyZap yesterday and there is </mnt/user/appdata/Pihole-DoT-DoH-V6> not <mount/cache>. And pw works. edit: I have to apologise, that what I wrote is totally bollocks. Didn't realised that I fixed it while setting up the docker. 🤦♂️ Edited May 3, 20251 yr by NoRaid99
May 2, 20251 yr Author 1 hour ago, NoRaid99 said: Sorry to say something because I'm a beginner in these things and I could be totally wrong, but I tested the new template from ZappyZap yesterday and there is </mnt/user/appdata/Pihole-DoT-DoH-V6> not <mount/cache>. And pw works. Thanks i am out for now and will review all commant as soon as i get in front of my computer
May 2, 20251 yr 16 minutes ago, ZappyZap said: Thanks i am out for now and will review all commant as soon as i get in front of my computer No worries. We appreciate your time sir. Thank you for what you do!
May 8, 20251 yr @ZappyZap Thank you for this container. Its working great. 👍 I have 2 questions, though: - I recently deployed a fresh v6 and noticed, that there is no stubby config file in /config anymore (as it was in v5). How does one change stubby config? - I'd like to change the automatic gravity update interval. As changing it via crontab -e won't persist and, if I understood correctly, according to this blog just exposing /var/spool/cron/crontabs/root will create a lot of problems even with correct user/permissions, would you be willing to implement a solution for that?
May 8, 20251 yr Author 2 hours ago, paddesb said: @ZappyZap Thank you for this container. Its working great. 👍 I have 2 questions, though: - I recently deployed a fresh v6 and noticed, that there is no stubby config file in /config anymore (as it was in v5). How does one change stubby config? i do not use stubby anymore , of course i can re-add to let the option open for those who would like to use it 2 hours ago, paddesb said: - I'd like to change the automatic gravity update interval. As changing it via crontab -e won't persist and, if I understood correctly, according to this blog just exposing /var/spool/cron/crontabs/root will create a lot of problems even with correct user/permissions, would you be willing to implement a solution for that? I will look at it
.thumb.jpg.bec61e4e919a9235cc4475f8cb53d5e3.jpg)
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.