The issue I am facing:
I have installed pihole on a raspberry pi 4. It appears that the pihole is working and blocking ads. I saw other forums that there was conflicts between services using the same ports, but that does not seem to be the issue here.
Im not sure if this is related, but i am getting errors in my debug file that there are failed connection attempts even though i am able to access the internet and am currently blocking ads. I cannot access the portal locally or through any other pc on the network.
Your debug log shows that pihole-FTL is listening for HTTP requests on port 80, indicating that this is a Pi-hole v6 installation:
*** [ DIAGNOSING ]: Ports in use
udp:0.0.0.0:5353 is in use by avahi-daemon
udp:0.0.0.0:47111 is in use by <unknown>
udp:0.0.0.0:123 is in use by pihole-FTL
udp:0.0.0.0:37051 is in use by avahi-daemon
udp:*:5353 is in use by avahi-daemon
udp:*:58886 is in use by avahi-daemon
udp:*:47111 is in use by <unknown>
[✓] udp:0.0.0.0:53 is in use by pihole-FTL
[✓] udp:*:53 is in use by pihole-FTL
[✓] tcp:[::]:53 is in use by pihole-FTL
[✓] tcp:0.0.0.0:53 is in use by pihole-FTL
udp:*:123 is in use by pihole-FTL
[✓] tcp:0.0.0.0:443 is in use by pihole-FTL
[✓] tcp:[::]:443 is in use by pihole-FTL
tcp:0.0.0.0:22 is in use by sshd
[✓] tcp:0.0.0.0:80 is in use by pihole-FTL
[✓] tcp:[::]:80 is in use by pihole-FTL
tcp:127.0.0.1:631 is in use by cupsd
tcp:127.0.0.1:44091 is in use by containerd
tcp:0.0.0.0:4001 is in use by lighttpd
tcp:[::]:22 is in use by sshd
tcp:[::1]:631 is in use by cupsd
tcp:[::]:4001 is in use by lighttpd
That would suggest that you should be able to access Pi-hole's UI via http://pi.hole/admin, or in case the accessing browser would not use Pi-hole for DNS via http://192.168.1.36/admin (provided you are accessing this from your home network, and not via Wireguard).
It's unusual though that an unknown process is listening on port 47111.
That is the wireguard port from Pi-hole's Wireguard guide.
Is this a fresh install of Pi-hole v6 or an upgrade from v5?
Clarification:
I am not using wireguard for this connection, i am unable to connect from home network.
This is a fresh install of v6. I have purged and reinstalled twice now, to no avail.
"It's unusual though that an unknown process is listening on port 47111."
^^ Yeah this was my own doing following some tutorial for a pihole/VPN that suggested to use that port. While this is the end goal, I want to get Pi-Hole working before I worry about the VPN side of things lol. Could this be part of the issue? Even though i am not currently using the wireguard interface or VPN connection?
"Is this a fresh install of Pi-hole v6 or an upgrade from v5?"
This is a fresh install of v6. I have purged and reinstalled twice now, to no avail.
I am sure i am on the same network. I can ssh into the device on the same device, so I'm on the same network, I just cant see the admin portal for whatever reason.
My pihole -d command shows the pihole-FTL is using port 80, so it shouldn't be the case that a different webserver is being used here.
Is there a way to get the pi-hole webserver to use a different port? That feels easier than trying to pin down whatever other webserver conflict is running alongside.
I could disable lighttpd, but I have done this before and it did not fix the issue, however i am not against trying again if you'd like to see some results from this troubleshooting.
Should note I also tried to access locally on the pi itself and could not reach it there either.
OK.
I found a very unusual way to replicate your screenshot.
Error 404: Not Found
Not found
If I move most of the files from /var/www/html/admin to a different place, the web server will show the same error message, but this is not a normal circumstance.
