I’ve tried using all three methods to access the web interface and none of them work. When I try using the https://<IP_ADDRESS_OF_YOUR_PI_HOLE>/admin/ I get search results to access my router login. (I obviously replace the link with my pihole’s IP address but I still get router login results)
Accessing through pi.hole/admin or pi.hole usually works but I keep having trouble connecting to the site. Checked downforeveryoneorjustme.com and it looks like pi.hole is down. Has this happened to anyone before? Do I just wait for the site to go back up?
When I try using the https://<IP_ADDRESS_OF_YOUR_PI_HOLE>/admin/ I get search results to access my router login.
Something is very wrong if you’re getting search results, maybe try a different browser?
Checked downforeveryoneorjustme.com and it looks like pi.hole is down.
The PiHole website is https://pi-hole.net/ is that what you meant to check?
You can’t check local private domains like pi.hole using a public service.
I’d check its IP in the router then try and access it via http, not https.
But my version in still 5.something and v6 could bring https, I have yet to update my LXCs
You are going to get a lot better advice posting on the pihole forum discourse.pi-hole.net
Try http rather than https
Aside from trying to reboot the pi-hole, you can also try plugging a monitor, and keyboard and mouse directly. You’ll get a better answer. Just waiting is not usually helpful.
downforeveryoneorjustme.com would not help as your pihole is a local service accessible only within your network.
downforeveryoneorjustme.com would not help as your pihole is a local service accessible only within your network.
Worth emphasizing. The call about the server being down is coming from inside the house!
Is that something you control? Because pi.hole is not a registered domain name. (And I wouldn’t trust a random person’s pihole anyway.)
Assuming it’s your local pihole and you have DNS set up, I would check that configuration start to finish.
Did you update from 5 to 6? That introduced a bunch of fuckery
This. After the most recent major version upgrade, I found mine was listening on port 8080. OP should try:
