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.