Upgrading to v6 (pihole -up) didn't disable lighttpd

No. This is after the upgrade to v6 and found /admin/ wasn't working. Rebooted. No change. And after I'd manually "systemctl" stopped and disabled lighttpd. Rebooted. Then saw the new HTTP was working. Saw that my v5 config hadn't been carried forward. So I decided to shutdown and make a new sdcard.

$ find /mnt/usba2/lib/systemd/system -name lighttpd.service -o -name 'php*.service' -exec ls -l {} +
-rw-r--r-- 1 root root 155 Jul 13  2022 /mnt/usba2/lib/systemd/system/phpsessionclean.service

Here's all the symlinks below /mnt/usba2/etc/systemd resolved without their leading /

/mnt/usba2 $ cat /tmp/files.txt | xargs ls -ld
-rw-r--r-- 1 root root 1463 Feb 20 22:26 etc/systemd/system/pihole-FTL.service
-rw-r--r-- 1 root root 1162 Feb 14  2023 lib/systemd/system/apparmor.service
-rw-r--r-- 1 root root  156 May 25  2023 lib/systemd/system/apt-daily.timer
-rw-r--r-- 1 root root  184 May 25  2023 lib/systemd/system/apt-daily-upgrade.timer
-rw-r--r-- 1 root root 1044 Apr 19  2023 lib/systemd/system/avahi-daemon.service
-rw-r--r-- 1 root root 1044 Apr 19  2023 lib/systemd/system/avahi-daemon.service
-rw-r--r-- 1 root root  870 Apr 19  2023 lib/systemd/system/avahi-daemon.socket
-rw-r--r-- 1 root root  760 Jan  2  2024 lib/systemd/system/bluetooth.service
-rw-r--r-- 1 root root  760 Jan  2  2024 lib/systemd/system/bluetooth.service
-rw-r--r-- 1 root root  343 Dec 13  2022 lib/systemd/system/console-setup.service
-rw-r--r-- 1 root root  316 Jul 17  2022 lib/systemd/system/cron.service
-rw-r--r-- 1 root root  313 Aug  8  2018 lib/systemd/system/dphys-swapfile.service
-rw-r--r-- 1 root root  138 Mar 26  2023 lib/systemd/system/dpkg-db-backup.timer
-rw-r--r-- 1 root root  251 Mar  4  2023 lib/systemd/system/e2scrub_all.timer
-rw-r--r-- 1 root root  553 Mar  4  2023 lib/systemd/system/e2scrub_reap.service
-rw-r--r-- 1 root root  369 May  1  2020 lib/systemd/system/fake-hwclock.service
-rw-r--r-- 1 root root  270 Mar 23  2023 lib/systemd/system/fstrim.timer
-rw-r--r-- 1 root root 2003 Jan 26  2024 lib/systemd/system/getty@.service
-rw-r--r-- 1 root root  254 Apr 13  2022 lib/systemd/system/hciuart.service
-rw-r--r-- 1 root root  287 Oct 29  2018 lib/systemd/system/keyboard-setup.service
-rw-r--r-- 1 root root  191 Oct 14  2019 lib/systemd/system/logrotate.timer
-rw-r--r-- 1 root root  171 Mar 12  2023 lib/systemd/system/man-db.timer
-rw-r--r-- 1 root root  515 Jan  3  2023 lib/systemd/system/ModemManager.service
-rw-r--r-- 1 root root  515 Jan  3  2023 lib/systemd/system/ModemManager.service
-rw-r--r-- 1 root root  540 Jan 26  2024 lib/systemd/system/multi-user.target
-rw-r--r-- 1 root root  813 Jan 24  2023 lib/systemd/system/networking.service
-rw-r--r-- 1 root root  813 Jan 24  2023 lib/systemd/system/networking.service
-rw-r--r-- 1 root root  652 Jul 24  2023 lib/systemd/system/NetworkManager-dispatcher.service
-rw-r--r-- 1 root root 1336 Jul 24  2023 lib/systemd/system/NetworkManager.service
-rw-r--r-- 1 root root 1148 Jul 24  2023 lib/systemd/system/NetworkManager-wait-online.service
-rw-r--r-- 1 root root  433 Jan 11  2023 lib/systemd/system/nfs-client.target
-rw-r--r-- 1 root root  433 Jan 11  2023 lib/systemd/system/nfs-client.target
-rw-r--r-- 1 root root  144 Jul 13  2022 lib/systemd/system/phpsessionclean.timer
-rw-r--r-- 1 root root  530 Jan 26  2024 lib/systemd/system/remote-fs.target
-rw-r--r-- 1 root root  348 Apr 11  2016 lib/systemd/system/rpi-display-backlight.service
-rw-r--r-- 1 root root  348 Apr 11  2016 lib/systemd/system/rpi-display-backlight.service
-rw-r--r-- 1 root root  348 Apr 11  2016 lib/systemd/system/rpi-display-backlight.service
-rw-r--r-- 1 root root  209 Feb 16  2024 lib/systemd/system/rpi-eeprom-update.service
-rw-r--r-- 1 root root  538 Dec 19  2023 lib/systemd/system/ssh.service
-rw-r--r-- 1 root root  538 Dec 19  2023 lib/systemd/system/ssh.service
-rw-r--r-- 1 root root  249 Nov  6  2023 lib/systemd/system/sshswitch.service
-rw-r--r-- 1 root root  811 Jan 26  2024 lib/systemd/system/systemd-pstore.service
-rw-r--r-- 1 root root 1764 Jan 26  2024 lib/systemd/system/systemd-timesyncd.service
-rw-r--r-- 1 root root 1764 Jan 26  2024 lib/systemd/system/systemd-timesyncd.service
-rw-r--r-- 1 root root  271 Sep  6  2016 lib/systemd/system/triggerhappy.service
-rw-r--r-- 1 root root   73 Sep  6  2016 lib/systemd/system/triggerhappy.socket
-rw-r--r-- 1 root root  207 Dec  7  2022 lib/systemd/system/udisks2.service
-rw-r--r-- 1 root root  432 Feb 24  2023 lib/systemd/system/wpa_supplicant.service
-rw-r--r-- 1 root root  432 Feb 24  2023 lib/systemd/system/wpa_supplicant.service
-rw-r--r-- 1 root root  204 Aug 28  2017 usr/lib/systemd/user/dirmngr.socket
-rw-r--r-- 1 root root  298 Aug 28  2017 usr/lib/systemd/user/gpg-agent-browser.socket
-rw-r--r-- 1 root root  281 Aug 28  2017 usr/lib/systemd/user/gpg-agent-extra.socket
-rw-r--r-- 1 root root  234 Aug 28  2017 usr/lib/systemd/user/gpg-agent.socket
-rw-r--r-- 1 root root  308 Aug 28  2017 usr/lib/systemd/user/gpg-agent-ssh.socket

