The other day I noticed the “update available” messages at the bottom of the pi-hole dashboard and had the bright idea to uninstall/re-install pi-hole on my umbrel to see if it would grab the latest versions of everything. After doing this, my pi-hole is no longer blocking traffic. I have my router configured to use the Umbrel for DNS, so nothing’s changed there. I even see all of my queries going through…it’s simply refusing to block anything. Any suggestions about how I might fix this?
These are the exact steps I took…but I barely know what I’m doing myself, so YMMV. I’ll also add that my Umbrel was hard-booted due to a power outage and the issue started again! This time I was able to fix it by entering the IP address of my Umbrel in /etc/resolv.conf rather than localhost 127.0.0.1. Anyway, here goes:
Enter the IP address of your Umbrel in the hostname field of PuTTY, leave everything else as default and hit “open”
login as userid “umbrel” and use the password you set
type sudo nano /etc/resolv.conf and enter your umbrel password again
my entries are: nameserver 192.168.1.137 nameserver 192.168.1.1
The first entry is the static IP address of the Umbrel on my local network. The second entry is my router’s IP. After you make updates, hit ctrl-o to write and ctrl-x to exit.
type sudo nano /etc/resolvconf.conf
Near the top you will see blue text preceeded by “#” above the name_servers line.
delete the “#” that proceeds the name_servers line so that it looks like: name_servers=192.168.1.137
Again, remember to modify the above address so that it matches your Umbrel which is almost certainly not 137. After you make updates, hit ctrl-o to write and ctrl-x to exit.
Well, I clearly don’t know what I’m doing although I do feel as though I’m on the right track… Anyway, I recently upgraded to Umbrel 0.5.0 and in order to do so, had to re-install Pi-Hole and the rest of my apps. Pi Hole stopped blocking again after that update. I followed my own steps above and it didn’t work.
I kept experimenting though and after changing the steps as below (but still following the rest of my guidance in the previous post,) it started working again:
Replace the updates made in steps 4 and 5 with only this: nameserver 127.0.0.1
…and step 7 with only this: name_servers=127.0.0.1