Interrupted Update with ctrl-c now pihole -up won't work and admin Interface is not reachable

[mrgnz]

pihole -v
Pi-hole version is v6.0.1 (Latest: v6.0.1)
web version is v6.0 (Latest: v6.0)
FTL version is v5.25.2 (Latest: v6.0)

pihole -d
https://tricorder.pi-hole.net/QtXuN0kN/ (cant access it myself, no idea why)

Errors in pihole -d
*** [ DIAGNOSING ]: Dashboard headers
[✗] Web interface X-Header: X-Header does not match or could not be retrieved.
HTTP/1.1 403 Forbidden
Content-Type: text/html
Content-Length: 341
Date: Thu, 20 Feb 2025 08:36:29 GMT
Server: lighttpd/1.4.63

*** [ DIAGNOSING ]: contents of /etc/lighttpd/conf.d
/etc/lighttpd/conf.d does not exist.

Expected Behaviour:

Access to admin web-interface should work and pihole -up should work.

Actual Behaviour:

I ran pihole -up yesterday and while fiddeling with tmux and different clients I accidentally hit ctrl-c mid update.

After that I wasn't able to run pihole -up again:

pihole -up
/opt/pihole/update.sh: line 108: : No such file or directory

The directory exists and all files are present there

Further I cannot access the admin webpage. I get a 404 message.

Other than that the pihole seems to do its work. (Tested with Pi-Hole Ad Tester – Fuzz The Pi Guy)

What can I do to resolve this? Newly install pihole?!

Debug Token:

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

[nero355]

You are running Pi-Hole v6 so you don't need LigHTTPd and PHP any longer

What does

systemctl status pihole-FTL

show at the moment ?

[mrgnz]

It says:

systemctl status pihole-FTL
● pihole-FTL.service - Pi-hole FTL
     Loaded: loaded (/etc/systemd/system/pihole-FTL.service; enabled; vendor preset: enabled)
     Active: active (running) since Thu 2025-02-20 00:21:06 CET; 14h ago
    Process: 1013 ExecStartPre=/opt/pihole/pihole-FTL-prestart.sh (code=exited, status=0/SUCCESS)
   Main PID: 1071 (pihole-FTL)
      Tasks: 19 (limit: 2136)
     Memory: 38.6M
        CPU: 13min 32.363s
     CGroup: /system.slice/pihole-FTL.service
             └─1071 /usr/bin/pihole-FTL -f

Feb 20 00:21:30 pihole pihole-FTL[1071]: [2025-02-20 00:21:27.385 1071M] Resizing "FTL-queries" from 2064384 to (40960 * 56>
Feb 20 00:21:30 pihole pihole-FTL[1071]: [2025-02-20 00:21:28.132 1071M] Resizing "FTL-queries" from 2293760 to (45056 * 56>
Feb 20 00:21:30 pihole pihole-FTL[1071]: [2025-02-20 00:21:28.734 1071M] Resizing "FTL-queries" from 2523136 to (49152 * 56>
Feb 20 00:21:30 pihole pihole-FTL[1071]: [2025-02-20 00:21:29.296 1071M] Resizing "FTL-queries" from 2752512 to (53248 * 56>
Feb 20 00:21:30 pihole pihole-FTL[1071]: [2025-02-20 00:21:30.061 1071M] Resizing "FTL-queries" from 2981888 to (57344 * 56>
Feb 20 00:21:30 pihole pihole-FTL[1071]: [2025-02-20 00:21:30.230 1071M] New upstream server: 9.9.9.10:53 (11/512)
Feb 20 00:21:30 pihole pihole-FTL[1071]: [2025-02-20 00:21:30.646 1071M] Imported 55118 queries from the long-term database
Feb 20 00:21:30 pihole pihole-FTL[1071]: [2025-02-20 00:21:30.655 1071M]  -> Total DNS queries: 55118
Feb 20 00:21:30 pihole pihole-FTL[1071]: [2025-02-20 00:21:30.655 1071M]  -> Cached DNS queries: 9695
Feb 20 00:21:30 pihole pihole-FTL[1071]: [2025-02-20 00:21:30.656 107

Well I guess pihole generally works. Still I cannot run pihole -up anymore and admin webinterface isnt reachable.

[nero355]

Can you access Pi-Hole on port 8080 or 8443 ?!

So something like http:// your Pi-Hole IP address/admin:8080 for example ?

If not : Can you run a repair of Pi-Hole ?

Last resort, but a bit weird : Maybe switch to checkout dev then update and then back to the master branch and update again ?!

Otherwise it's either manually fixing stuff or uninstall and reinstall Pi-Hole

[mrgnz]

I cant connect with any other port. Neither with foo.bar:port/admin nor foo.bar/admin:port. I tested it with both ports.

I'll the reconfigure option to try to repair it.

Edit:
Using pihole -r fixed it!
I've chosen repair to retain the configs. After a while it asked me if I wanted to quit using lighttpd which I obiously have chosen. Then it said that it'll be listening to port 8080. It seems like some postupdate script for exactly this scripts didn't trigger due to me hiting ctrl-c during the first update.

Thanks for the help.

[rdwebdesign]

@mrgnz

cant access it myself, no idea why

Because only Pi-hole team has access to the uploaded logs.

You can see your own log in /var/log/pihole/pihole_debug.log

[mrgnz]

Thanks for clarifying.