Adam Warner

> have you tried that - because the "=" breaks it. Yeah, sorry - that's what I meant by: >, although I'm currently struggling to get a value to stick...

@troykelly - the latest tag should fix this issue. Please let us know! https://github.com/pi-hole/docker-pi-hole/releases/tag/2025.02.2

Do you see the same behaviour if you set the blocking mode to `NXDOMAIN` rather than `NULL`?

Thanks for the update. @DL6ER any thoughts here?

Pi-hole's webserver is embedded (per https://pi-hole.net/blog/2025/02/18/introducing-pi-hole-v6/) If paths are conflicting, perhaps run it on a different port. (see /etc/pihole/pihole.toml -> webserver.ports) However, as you've posted this in the docker repo...

What does your docker compose look like?

> - "10.0.13.4:8090:80/tcp" Right, OK - so presumably host networking here and you're mapping 8090 _outside_ the container to 80 _inside_ it. Can you try setting the web interface port...

@tsutsu3 could you rebase this on development please? The tests/checks have deployed since this was reviewed and we are currently unable to merge until it is rebased. Thanks!

Taking an exact copy of your docker compose file above, I am unable to repro this, at least on Docker Desktop on Windows. What version of Ubuntu is your host?...

> No, I verified, there is no FTL running in container at the time the pihole updatechecker command running and failing to resolve. This is very unusual. FTL is starting,...