Router Login Not Working: Why You Can't Access 192.168.1.1 and How to Fix It

A router admin panel that refuses to load is one of the most frustrating networking failures because it blocks every other fix. You cannot change Wi-Fi credentials, update firmware, or reconfigure DHCP without admin access. The cause is almost always one of five things, and once you know which, the fix takes under five minutes.

Quick Diagnosis: Symptom to Cause to Fix

Read the column that matches what you see, then jump to the section below.

Symptom you see	Most likely cause	Fix
Browser says “This site can’t be reached” or “ERR_CONNECTION_TIMED_OUT”	Wrong IP, or device on wrong network	Run ipconfig / ifconfig to find the real gateway
Browser shows a security warning (certificate error, NET::ERR_CERT_AUTHORITY_INVALID)	Browser forced HTTPS on an HTTP-only router	Type http:// prefix explicitly; clear HSTS for that IP
Page loads but says “Page not found” or shows a 404	Wrong path or hostname	Use the bare IP, not a brand hostname; or vice versa
Login page loads, credentials rejected	Wrong username/password	Check label; try defaults; factory reset if forgotten
Page loads briefly then drops, or loads on phone but not laptop	VPN, proxy, or firewall on the laptop	Disconnect VPN, disable firewall temporarily, test again
Nothing loads on any device	Router itself is hung	Power cycle (unplug 30s, plug back in)
Loads after reboot, then breaks again	Firmware bug or overheating	Update firmware; check ventilation; factory reset if persistent

What to Try First: The 60-Second Checklist

Run these in order before going deep. Most login failures resolve at step 3 or 4.

1. Confirm the network. Look at the Wi-Fi icon on your device. Is the SSID the router’s own SSID? Not a hotspot, not a neighbor’s Wi-Fi, not a guest network on a different router.
2. Confirm the IP. Open a terminal and find the gateway (commands below). Type that exact IP in the browser.
3. Use http:// explicitly. Type http://192.168.1.1, not 192.168.1.1. The browser is less likely to force HTTPS.
4. Turn off the VPN. Disconnect every VPN, proxy, and corporate tunnel client. Wait 5 seconds.
5. Try a private window. Cmd/Ctrl + Shift + N (Chrome/Edge) or Cmd/Ctrl + Shift + P (Firefox). This bypasses extensions, cache, and HSTS.
6. Try a different device. If the phone loads the admin page and the laptop does not, the issue is laptop-side (firewall, VPN, browser).
7. Power cycle the router. Unplug. 30 seconds. Plug back in. Wait 3 minutes for full boot.

Verify You Are Using the Correct IP Address

The single most common cause of a failed login is typing the wrong IP. Most routers default to 192.168.1.1, but many ship at 192.168.0.1, 192.168.0.254, 10.0.0.1, or a brand-specific address. ISP-provided routers are particularly inconsistent: Jio Fiber uses 192.168.29.1, Huawei consumer units use 192.168.3.1 or 192.168.8.1, and Xiaomi defaults to 192.168.31.1.

Find the real gateway IP on Windows:

1. Press Win + R, type cmd, press Enter.
2. Type ipconfig and press Enter.
3. Find your active adapter (Wireless LAN or Ethernet) and read Default Gateway.

Find the real gateway IP on macOS:

1. Open Terminal (Applications > Utilities > Terminal).
2. Run route get default | grep gateway.
3. The address after gateway: is your router’s IP.

Find the real gateway IP on Linux:

1. Open a terminal.
2. Run ip route | grep default.
3. The address after via is your router’s gateway IP.

Find the real gateway IP on Android:

1. Settings > Wi-Fi > tap your connected network.
2. Read Gateway (sometimes under Advanced).

Find the real gateway IP on iOS:

1. Settings > Wi-Fi > tap the (i) icon next to your network.
2. Read Router.

For a complete OS-by-OS walkthrough including command-line variants, see the find router IP address guide. For a concept-level explainer, see what is a default gateway.

Some brands also respond to a memorable hostname. If the numeric IP refuses to load, try the brand hostname:

