PiHole - port 53 appears to be conflicting

Apps and Virtualization
,
1

Hi All,

I’ve been running my TrueNAS Scale instance for a few weeks without issue. After a powercut yesterday, all the apps came back up, apart from Pihole.

After looking into the /var/log/app_lifecycle.log for more details as advised, I found this.

11.12MB/11.12MB
9fe644bd1a92 Pull complete 
pihole Pulled 
Network ix-pihole_default  Creating
Network ix-pihole_default  Created
Container ix-pihole-pihole-1  Creating
Container ix-pihole-pihole-1  Created
Container ix-pihole-pihole-1  Starting
Error response from daemon: driver failed programming external connectivity on endpoint ix-pihole-pihole-1 (18a41e823f3a49e29c0b8243e65bae93119ae7405cf26f5cbcc9e563c89b3961): failed to bind port 0.0.0.0:53/tcp: Error starting userland proxy: listen tcp4 0.0.0.0:53: bind: address already in use\n

I can see that some other service is using port 53.

How can I stop this or alter the config of Pihole??

2

Its propably incus using port 53 for internal dns resolution.

you can try with

sudo incus network set incusbr0 raw.dnsmasq="port=5354"

to rebind the incus port and free up port 53

1 Like
3

Amazing!! Thanks for the rapid and very useful response!
That worked a treat!