Hi all. Thanks in advance for any help.
I have updated my TrueNAS Scale to 24.04.2. My Pi-Hole was not working after install so I deleted the Pi-Hole app and installed the new Pi-Hole App which is Chart Version 2.0.13.
I am getting an error message that some seem to have experienced years ago and I cannot figure out what I am to do to solve this issue?
My error message in Pi-Hole is as indicated in attachment
Any suggestions on how to solve?
I think you need to create a bridge, then attach your NIC and apps to it.
I can’t find a good guide rn. I’ll check my desktop’s bookmarks for one tomorrow.
I couldn’t find the tutorial I used. But this is definitely how I’m configured, one bridge attaching apps, NIC and the web connected VMs. Did you get it working?
Well there must be a better solution, but in my truenas where I run 2 instances of Pihole–the official app and in a truenas VM–this works:
Edit the Pihole app
Under additional environment variables insert: Name “Interface”,
Value “your truenas network name”
Save the app and in the Pihole GUI go to settings and select the DNS tab
Select “Permit all Origins”
My truenas and home network are behind a firewall so this works for me but I wouldn’t do this otherwise.
Kind of late to the party on this one.
I had this some time ago. The fix at that time was to add a couple of environment variables. One for DNSMASQ_USER that I set to root, and one for INTERFACE set to the interface in question.
When I set up a jail (with Jailmaker/Dockge) and bridged my connection, I forgot about initially and PiHole stopped working until I changed it.
Today, when I tried to update PiHole to the latest version, it was failing to update. I started down the wrong route looking at the warning that the k3s.yaml file was group readable. When I decided to delete and reinstall it, I worked out that it was moaning that I was trying to set INTERFACE. In the latest version, there is a box for defining the interface, so the environment variables I added before weren’t need (and shouldn’t be added).