Brand	Hostname	Numeric IP
TP-Link	tplinkwifi.net	192.168.0.1
TP-Link Deco	tplinkdeco.net	192.168.68.1
Netgear	routerlogin.net	192.168.1.1
Netgear Orbi	orbilogin.com	192.168.1.1
ASUS	router.asus.com	192.168.1.1
Linksys	myrouter.local	192.168.1.1
D-Link	dlinkrouter.local	192.168.0.1
Linksys (Smart Wi-Fi)	linksyssmartwifi.com	192.168.1.1

Confirm You Are on the Correct Network

Your browser can only reach the router admin panel when your device is connected to that router’s own local network. Sounds obvious. It is the second most common cause of login failure.

Common wrong-network situations:

• Laptop is on a mobile hotspot, not the home Wi-Fi.
• Phone auto-joined a neighbor’s open Wi-Fi.
• You have two routers (ISP modem-router plus a personal router) and you are on the wrong one. The admin IP belongs to one or the other, not both.
• Phone is using cellular data because Wi-Fi has weak signal in the room.
• Laptop is on a corporate VPN that has its own local subnet.

How to verify the connection: On Windows, click the Wi-Fi icon and confirm the SSID. On macOS, click the menu bar Wi-Fi icon. On phones, open Settings > Wi-Fi.

For the most reliable login experience, plug an Ethernet cable from a LAN port on the router (yellow ports, not the WAN port labelled Internet or marked blue) to your computer. Ethernet bypasses every wireless ambiguity and guarantees you are on the right network.

Disconnect VPN and Proxy Software

A VPN takes every outbound packet from your device and routes it through a remote server. That includes requests for local IP addresses like 192.168.1.1, which the VPN cannot find because the VPN server has no idea your router exists. The request times out.

Disconnect these before trying to login again:

• Commercial VPN apps: NordVPN, ExpressVPN, Surfshark, Mullvad, Proton VPN, IVPN.
• Self-hosted VPN clients: WireGuard, OpenVPN, Tailscale.
• System-wide proxies in Network preferences.
• Browser proxy extensions: SwitchyOmega, FoxyProxy, Privacy Badger (in some modes).
• Corporate clients: Cisco AnyConnect, Palo Alto GlobalProtect, Fortinet FortiClient, Citrix Gateway.

Disconnect the VPN entirely. Pausing it is not always enough because some clients keep the tunnel device active. Wait 5 seconds for normal routing to return, then try the router IP again.

Some VPN clients have a “split tunneling” or “allow local network access” option that lets local IPs bypass the tunnel. If you need the VPN running while you administer the router, enable that. The cleaner fix is to disconnect, work in the admin panel, and reconnect when you are done.

Fix Browser and HTTPS Issues

Modern browsers aggressively force HTTPS. Most router admin panels only speak HTTP. Result: a certificate error, a blank page, or an HSTS lockout.

Force HTTP explicitly. Type http://192.168.1.1 in the address bar with the http:// prefix. The browser cannot upgrade what you already typed (though some still try). Bookmark the URL once you get in.

Open a private/incognito window. Cmd/Ctrl + Shift + N (Chrome, Edge, Arc, Brave) or Cmd/Ctrl + Shift + P (Firefox). Incognito disables extensions and skips cached HSTS entries. If incognito works, the issue is in a normal browser profile.

Clear the HSTS cache for the router IP. Chrome: open chrome://net-internals/#hsts, scroll to “Delete domain security policies”, type your router IP (192.168.1.1), click Delete. Firefox: open the URL bar history, find a hit for the IP, right-click > Forget About This Site. This wipes the saved HTTPS enforcement for that address.

Clear the browser cache. Chrome: chrome://settings/clearBrowserData > Cached images and files > Clear. Firefox: Settings > Privacy & Security > Cookies and Site Data > Clear Data.

Try a different browser. If Chrome refuses, try Firefox. If Firefox refuses, try Safari (macOS) or Edge (Windows). Each browser handles HTTPS upgrade rules and cache invalidation differently. The router did not change; the browser did.

Check Firewall and Security Software

Firewalls on your computer can block requests to local IP addresses. Less common than browser or VPN problems, but it does happen with aggressive security suites.

Windows Firewall: Open Windows Security > Firewall & network protection. Confirm the network profile is set to “Private”. The “Public” profile restricts local network access. If the profile is correct, temporarily disable the firewall for testing.

macOS Firewall: System Settings > Network > Firewall. Disable temporarily. If the admin page loads with the firewall off, add an exception for your browser application before re-enabling.

Third-party suites: Norton, Kaspersky, Bitdefender, McAfee, Avast, ESET all bundle network protection features that filter or block local IPs. Look for “network inspection”, “safe browsing”, “web protection”, “intrusion detection”. Disable temporarily and retest.

Browser extensions blocking local access: uBlock Origin, AdBlock Plus, Privacy Badger, NoScript, and DNS-over-HTTPS extensions sometimes interfere with router pages. The fastest test is a private window (extensions disabled by default). If that fixes it, disable extensions one at a time in the normal profile to find the culprit.

Login Page Loads but Credentials Are Rejected

This means the network path is fine but you have the wrong username or password. Three scenarios:

You are using the wrong defaults. Defaults vary by brand. Read the label on the bottom or back of the router. The defaults are usually printed there. Common defaults:

• TP-Link: admin / admin
• ASUS: admin / admin
• Netgear: admin / password
• Linksys: admin / admin (some models leave username blank)
• D-Link: admin / admin or admin / blank
• Huawei: admin / admin
• Belkin: blank / blank or admin / blank
• Old Cisco: cisco / cisco or admin / cisco

For a full per-brand reference, see default router passwords.

Someone changed the password and you have it written down somewhere. Common locations: a sticky note near the router, the original setup app on a phone, an email from the installer, the find Wi-Fi password guide for OS-side stored credentials.

Someone changed the password and you have no record of it. Factory reset the router. Press and hold the reset button (a tiny recessed button on the back) for 10 to 15 seconds with a paperclip. The router reverts to the defaults printed on the label. See the reset router guide. Note: a reset wipes all configuration (Wi-Fi name, password, port forwards, parental controls, custom DNS), so use this only when other options fail. See also: recover router password.

Power Cycle the Router If Nothing Else Works

If you have confirmed the IP, verified the network, disconnected VPNs, tried multiple browsers, and the page still will not load on any device, the router itself is hung. Web server processes inside the router can crash due to memory leaks, overloaded connection tables, or firmware bugs.

Soft reboot:

1. Unplug the router power cable from the wall.
2. Wait 30 seconds. (Longer than you think. Capacitors hold charge.)
3. Plug back in.
4. Wait 2 to 3 minutes for the router to fully boot. Watch for steady power and internet LEDs.
5. Try the admin page again.

If a power cycle does not restore admin access, escalate:

• Connect a computer to the router by Ethernet (no Wi-Fi variables) and try again.
• Try a second device. If both fail, the router is at fault. If only one fails, the device is at fault.
• Factory reset the router (paperclip into the reset button, hold 10 to 15 seconds). See the reset router guide for the full procedure. A reset restores default IP, default credentials, and a clean configuration.

After a factory reset, the login page loads at the default IP and you sign in with the default credentials printed on the label. Reconfigure Wi-Fi, the admin password, and any custom settings.

Decision Tree: Which Fix to Try Next

Login page will not load
├── Did you check the gateway with ipconfig/ifconfig?
│   ├── No → Check it now. Use that exact IP.
│   └── Yes → Continue.
├── Is the device on the right SSID (not hotspot/neighbor/cellular)?
│   ├── No → Reconnect to the correct Wi-Fi or use Ethernet.
│   └── Yes → Continue.
├── Is a VPN, proxy, or corporate tunnel active?
│   ├── Yes → Disconnect entirely. Retry.
│   └── No → Continue.
├── Are you typing http:// explicitly?
│   ├── No → Add http:// prefix. Retry.
│   └── Yes → Continue.
├── Does a private/incognito window work?
│   ├── Yes → Cache or extension issue. Clear cache and HSTS.
│   └── No → Continue.
├── Does a different device (phone) work?
│   ├── Yes → Issue is on the original device. Check firewall.
│   └── No → Router is at fault.
├── Power cycle the router (unplug 30s).
│   ├── Loads → Done.
│   └── Still no → Factory reset (10-15s reset button hold).
└── Still no after reset → Hardware fault. Contact manufacturer.

Related Guides

• Router login basics
• Find your router IP address
• Reset router to factory defaults
• Recover a forgotten router password
• Default router passwords by brand
• Update router firmware
• What is a default gateway
• 192.168.1.1 details, 192.168.0.1 details, 10.0.0.1 details