192.168.1.1 Not Working - 8 Fixes

When typing 192.168.1.1 in your browser loads a blank page, an error, or just spins forever, one of these eight causes is almost always responsible. Work through them in order - most people find their fix within the first three.

Before You Start

Run ipconfig on Windows or ip route show default on Mac/Linux. Look at the Default Gateway value. If it is not 192.168.1.1 - if it shows 192.168.0.1 or 10.0.0.1 or something else - then your router does not use 192.168.1.1 at all. Use whatever IP appears in the Default Gateway field instead.

The single most common reason 192.168.1.1 fails is that the router actually uses a different address. Always confirm with ipconfig first.

Fixes in Order of Likelihood

1

Add http:// explicitly

Modern browsers automatically try HTTPS on addresses they recognise. Type http://192.168.1.1 with the http:// prefix in full. Without it, Chrome and Edge redirect to https://192.168.1.1 - which fails because the router has no SSL certificate, producing a "connection refused" or certificate error.
2

Disconnect your VPN

A VPN tunnels all traffic through an external server, making local IP addresses completely unreachable. If you have a VPN client running - NordVPN, ExpressVPN, ProtonVPN, or a corporate VPN - disconnect it, then try 192.168.1.1 again. See: Disable VPN for router access.
3

Check you are on Wi-Fi, not mobile data

192.168.1.1 is a local network address - it only works when you are connected to your home network. If your phone switched to mobile data (4G/5G) automatically, or you are connected to a hotspot, the router address is unreachable. Pull down your phone's status bar and verify Wi-Fi is the active connection.
4

Clear browser cache or use incognito

A cached bad response can block the router page from loading even after fixing other issues. Press Ctrl+Shift+N (Windows) or Cmd+Shift+N (Mac) to open an incognito window, then try http://192.168.1.1 there. If it loads in incognito, clear your browser cache entirely. See: Clear browser cache guide.
5

Power cycle the router

Unplug the router's power adapter from the wall. Wait a full 30 seconds - not 5, not 10. Plug it back in and wait 60 seconds for the router to fully boot. Then try 192.168.1.1. A soft reboot via the router's power button often does not fully clear the issue; a physical power disconnect does. See: Power cycle guide.
6

Try a different browser

Browser extensions - particularly ad blockers, privacy tools, and security suites - can interfere with local IP navigation. Try Firefox or Edge if you normally use Chrome, or vice versa. If a different browser works, disable extensions one at a time in your main browser to identify the culprit.
7

Flush your DNS cache

On Windows: open Command Prompt and run ipconfig /flushdns. On Mac: run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder in Terminal. Then try the router address again. A stale DNS cache can sometimes prevent resolution of local hostnames though it rarely blocks a numeric IP - still worth trying if other steps fail.
8

Factory reset as last resort

If someone changed the router's admin IP address to something other than 192.168.1.1, a factory reset is the only way to restore the default. Press and hold the pinhole Reset button on the back of the router for 10-30 seconds until the lights flash. After reset, 192.168.1.1 will respond again. Note: this erases all Wi-Fi settings, passwords, and port forwarding rules. See: Factory reset guide.

What Specific Error Messages Mean

Error Message	Likely Cause	Fix
ERR_CONNECTION_REFUSED	Router is not accepting connections, or wrong IP	Check your actual gateway IP with ipconfig
ERR_CONNECTION_TIMED_OUT	Not connected to the router network, or VPN active	Check Wi-Fi connection, disconnect VPN
This site can't provide a secure connection	Browser trying HTTPS instead of HTTP	Type http://192.168.1.1 with http:// prefix
Privacy error / NET::ERR_CERT_*	Router has no SSL certificate	Click Advanced → Proceed anyway, or use http://
ERR_NAME_NOT_RESOLVED	Typed as a hostname, not an IP	Ensure you are typing numbers not a search query
Page loads but immediately redirects	Router firmware redirect loop	Clear browser cache, try incognito

FAQ

192.168.1.1 worked yesterday but not today - what changed?

The most common overnight changes: a VPN app auto-connected at startup, a Windows update changed network adapter settings, or the router accumulated a software fault after extended uptime. Start with the VPN check and a power cycle - these resolve the majority of "worked yesterday" cases.

Can I access 192.168.1.1 from a different network?

No. 192.168.1.1 is a private IP address that only exists on your local network. You cannot reach your home router from a coffee shop or a friend's house unless you have set up remote management or a VPN server on the router itself. From outside your network, your router is only accessible via its public IP address on specific ports.