Pi-Hole admin page giving '404 page not found'1

[yakobschamwow]

Expected Behaviour:

When running the curl command curl -L http://localhost:443/admin/ on my machine with pihole, it should print a success code and the content of the admin page. Also, would expect to be able to access the page by going to the website“http://${PIHOLE_IP}:443/admin” on a separate machine.

I am running this on a mini Beelink PC with Fedora Linux 42 (Server Edition) installed. I installed using the first alternative method in GitHub (cloned the repo, ran basic-install.sh).

I had previously used docker to run pihole, but wanted to get away from docker in general, so deleted all that stuff, uninstalled docker and tried installing pi-hole directly.

Actual Behaviour:

When running the curl command curl -L http://localhost:443/admin/ on my machine with pihole installed, I see ‘404 page not found’ as the output. On a separate PC, going to the website "http://${PIHOLE_IP}:443/admin” gives a blank screen with the same error text: “404 page not found.”

Debug Token:

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

Saw there were some other topics on this in the past, but none of those solutions worked for me…. not sure what’s going on here. I’m not very smart when it comes to networking so any help here would be appreciated. Thank you!

[rdwebdesign]

Why are you using port 443 for http?

This port is usually used to access using https (secure HTTP).
I'm not sure if there is a firewall rule blocking this port, specially if you are connecting using http protocol.

Your debug log shows there is nothing currently using port 80.
Try to configure Pi-hole to use port 80 and 443:

sudo pihole-FTL --config webserver.port '80o,443so'

And try again.

---

Note:

The o is a flag to make the port "optional". This means that the web server will start even if this port is not available.
The s flag is used to mark a port as "secure". It is used to define ports for https protocol.

[yakobschamwow]

Thanks for the response. I think I had tried both port 80 and 443, but didnt mention that in my post (both gave the 404 error). I did just run that config command to use both port 80 and 443 but it’s now giving the same result. Even stopped firewalld and re-ran the curl command and it’s still giving a 404 (turned it back on after, lol).

Here’s my new debug log: https://tricorder.pi-hole.net/fTDgnh1f/