Written 6 Sep 2026. This is a how-to, not a product card.

When the home router page won't open

192.168.x.1, routerlogin.net, or the sticker URL won't load. Find the gateway number, use http on house Wi-Fi, then log in. You don't need a new router.

Trying to open Pi-hole's dashboard instead? That is when the Pi-hole admin page won't open. Haven't pointed house DNS at the computer yet, and you only need the brand menus? Start with point common home routers at Pi-hole. This note is the blank tab when the router or ISP gateway itself will not show a login page.

Skip until you mean the router, not Pi-hole

Pi-hole lives on the old PC. The router (or ISP gateway) is the box that hands out Wi-Fi and usually sits near the modem. If the page you want is http://pi.hole/admin or the computer's number plus /admin, stop and use when the Pi-hole admin page won't open. Don't factory-reset the gateway because a bookmark failed once.

What this is

Every phone and laptop on the house network has a default gateway: the address of the router that routes traffic out. The admin page is a small web UI on that gateway. You open it with the gateway number over http on the same house network. Sticker hostnames (routerlogin.net, tplinkwifi.net, and friends) only work when DNS still resolves them. After you point DNS at Pi-hole, the number is the reliable path.

Step 1: same house network

Phone or laptop on house Wi-Fi, or a cable into the same router. Guest Wi-Fi often cannot reach the gateway admin. Cellular never will. VPN apps on the phone can hide the real gateway. Turn the VPN off for this test. Guest SSID still weird for ads? See when guest Wi-Fi still shows ads.

Step 2: find the gateway number

Guessing 192.168.1.1 fails on a lot of houses (ASUS often uses 192.168.50.1, some TP-Link boxes use 192.168.0.1, ISP gateways vary). Read the number the laptop already has.

On a Mac or Linux laptop:

ip route | head -5

Or on many Macs:

route -n get default | grep gateway

On Windows, in Command Prompt or PowerShell:

ipconfig

Look for Default Gateway on the active Wi-Fi or Ethernet adapter. On an iPhone: Settings → Wi-Fi → the info button next to the house network → Router. On Android: the house network details → Gateway (wording varies). Write that number down. It is the one you will type in the browser.

Step 3: open http plus the number

In the browser, type exactly (swap your gateway):

http://192.168.1.1

Use http, not https, unless you set TLS on the router on purpose. A padlock warning or a blank https tab is often the wrong scheme. Don't add /admin unless that maker's docs say so. That path is for Pi-hole on the old PC, not for most home routers.

Sticker names are optional. If http://routerlogin.net or http://tplinkwifi.net fails after you pointed DNS at Pi-hole, ignore the name and use the gateway number from Step 2. You can allow a maker hostname later in Pi-hole if you want the shortcut back: allow a site in Pi-hole on purpose.

Step 4: match what the browser shows

Step 5: password when the form already loads

Sticker username and password, or the password you set in the maker app. ISP gateways sometimes want the account PIN or an app login instead of a local page. If the form is the Pi-hole admin form, you are on the wrong box: change the Pi-hole admin password is not the router password.

Don't factory-reset yet. A reset wipes LAN DNS and DHCP reservations and sends you back through when the ISP swaps your router style recovery even when the hardware did not change. Full password walk (sticker vs Wi-Fi passphrase vs maker app vs careful reset): when the router password won't work.

Step 6: prove the gateway answers

From the laptop, ping the gateway number (swap yours):

ping -c 3 192.168.1.1

On Windows:

ping -n 3 192.168.1.1

Replies mean the box is on the LAN path. No replies usually means wrong number, guest isolation, or a dead gateway. Power-cycle the gateway only after you have the right number and http still fails. Then retry Step 3.

Step 7: when you only needed DNS menus

Once the login page opens, set LAN or DHCP DNS to the computer if that was the job: brand menus in point common home routers at Pi-hole, or the shorter walk in point the house at the ad block. Keep the computer on one address: keep the computer on the same address on common routers. Nest or an ISP box that will not take custom DNS: point a phone or laptop at Pi-hole when the router won't.

What this is not

This is not a reason to buy a mesh kit or a new router on day one. It is not opening the router admin from a coffee shop. It is not the Pi-hole dashboard on the old PC. It is not "ads came back" when the router page already loads (that is when ads come back). It is not a factory reset as the first move.

What next

When the gateway login works, leave a bookmark to http:// plus the number. Form loads but password fails? When the router password won't work. Point DNS if you have not: point common home routers at Pi-hole. After a tech swap wiped settings: when the ISP swaps your router. Pi-hole dashboard blank instead? When the Pi-hole admin page won't open.

Optional: jot the gateway number that worked in Lab plan — username + passkey, no email. Skip if you just want to keep reading.

Skip

• Skip buying a new router because 192.168.1.1 was wrong for your house.
• Skip a factory reset before you try the real Default Gateway over http.
• Skip opening the gateway admin from cellular or from guest Wi-Fi.
• Skip forcing https on day one.
• Skip forwarding the router admin page to the internet.
• Skip this if you meant the Pi-hole dashboard on the old PC. That is a different walk.