AlBundy33

Any news about this issue?

docker-compose.yml ``` version: "3" # More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/ services: pihole: container_name: pihole image: pihole/pihole:latest restart: always ports: - "192.168.1.111:53:53/tcp" - "192.168.1.111:53:53/udp" - "192.168.1.111:3080:3080/tcp" environment: TZ: 'Europe/Berlin' WEBPASSWORD:...

https://tricorder.pi-hole.net/ARWRNTBb/

adding a `+x` to basic-install.sh seems that a command `pihole updatechecker remote` seems to be the problem during startup. -> Note I've advertised pi-hole as default-dns in my network and...

remote update was introduced in 0d5a001916335cf4b27408217063ac9e04cc7e0d and this cannot work if pi-hole is the dns of the network pi-hole starts much faster after removing the remote-line

I've already set ``` PIHOLE_DNS_: '192.168.1.1;fd00::cece:1eff:fea8:6d0' WEB_PORT: 3080 DNS_BOGUS_PRIV: 'true' DNS_FQDN_REQUIRED: 'true' REV_SERVER: 'true' REV_SERVER_DOMAIN: 'fritz.box' REV_SERVER_TARGET: '192.168.1.1' REV_SERVER_CIDR: '192.168.1.0/24' ``` With this setup all is working as expected: -...

Since the update is also executed in a running container it would be nice if the remote update could be moved after the startup :-)

+1 for this feature request. inserts into sqlite-db works but it's not a convenient solution for endusers. Therefore an import/export with csv or excel or would be nice

It's already available in latest releases (4.3.0) -> at least on windows

nothing special - just a small sound for user C that he knows that the call was transfered and he talks now to user A