Please follow the below template, it will help us to help you!
If you are Experiencing issues with a Pi-hole install that has non-standard elements (e.g you are using nginx, apache2 or another reverse proxy, or there is some other aspect of your install that is customised) - please use the Community Help category.
Expected Behaviour:
Installed on Raspberry Pi OS, I am trying to access the web interface using the standard http://<ip-address>:8443/admin. I’ve set it up to redirect port 8080, but when I use either port, it’s not working. My Pi has other things installed on it, but I’ve checked the ports, and they’re not being used by anything else. I’ve removed the IPv6 ports as I don’t have it configured for IPv6
Actual Behaviour:
I’m getting “this site can’t be reached, it took too long to respond. ERR_CONNECTION_TIMED_OUT”
Debug Token:
https://tricorder.pi-hole.net/7X3qyqP4/
Your debug log shows Pi-hole web server is using the correct ports 8080 and 8443:
[✓] tcp:0.0.0.0:8443 is in use by pihole-FTL
...
[✓] tcp:0.0.0.0:8080 is in use by pihole-FTL
And the machine IP is: 192.168.1.42
Just to confirm: did you use the correct IP and port: http://192.168.1.42:8443/admin?
You log also shows the log files (webserver.log and FTL.log) are empty, which is not expected.
Please check if the FTL service is still running using this command:
sudo systemctl status pihole-FTL.service
That is correct, yes. Even clicking on your hyperlink in your message doesn’t take me to the interface, just the same “ERR_CONNECTION_TIMED_OUT” screen
Ohh... I edited the other message while you answer it.
Please try the command suggested.
Running this command gives me the following response -
“Unit FTL.service could not be found.”
I don’t understand how it isn’t found, I ran pihole -r before all this to confirm it was installed
I'm an idiot... I didn't notice there was a typo.
The correct command is:
sudo systemctl status pihole-FTL.service
That’s okay, we all make mistakes 
The response to the new command is as follows:
● pihole-FTL.service - Pi-hole FTL
Loaded: loaded (/etc/systemd/system/pihole-FTL.service; enabled; preset: enabled)
Active: active (running) since Sun 2025-12-21 23:54:04 GMT; 1h 10min ago
Process: 11419 ExecStartPre=/opt/pihole/pihole-FTL-prestart.sh (code=exited, status=0/SUCCESS)
Main PID: 11444 (pihole-FTL)
Tasks: 12 (limit: 758)
CPU: 29.576s
CGroup: /system.slice/pihole-FTL.service
└─11444 /usr/bin/pihole-FTL -f
Dec 21 23:54:04 jumpbox pihole-FTL[11444]: 2025-12-21 23:54:04.510 GMT [11444M] INFO: FTL user: pihole
Dec 21 23:54:04 jumpbox pihole-FTL[11444]: 2025-12-21 23:54:04.510 GMT [11444M] INFO: Compiled for linux/arm64/v8 (compiled on CI) using cc (Alpine 14.2.0) 14.2.0
Dec 21 23:54:04 jumpbox pihole-FTL[11444]: 2025-12-21 23:54:04.518 GMT [11444M] INFO: Wrote config file:
Dec 21 23:54:04 jumpbox pihole-FTL[11444]: 2025-12-21 23:54:04.518 GMT [11444M] INFO: - 162 total entries
Dec 21 23:54:04 jumpbox pihole-FTL[11444]: 2025-12-21 23:54:04.518 GMT [11444M] INFO: - 158 entries are default
Dec 21 23:54:04 jumpbox pihole-FTL[11444]: 2025-12-21 23:54:04.518 GMT [11444M] INFO: - 4 entries are modified
Dec 21 23:54:04 jumpbox pihole-FTL[11444]: 2025-12-21 23:54:04.518 GMT [11444M] INFO: - 0 entries are forced through environment
Dec 21 23:54:04 jumpbox pihole-FTL[11444]: 2025-12-21 23:54:04.522 GMT [11444M] INFO: Parsed config file /etc/pihole/pihole.toml successfully
Dec 21 23:54:04 jumpbox pihole-FTL[11444]: 2025-12-21 23:54:04.522 GMT [11444M] INFO: PID file does not exist or not readable
Dec 21 23:54:05 jumpbox pihole-FTL[11444]: 2025-12-21 23:54:04.522 GMT [11444M] INFO:
Do you need anything else, or is the above enough?
For anyone else who’s having the same problem as me and also isn’t getting an answer or help, the only way I managed to resolve it was rebuilding pihole in a docker container on my pi