we will have PiHole v6 included soon. dietpi-software: Pi-hole: add support for v6 by MichaIng · Pull Request #7421 · MichaIng/DietPi · GitHub
There will be some changes compare to stock installation. One will be usage of web interface port 8089 instead 80 or 8080. Why? We want to prevent a port conflict with other applications such as SABnzbd or regular web server.
Does that mean that future Pihole updates have to be installed from within DietPi not direct from PiHole?
this has nothing to do with it.
We will do a migration from v5 to v6 on next DietPi release 9.11. However further PiHole updates can be carried out using PiHole tools as usual.
EDIT:
need to correct myself, we will not force a migration on DietPi 9.11. We just clean already migrated systems and allow new installs on v6 Pihole fresh install · Issue #7422 · MichaIng/DietPi · GitHub
Some idiots like me just hit “pihole -up” without reading the details. So used to updates being trouble free I even forgot to backup tonight. Doh!!
After update no DNS and no access to admin webpage. Also I got no warning about lighttpd.
For me, to FIX: Pi-hole update caused web to stop and no resolution - Help - Pi-hole Userspace
If you updated to Pi-Hole v6, there may have been a prompt asking you to disable lighttpd. I didn’t see it when I updated. Here’s the command to check if it is running:
sudo systemctl status lighttpd.service
If it is running (and you don’t need it for anything else), use these commands to disable it:
sudo systemctl stop lighttpd.service
sudo systemctl disable lighttpd.service
Then, reboot. Following these exact steps, I was able to get back into the web admin interface and set the DNS servers back to their original values. For some reason, updating to v6 wipes out your existing DNS settings.
For me I found my conditional DNS stuff was reset and had to do some tweaking - but that is a PiHole issue and check their forums.
I have a very simple DietPI setup mainly for PiHole. So killing lighttpd was not issue.
Also note - I did not have a webpage on :80 or :8080 until I ran the above commands and rebooted.
proably enough to adjust web interface port in /etc/pihole/pihole.toml. Maybe a challenge of the PiHole own migration script not setting the port correctly if a web server is still present? OK just guessing.
Is there a way to see if something else in the system uses the lighttpd? I think my Nextcloud server does, not sure.
So from my understanding the best way of action is wait for 9.11. Backup and uninstall v5 and do a fresh install of v6?
Yes NC is using a regular web server
Depends on what you planning to do. On DietPi v9.11 we are going to adjust settings for people already moved to PiHole v6. For others, who still use PiHole v5, nothing will change.
On new installations, PiHole v6 will be installed.
We are not going to force a PiHole update from v5 to v6 yet. From our point of view, still too many challenges with the PiHole update function. We will wait a few more weeks before the forced migration begins.
Our current recommendation is to stay on PiHole v5 until PiHole v6 is stable enough and the update process works smoothly. However, this is somewhat beyond our control.
I reimaged DietPi and it installed v6 as you mentioned. Is there a procedure to get the DietPi software installer to install v5 instead?
PiHole V6 is installed automatically because this is the default PiHole offers. However you should have see some error messages as our scripts on DietPi 9.10 did not expect the new PiHole world. Because files have been removed or renamed between v5 and V6. This will change on DietPi v9.11.
I don’t think v5 is available still.
Correct, I saw some errors about missing /etc/pihole/pihole-FTL.conf. I can do a manual installation of v5 but hoping to take advantage of whatever optimizations DietPi has made to the PiHole logging process.
As said, on DietPi v9.11 the installation should work without issues. It’s already in Beta and can be tested by switching to our DietPi beta branch.
Anyway, you should be ok to continue using new installation off v6. I don’t see an advantage on PiHole v5 for fresh installation.
Thanks. Will give it another go. I’m surprised and concerned about the number of issues being raised for the v6 release.
We feel the same way. We currently advise against upgrading, at least for existing installations
just ended with a pihole v6 on a old RapiOS → this ended in a running pihole without webinterface.
So I updated to dietpi + pihole.
there are errors during the install process, but pihole is up and running!
newbie question: how to update pihole on dietpi: managed by dietpi or use pihole -up or can a user choose whatever one likes more? recommendations?
Expected until DietPi v6.11, which currently is in beta, has been released.
There is nothing special on DietPi, still standard PiHole tooling to be used
Nope, you need to use PiHole tools as usual
Thx…! good to know
DietPi v9.11 has been released, supporting new installations on PiHole v6.
Any update for form of action for v5 users that also need the lighttpd server for Nextcloud?
Nothing changes for users of PiHole v5.
If you want to update to PiHole v6, you simply have to answer the question about the web server in such a way that you want to keep it. But this has nothing to do with DietPi directly, as the question comes up during the PiHole update.
If you plan to use PiHole v6, you should update your existing installation to the new PiHole version before updating to DietPi v9.11.
Thanks a lot!
I have a migration problem with dietpi 9.11 Version 2: The query log stays empty even if I activate the option * Should FTL load queries from the database on (re)start?*. With different browsers same result 