I’m new to running Pi-hole on TrueNAS SCALE and I’m running into an issue when trying to install the app.
Pi-hole requires port 53 for DNS, but during installation I receive an error saying that **port 53 is already in use by “Virt Service”.
From what I understand, this is related to the virtualization service used for VMs. However, I currently don’t have any VMs running on the system.
Because of this conflict, TrueNAS refuses to deploy the Pi-hole app as it cannot bind to port 53. I also tried changing the DNS port for Pi-hole, but that doesn’t seem to work properly.
Has anyone else run into this issue, and is there a recommended way to resolve it?
After having the same issue and trying to get it working for 3 hours straight, I managed to find a work around by installing dockage and having pihole run through there instead.
It seems for whatever reason even though port 53 isn’t used by anything else, truenas is marking port 53XX as being port 53.
Hopefully you’ve managed to solve the issue, or if you used another method I would be insterested to hear how you did it.
@LarsR do you see this being a problem with the 26 release, as its using libvirt?
For me, I seporate all my docker apps from truenas services onto there own IP addresses. That way you shouldn’t get any conflicts and using ports like 80 or 443 arn’t a problem. I am not sure if that will help with this specific conflict as it might be applied to 0.0.0.0, but its worth checking out.
For the new libvirt backend i honestly don’t know, i wasn’t able to set up my truenas 26 beta testbox and since there were reports about broken lxc after migrating to the beta i’m hesitant to update my main system to the beta.
This Friday is a holiday and i hope i have some time to play around with the 26 beta…
