No admin page on update Pihole v6.0.5 on RP Zero W

Help
1

I am using Pihole installed with apache2 on a Raspberry Pi Zero W. It was working great until I mistakenly did "pihole -up". It erased the update command as well as the index.php and who knows what else. It is still running well in the background but now there is no way to make edits or changes.
When I go to http://x.x.x.x/admin it goes to the Index of /admin directory but there are no pihole files there

Debug Token:

https://tricorder.pi-hole.net/fAXa8weY/

2

What do you mean? Please elaborate.
The command to update Pi-hole is the same in v5 and v6: pihole -up

Each of these changes (and a lot more) were described in v6 release notes:

Pi-hole v6 now uses its own web server (embedded into FTL). Apache2 cannot execute the new web interface pages.

The installer identified there was something using port 80 (apache2) and used the alternative port 8080 for the new web server (pihole-FTL):

*** [ DIAGNOSING ]: Ports in use
...
[✓] tcp:0.0.0.0:8080 is in use by pihole-FTL
...
[✓] tcp:0.0.0.0:443 is in use by pihole-FTL
...
[✗] tcp:*:80 is in use by apache2

Also note that Pi-hole now offers https (port 443).

Currently you can access the web interface using one of the URLs below:

Note:

You are running an outdated and unsupported OS (Raspbian 10).

3

Thank you very much. I thought I tried all the different ports including 8080 but must have been during one of the changes that didn't work.

And yes, the pihole -up command showed up as No such file exists... but I wiggled around and the pihole -r must have fixed it.

It works using those links now. Port 8080.
Yes, I'm using an outdated system but that can't be helped. The Raspberry Pi Zero W required a LOT of work arounds just to get a VPN, Pi-hole, and Discord bot running. With only a few MB of memory left I'll just let it run in peace until it all breaks.

Thanks again.

4

i had same issue with latest update. i wound up reloading from scratch to get it up and running again. funny/not funny that the most current update was the update that it performed the first time around. the most irritating part of it was it was my first update to my new raspberry pi 5. alls good now.