This has never been the case. The CLI has always been the only method.

Ok. Sorry. My bad. I updated my post that mentioned that.

Ah okay, makes sense. Then I guess it is now difficult to find out why disabling Lighttpd has not been offered during your update. But as said, it looks like one of the latest Pi-hole releases changed/fixed something there.

And I forgot that Pi-hole installed php-cgi and no php-fpm server, which explains why there is no PHP service active (other than the session cleaning).

That has been definitely solved with latest Pi-hole :slight_smile:.

I see my /admin/ page is telling me:

I am hesitant. :rofl:

Thank you for all your attention to this. We now return you to your regularly scheduled mayhem.

1 Like

When I ran into this original issue with lighttpd not being disabled (and not being asked about disabling it by the Pi-hole upgrade), I was running on a DietPi installation of Pi-hole v5 + Unbound:

The install instructions on the DietPi website say:

"DietPi-Software calls the Pi-hole installer with the --disable-install-webserver flag, which skips the Lighttpd and PHP installation parts. Instead, Lighttpd, Nginx or Apache is installed separately, based on user choice"

and the install process includes the 'Webserver Stack' which I imagine most people (like me) will choose to install lighttpd.

No idea if those details are helpful or not.

1 Like

DietPi implements Pi-hole v6 support here: Release v9.11 by MichaIng Β· Pull Request #7426 Β· MichaIng/DietPi Β· GitHub
The update will also offer to uninstall the Webserver and PHP, if no other dependents are installed. Would be great if you could give it a try:

