Router Login Page Won't Load — Fix Guide

Six things to check, in order, when typing your router's IP doesn't open anything.

Quick answer

The login page won't open in 95% of cases for one of four reasons: wrong IP, browser cache, VPN/proxy interference, or the router is unreachable. Use our reachability tester to confirm the IP is alive, then clear cache and try http:// + https:// + a different browser.

You typed 192.168.1.1 (or whatever your router is), and the browser just spins. Frustrating, but methodical troubleshooting almost always finds the cause within a few minutes.

Pre-flight checklist (30 seconds)

You're on the router's Wi-Fi — not mobile data, not a guest network, not a corporate VPN.
Other devices on the same Wi-Fi can reach the internet — confirms the router is up.
The IP you're typing is correct — verify with our IP detection tool.

Most common causes & fixes

1. Wrong router IP

You assumed 192.168.1.1 but your router is actually 192.168.0.1, 192.168.50.1, or 10.0.0.1. Run ipconfig (Windows) or ip route | grep default (Mac/Linux) and use whatever it returns. Or just open our auto-detect tool.

2. Browser cached a redirect or wrong page

If you previously visited the router at a different IP, the browser may be sending you somewhere else. Fixes:

Hard refresh: Ctrl+Shift+R (Win/Linux) or Cmd+Shift+R (macOS).
Try in an Incognito / Private window.
Clear cache for the last hour.
Try a different browser (Firefox, Edge, Safari).

3. Wrong protocol (HTTP vs HTTPS)

Modern routers redirect to HTTPS with a self-signed certificate — your browser shows a scary "Not secure" warning. That's normal. Try both http://192.168.1.1 and https://192.168.1.1 explicitly.

4. VPN or proxy hijacking traffic

Active VPN clients (NordVPN, ExpressVPN, ProtonVPN, corporate VPNs) often route all traffic, including local. Disconnect the VPN, then retry. Same for any system-level proxy in your OS network settings.

5. Browser-extension interference

Ad blockers, privacy extensions, and security plugins occasionally block requests to private IPs. Open the page in Incognito (where extensions are usually disabled) or temporarily disable extensions.

6. Router itself is unreachable

Run our reachability test. If all four methods fail, the router is genuinely unresponsive. Try:

Power-cycle: unplug the router for 30 seconds, plug back in, wait 2 minutes.
Plug into the router with an Ethernet cable — bypasses any Wi-Fi issue.
If still unreachable, factory reset (see our How to reset guide).

7. Firewall or antivirus blocking

Some security suites block access to "private network admin interfaces" by default. Temporarily disable the firewall portion of your antivirus (Norton, McAfee, Kaspersky) and retry.

8. Wrong subnet

If your laptop got an IP like 169.254.x.x (APIPA) or a totally different subnet from the router, DHCP failed. Restart networking, or set a static IP on your device in the router's subnet.

Diagnostic decision tree

Symptom	Most likely cause	Try
Browser hangs forever	Wrong IP or router down	Verify IP, ping it, power-cycle
"Site can't be reached"	Router unreachable	Reach test, Ethernet cable, reset
"Your connection is not private"	HTTPS self-signed cert — normal	Click Advanced → Proceed anyway
Login page loads but credentials fail	Forgotten password	See our forgot-password guide
Page loads partially / blank	JavaScript blocked / cache	Incognito, different browser, clear cache
Redirects to ISP captive portal	You're on a temp/guest SSID	Connect to your real Wi-Fi

When all else fails: the nuclear option

Factory-reset the router (30-second pinhole hold). After the reset:

Connect to the default Wi-Fi name (printed on the sticker).
Visit the default IP (also on the sticker).
Sign in with default credentials.

Frequently asked questions

Why does Chrome say my router is dangerous?

Chrome's HSTS preload list flags any HTTPS site with an invalid certificate. Your router uses a self-signed cert because it has no public domain. Click Advanced → Proceed to 192.168.x.x (unsafe) — it's safe on your own LAN.

Why can my phone reach the router but my PC can't?

Your PC probably has a stale IP, a VPN running, a firewall block, or DNS pointing somewhere weird. Restart its network adapter and disable the VPN.

I see the login page but it never accepts my password — is the router broken?

Probably not. The credentials may have been changed by an ISP installer or a household member. Try the defaults from the sticker; if those fail, factory-reset.

My router has no admin web page at all — only a mobile app.

Some modern mesh systems (Google Nest Wifi, eero, original Linksys Velop) only configure via the manufacturer's app. There's no IP to type — install the app and sign in with your account.

I get "ERR_CONNECTION_REFUSED" specifically — what's that?

The router answered, but refused the connection on that port. Try the other protocol: if HTTP refused, try HTTPS, and vice versa. Some routers move admin to port 8080 (try http://192.168.1.1:8080).