copied and pasted all the commands as listed and ran them. Pi-hole still shows as installed and won’t let me install as it thinks it’s installed already.
Pi-hole is still running, but I no longer have the web consol. Should I reboot or should I attempt an uninstall from dietpi-software first or…
[edit] I see I was typing while you answered… I did essentially what you described. {Oops… I let it delete whatever it wanted to, but it didn’t seem to harm anything]
Hi,
I have this sneaking suspicion that I was supposed to run the remove script first and then do the manual commands to clear anything else out.
I ran the remove script from dietpi-software and then I could re-install pi-hole. This time I got the lastest web consol and all appears to be well.
My only remaining problem is that I used to edit /etc/dsnmask.conf to switch from google’s DNS servers to OpenDNS. That file has changed big time and I cannot find where to edit the DNS address anymore… perhaps SystemD looks at another file somewhere else for that information?
The DNS server change is not a big deal, it works fine as is.
Ah… I see that my whitelist is completely empty… fortunately, I have a screen shot of it, so I re-created it and added all the addresses via the web consol. I’m pretty sure the blacklist was empty as I never added anything there myself.
I’ll have a look later, however another issue has cropped up.
I am not getting any statistics showing in the web consol. Perhaps this is related to my allowing the un-install to delete things, but I would have thought that Pi-Hole has started to write new logs?
I did not notice this yesterday, as I am used to having zero stats when it first starts up… but today, things are still at zero, including the number of domains being blocked which shows as zero, yet in use, ADs are being blocked, so Pi-Hole must be working.
The PiHole log files have an exclusion to the above Ramlog (/var/log/pihole), they are only cleared daily. So its most likely incorrect permissions on the file.
Check permissions with (should be www-data:www-data):
root@DietPi:/var/log# ls -l pihole.log
-rwxrwxr-x 1 www-data www-data 0 Nov 10 14:27 pihole.log
Just to quickly get this done I did:
root@DietPi:/var/log# chmod 777 pihole.log
And after chmod it reads:
root@DietPi:/var/log# ls -l pihole.log
-rwxrwxrwx 1 www-data www-data 0 Nov 10 14:27 pihole.log
chmod appears to have had no effect on the problem. I wonder if I should just do a fresh install and get things back to normal? That would seem to be the “easy” way…
edit: I forgot to mention, it’s not just the log… it’s every data listing in the web consol:
0 Ads blocked today; 0 DNS inquiries; 0.0% of today’s traffic is ads; 0 Domains being blocked
root@DietPi:~# systemctl status dsnmasq -l
● dsnmasq.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
root@DietPi:~#
Update to Dietpi V137 has come along and I reluctantly installed it but I uninstalled Pi-Hole first (which probably had no bearing on this). I updated to 137 and then selected Pi-Hole for installation. On the last update, things appeared to break, leaving me with a limping system, which, by the way, I did not fix, but simply left it limping until today.
During the installation of Pi-Hole, a screen pops up that asks you to select the network interface… the last time I was updating I figured there was no point, as nothing had changed, and my ip address was set in the router etc, but in fact, hitting OK instead of cancel took me to new screens which had additional selections of DNS choice etc. and after following the bouncing ball, I was left with a perfectly working Pi-hole! The Web consol works correctly, all my stats show up as they should, and my chosen DNS is actually being used.
So I’m afraid, all that trouble earlier on can be blamed squarely on me and not Dietpi.