G_DEV_BRANCH beta

We will release it today, but I am happy for every successful test beforehand.

I justed updates my second pihole from v5 to v6.04
Lighttpd was NOT disabled although I confirmed during the script request.
All remaining stuff was migrated (Unbound, all settings, etc).

I disabled Lighttpd and purged the service by
sudo apt-get remove lighttpd

The webserver ports were set manually in
/etc/pihole/pihole.toml

Now it runs like a charm and the webgui appears also in http:// mode.

How do you know that it was not disabled? And can you paste the logs from the relevant part of the update? If you confirm disabling Lighttpd during the update, it is moreless impossible that it does not happen. It immediately checks whether systemctl exists, in case uses it to stop and disable the service, otherwise even falls back to the legacy service command (supporting systems without systemd in turn). If any command fails, the update would abort right there.

I had to manually disable and stop the service and as I don't need it anymore I deinstalled it consequently.

Anyhow, the ports were not corrected in the toms file so the webgui didn't load. Same result as on 6.0 update.

But you said that you got the dialog to disable Lighttpd. If that is the case, and you did confirm to disable it, it would help a lot to find out why it did not happen.

Once the update went through, ports are not touched anymore. Pi-hole should then run on ports 8080/8443. The web UI should show up nicely there, e.g. using https://pi.hole:8443/admin/ in browser, or that with your local IP address.

Hey, I had the same problem. Lighthttp was running after upgrading to pihole 6, even though i pressed yes on disabling it on update, but after, I could not access /admin.

I tried what you wrote, and reboot:

sudo service lighttpd stop
sudo apt remove lighttpd

Now there is no webserver running on my pihole at all, whats going on here? Anybody know how to fix this?

Pihole is up

➜ ~ sudo pihole -up
[βœ“] Supported OS detected
[βœ“] Update local cache of available packages
[βœ“] Building dependency package pihole-meta.deb
[βœ“] Installing Pi-hole dependency package

[i] Checking for updates...
[i] Pi-hole Core: up to date
[i] Web Interface: up to date
[i] FTL: up to date

But visiting its address just says refused to connect

This site can’t be reached

pihole.local refused to connect.

Hmm i figured it out. Now it is on port 8080, not 80.

1 Like

You can change it back to port 80 by editing /etc/pihole/pihole.toml and looking for the [webserver] section

1 Like

Hey guys, I don't know too much about the technical end, but I recently updated my working pihole and my raspberry pi. Everything says it's working, but I can't access the web interface anymore, and my local IP hasn't changed at all.

I tried accessing it via different ports, based on posts I read here, but at best I just get an apache server on port 8080 that lists a bunch of files. Tried repairing the install, but that hasn't helped. Not sure what else to do/try, or what might be broken.

I ran the debug command, if that can help: https://tricorder.pi-hole.net/YElASSTd

According to your debug log, Pi-hole should be listening on port 8080 (see /etc/pihole/pihole.toml -> webserver.port)

Set that back to the default of set that back to default with pihole-FTL --config webserver.port "80o,443os,[::]:80o,[::]:443os", and that should stop it clashing with apache.

Depending on when you updated, you may have fallen foul of a migration issue that should now be resolved in future updates.

2 Likes

This fixed it perfectly, thank you so much for the help and for the software! :heart:

This worked for me, too. Thx