Written 5 Sep 2026. This is a how-to, not a product card.
When the Pi-hole admin page won't open
http://pi.hole/admin or the computer's address plus /admin won't load. Check house Wi-Fi, the address, then Pi-hole and the web service. You don't need a new router.
Haven't installed Pi-hole yet? Start with the first useful thing. Ads are back house-wide, but the dashboard still opens? That is when ads come back. Login form shows and the password fails? That is change the Pi-hole admin password. This note is the blank or timed-out browser tab.
Skip until Pi-hole is installed
If you never ran the installer, stop here. Put ad block on the old PC first: the first useful thing. Don't buy a Raspberry Pi because a bookmark failed. Don't open port 80 or 443 on the router to "test" the dashboard from outside.
What this is
The admin page is a small web UI on the same computer that runs Pi-hole. The browser has to reach that computer on the house network, then the web service has to be up. pi.hole is only a shortcut when your DNS already asks Pi-hole. The number plus /admin works even when the shortcut name does not.
Step 1: same house network
Phone or laptop on house Wi-Fi (or a cable into the same router). Guest Wi-Fi often cannot see the computer. Cellular never will. Guest SSID still weird for ads? See when guest Wi-Fi still shows ads.
Step 2: prove the computer is awake
Power light. Fan. Soft-off looks like a dead dashboard. Check before you reinstall: is it still on?. Wake from the couch if it is soft-off: wake the computer from the house network.
SSH from the laptop on the house network:
ssh youruser@192.168.1.50
Swap the login and the number. Can't connect? Fix that first: when SSH won't connect. Forgot the number? find it on the house network.
Step 3: try the number, not only pi.hole
In the browser, type exactly (swap the address):
http://192.168.1.50/admin
Use http, not https, unless you set TLS on purpose. A padlock error or a blank https tab is often the wrong scheme. If the number works and http://pi.hole/admin does not, DNS on that phone or laptop is not asking Pi-hole yet. Point the router: point the house at the ad block, or brand menus in point common home routers at Pi-hole. One device when the router won't: point a phone or laptop at Pi-hole when the router won't. A short house name later: add a local name in Pi-hole.
Step 4: match what the browser shows
| What you see | Likely cause |
|---|---|
| Timed out / can't reach this page / site can't be reached | Wrong address, asleep computer, guest Wi-Fi, or the web service is down. Steps 2–5. |
| Connection refused | Nothing listening on port 80, or a firewall blocked it. Steps 5–6. |
| Login form loads, password fails | Wrong page. Reset the admin password: change the Pi-hole admin password. |
| https warning / certificate error | Try http:// plus the number and /admin. Skip forcing https on day one. |
| pi.hole fails, number works | That device is not using Pi-hole for DNS. Step 3. |
Step 5: check Pi-hole and the web service
From SSH on the computer:
pihole status
You want FTL running and blocking enabled. Then see if the web service answers on the computer itself:
curl -I http://127.0.0.1/admin/
A 200 or 301/302 means the page is up locally. If curl fails on the box, restart DNS and the usual services:
pihole restartdns
sudo systemctl restart lighttpd
On some installs the unit is pihole-FTL only and lighttpd is gone; if systemctl status lighttpd says the unit is missing, skip that restart and rely on pihole restartdns, then try curl again. Still dead after a status failure? The quieter check before you buy anything: when ads come back, check the ad block.
Step 6: firewall without locking yourself out
If you turned on ufw and forgot HTTP:
sudo ufw status
Allow house LAN HTTP only if you understand the rule, or temporarily:
sudo ufw allow from 192.168.0.0/16 to any port 80 proto tcp
Swap the house range if yours is 10. something. Don't ufw allow 80 to the whole internet. Fuller walk: turn on a simple firewall without locking yourself out.
Step 7: confirm from the laptop
Reload http://THE-NUMBER/admin on house Wi-Fi. Log in. If the form appears, you are done with this page. Change a sticky-note password: change the Pi-hole admin password. Weekly software and lists: keep Pi-hole updated. One bank page broken while ads stay gone: when a site won't load after Pi-hole.
What this is not
This is not a reason to buy a Raspberry Pi, a mesh kit, or a new router. It is not opening the admin page past the house network. It is not "ads came back on every device" (that is when ads come back). It is not a wrong admin password when the login form already loads.
What next
When the dashboard opens, leave it on the house network. Point the router if you have not: point common home routers at Pi-hole. Keep a Teleporter export before scary changes: save a Pi-hole backup. A file share on this same computer can wait: a file share.
Optional: note which browser error you hit in Lab plan — username + passkey, no email. Skip if you just want to keep reading.
Skip
- Skip opening port 80 or 443 on the router to the internet.
- Skip buying a Raspberry Pi because
pi.holefailed once. - Skip forcing https on day one.
- Skip a mesh kit for a blank admin tab.
- Skip reinstalling Pi-hole before you try the number plus
/admin. - Skip this if ads are back house-wide but the dashboard already loads. That is a different walk.
Sources
Pi-hole docs. Pi-hole basic install (admin URL). Pi-hole command (status, restartdns). Official pages only. For install, see the first useful thing. For ads returning house-wide, see when ads come back. For the password when the form already loads, see change the Pi-hole admin password.