I've done a pihole -up and, foolishly, I started to mess with the wifi signal without realizing that I had run the pi-hole update, so when I make changes to channels or MHz, the router restarts, and the update is left half done.
I have full access to pi-hole via ssh, but I can't access it at all via the web interface.
I've read these forums, used chatgpt and I can't find the key, among other things I've already done 2-3 "pihole -r" or similar, so that I end up getting a configuration completion screen and it checks the IP and port of Pi-hole to try to see that nothing has changed in the way of access, and it seems that it hasn't. Besides the fact that the Rasp is configured with the IP 192.168.1.152 as always with the Pi's MAC, the same thing happened to me when connecting it to a screen, running Raspberry OS updates via wifi, rebooting and re-running "pihole -r" with the IP .99 in this case and I still couldn't get the web interface.
The command sudo systemctl disable lighttpd will disable the lighttpd service, as Pi-hole v6 now uses a built in web server instead of lighttpd. Disabling it will cause less conflict with pihole-FTL.
Since you disabled lighttpd after the update was finished FTL may have used port 8080, you can try accessing the web interface at http://192.168.1.152:8080/admin.
If this still doesnt work please post your debug log link after running sudo pihole -d
Your configuration is not wrong, but it is a little unorthodox.
You set 2 ports for http (80 and 8080) and 2 ports for https (443 and 4443), but all ports use IPv4. No IPv6 ports were added. Was this intentional?
The default settings use 80 and 443, IPv4 and IPv6: "80o, 443os, [::]:80o,[::]:443os"
(o means "optional". You can remove it if you know your server doesn't use other web server).
I check that, because it suggested the interface go to https and paradoxically it don't enter at the beginning then ask me for this, and by the way maybe I will redirect that internal port as I have started do with my NAS and home automation server.
You can either edit the port line in /etc/pihole/pihole.toml or in the Web interface
All Settings > Webserver and API > webserver.port when in Expert mode.
If this configuration is unorthodox, then why is it provided as an example?:
# ... This flag may be
# combined with 'r' and 's' like "80or,443os,8080,4443s" (80 redirecting to SSL if
# available, 443 encrypted if available, 8080 mandatory and unencrypted, 4443
# mandatory and encrypted).
My attempts at concocting this setting have failed, so until the ideal permutation becomes clear, I'm sticking with this.
Omitting IPv6 is intentional, as I disable it globally.
