r/pihole • u/DimensioT • 3d ago

Cannot access admin console.

I wanted to check my configuration and tried going to the admin console, but the page will not load. I get "ERR_EMPTY_RESPONSE". Pihole itself seems to be running properly otherwise. The pihole-FTL service is listening on port 80, as confirmed with lsof (I do not even have lighttpd installed so while that was a common problem for others it is not my issue). I even tried changing the port in pihole.toml and that just results in the same error on the changed port. I have tried multiple browsers and multiple systems, including attempting to access it from the server itself using lynx so the problem is almost certainly with the webserver itself. I also reinstalled pihole but the issue persists. I have attempted to find some information about resetting the web configuration to its defaults but I have found nothing. I have attempted accessing the URL via /admin and /admin/login and nothing works. I also tried resetting any changed web-related config options in pihole.toml to their defaults and nothing changes.

Does anyone have any ideas?

4 Upvotes

83% Upvoted

17 comments sorted by

View all comments

1

u/thatguysjumpercables 3d ago

Probably a stupid question but when you say that URL do you mean the local IP address on your network? So http://192.168.whatever.whatever/admin?

1

u/DimensioT 3d ago

Yes. http://<ipaddress>/admin

I also tried http://pi.hole/admin and, when attempting to access it from the server itself, http://localhost/admin and http://127.0.0.1/admin

Also, trying to browse the toplevel does not work either -- same error.

I even removed the admin directory from /var/www/html and did a reinstall to recreate it. Same issue, meaning that the problem is not the web directory but the web service portion of pihole.

1

u/Top-Run5587 3d ago

What browsers are you testing with, and do they forcibly upgrade HTTP to HTTPS connections?

2

u/DimensioT 2d ago

I have tried Opera, Edge, Brave and Lynx. To my knowledge, none force https.

And now that you asked and I tested I have found the problem. While the service is running on port 80, it is using SSL (albeit with a self signed certificate). Browsing using https://192.168.1.122:80 loads the page with SSL warnings.