Admin Web page not loading for administration when going to pihole.local/admin
Running Pi-Hole 6
Raspberry Pi 4
Device is still functional, still running Lookup's etc.
It's as though some DNS information isn't working properly? I'm not quiet sure... I've added the debug token below.
You changed the port from 80 to 8088:
[webserver]
port = "8088o,8443os,[::]:8088o,[::]:8443os" ### CHANGED, default = "80o,443os,[::]:80o,[::]:443os"
You need to add the port (:8088) to the URL. Also, the domain pihole.local is not the correct one.
Try one of the URLs below:
Or reconfigure the ports to use the default values and access without the ports.
First, thanks. After using the updated port in my url, that did work...
But this is strange because I didn't change it, or if I did, I unknowingly changed it.... How would I go back to allowing access on port 80?
To return to the default ports (80 and 443), run this command:
sudo pihole-FTL --config webserver.port '80o,443os'
I've ran that command and rebooted and it didn't appear to change... I've gathered another diagnostic:
https://tricorder.pi-hole.net/A8vWEeyn/
You made a mistake.
You replaced the comma (,) with a dot (.):
[webserver]
port = "80o.443os" ### CHANGED, default = "80o,443os,[::]:80o,[::]:443os"
Run the command again, but using a comma.
I copy/pasted your command from the above line twice, just to make sure... Still not loading with port 80...
Please generate a new debug token.
Looks like it took a bit. Wonder if internal DHCP needed to update?
https://tricorder.pi-hole.net/Lt0Gjmrz/
If you can view other settings and make recommendations, I'm all for it...
The log shows the previous attempt (using .):
[2025-04-25 11:59:18.397 CDT 1136] 80o.443os: invalid port spec (entry 1). Expecting list of: [IP_ADDRESS:]PORT[s|r]
[2025-04-25 11:59:18.397 CDT 1136] Failed to setup server ports
And the correct one:
[2025-04-25 16:29:36.328 CDT 1136] Initializing HTTP server on ports "80o,443os"
[2025-04-25 17:43:30.980 CDT 1136] Authentication required, redirecting to /admin/login
The web server is working.
Now you should be able to access the web interface using these addresses:
If it fails, please post the exact URL you are trying to access.