I have an install of Pi Hole running on a Raspbery Pi 3B+ which I've been using for a number of years. The OS is Ubuntu Server 24.04, and I think it is a fairly "vanilla" install (no Docker, VMs or anything). I decided to upgrade to the latest version today (from the most recent PiHole 5.x version) having put it off for a while. The upgrade completed without any error messages. However, I can no longer access the web control panel at all.
Expected Behaviour:
Ability to log into Pi Hole web interface via it's IP address i.e. http://192.168.1.2/admin or via http://pi.hole/
This is what it was doing prior to the upgrade.
Actual Behaviour:
"Placeholder Page" which contains the following text.
You should replace this page with your own web pages as soon as possible.
Unless you changed its configuration, your new server is configured as follows:
- Configuration files can be found in /etc/lighttpd. Please read /etc/lighttpd/conf-available/README file.
- The DocumentRoot, which is the directory under which all your HTML files should exist, is set to /var/www/html.
- CGI scripts are looked for in /usr/lib/cgi-bin, which is where Ubuntu packages will place their scripts. You can enable cgi module by using command "lighty-enable-mod cgi".
- Log files are placed in /var/log/lighttpd, and will be rotated weekly. The frequency of rotation can be easily changed by editing /etc/logrotate.d/lighttpd.
- The default directory index is index.html, meaning that requests for a directory /foo/bar/ will give the contents of the file /var/www/html/foo/bar/index.html if it exists (assuming that /var/www/html is your DocumentRoot).
- You can enable user directories by using command "lighty-enable-mod userdir"
About this page
This is a placeholder page installed by the Ubuntu release of the Lighttpd server package.
This computer has installed the Ubuntu operating system, but it has nothing to do with the Ubuntu Project. Please do not contact the Ubuntu Project about it.
If you find a bug in this Lighttpd package, or in Lighttpd itself, please file a bug report on it. Instructions on doing this, and the list of known bugs of this package, can be found in the Ubuntu Bug Tracking System.