Looks like incus successfully bound to port 5354 and freed up port 53.
At least in theory nothing should prevent pihole or another dns server to use it.
But i’m honestly out of ideas.
If you’re worried about truenas running “outside the recommended configuration lines” then just use the same command but replace 5354 with 53 and you’re back to running the defaults…
I figured. I was just being snarkier than necessary. It’s back now. ![]()
That sounds suspiciously like a subset of what nginx-proxy-manager does.
That’s my understanding also.
But I prefer to bind IP addresses to specific apps from within the TrueNAS appliance vs. using yet another app to help an app.
tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 1120988/docker-prox
tcp6 0 0 :::53 :::* LISTEN 1120994/docker-prox
udp 0 0 0.0.0.0:53 0.0.0.0:* 1121002/docker-prox
udp 0 0 0.0.0.0:5353 0.0.0.0:* 3558/avahi-daemon:
This is the result of the port 53 query for my PiHole official app which has been running flawlessly for several years so I wonder how your install is using a different ip address seemingly without docker?
Also have you successfully installed any other apps?
But I prefer to bind IP addresses to specific apps from within the TrueNAS appliance vs. using yet another app to help an app.
Oh, believe me, I get that. I was just calibrating. I didn’t even know that was there. I will definitely look into it. I have no emotional investment in nginx-proxy-manager.