Router Login Not Working: How to Fix It

A router login page that refuses to load is one of the most frustrating networking problems because it locks you out of every setting. You cannot change your Wi-Fi password, update firmware, or troubleshoot connection issues without admin panel access. The causes range from simple typos to VPN conflicts, and most can be fixed in under five minutes.

Verify You Are Using the Correct IP Address

Your router’s admin panel lives at a specific local IP address, and typing the wrong one is the single most common reason the login page fails to load. Most routers use 192.168.1.1, but many use 192.168.0.1, 10.0.0.1, or a brand-specific address.

Find your actual router IP on Windows:

1. Press Win + R, type cmd, press Enter.
2. Type ipconfig and press Enter.
3. Look for “Default Gateway” under your active network adapter. That is your router’s IP.

Find your actual router IP on macOS:

1. Open Terminal (Applications > Utilities > Terminal).
2. Type route get default | grep gateway and press Enter.
3. The gateway address is your router IP.

Find your actual router IP on Linux:

1. Open a terminal window.
2. Type ip route | grep default and press Enter.
3. The IP after “via” is your router’s gateway address.

For a complete walkthrough on every platform including mobile, see the find router IP address guide.

Some brands also respond to custom hostnames. ASUS routers accept router.asus.com, Netgear responds to routerlogin.net, TP-Link uses tplinkwifi.net, and Linksys uses myrouter.local. Try these if the numeric IP does not resolve.

Confirm You Are on the Correct Network

Your browser can only reach the router login page when your device is on the router’s own local network. This sounds obvious, but several situations cause you to be on the wrong network without realizing it.

Common wrong-network scenarios:

• Your laptop is connected to a mobile hotspot instead of your home Wi-Fi.
• You are connected to a neighbor’s open network that your device auto-joined.
• You have multiple routers (e.g., ISP modem-router plus a personal router) and are connected to the wrong one.
• Your phone is using cellular data instead of Wi-Fi.

How to verify: On Windows, click the Wi-Fi icon in the taskbar and confirm the network name matches your router’s SSID. On macOS, click the Wi-Fi icon in the menu bar. On a phone, check Settings > Wi-Fi.

For the most reliable connection, plug an Ethernet cable directly from your computer to one of the router’s LAN ports (not the WAN/Internet port). Ethernet bypasses all wireless issues and guarantees you are on the correct network.

Disconnect VPN and Proxy Software

VPN software is one of the most overlooked causes of router login failures. A VPN routes your internet traffic through a remote server, which means requests to local IP addresses like 192.168.1.1 never reach your router. They get sent to the VPN tunnel instead.

Disconnect these before attempting router login:

• VPN apps: NordVPN, ExpressVPN, Surfshark, Mullvad, Proton VPN, WireGuard
• System-wide proxies configured in your OS network settings
• Browser proxy extensions like proxy switchers or privacy tools
• Corporate VPN clients like Cisco AnyConnect, GlobalProtect, or Fortinet

After disconnecting the VPN, wait a few seconds for your network routing to revert to normal, then try the router IP again. Some VPN clients have a “split tunneling” feature that allows local network access while the VPN is active, but the simplest fix is to disconnect entirely.

Fix Browser and HTTPS Issues

Your browser itself can prevent the router login page from loading. Modern browsers aggressively enforce HTTPS, and since most router admin panels only support HTTP, this creates certificate errors and blank pages.

Force HTTP instead of HTTPS. Type http://192.168.1.1 in the address bar with the http:// prefix explicitly included. Many browsers auto-upgrade URLs to HTTPS, which causes a certificate error because routers do not have valid SSL certificates.

Try a private/incognito window. Press Ctrl + Shift + N (Chrome/Edge) or Ctrl + Shift + P (Firefox). Incognito mode disables extensions and uses a clean cache, eliminating two common sources of interference.

Clear your browser cache. Cached redirects and HSTS entries can force HTTPS even when you type HTTP. In Chrome, go to chrome://settings/clearBrowserData, select “Cached images and files,” and clear. In Firefox, go to Settings > Privacy & Security > Cookies and Site Data > Clear Data.

Delete HSTS entries for the router IP. In Chrome, go to chrome://net-internals/#hsts, scroll to “Delete domain security policies,” type your router’s IP address, and click Delete. This removes any saved HTTPS enforcement for that address.

Try a different browser. If Chrome does not work, try Firefox, Edge, or Safari. Each browser handles HTTPS enforcement and caching differently. If one browser has a corrupted cache entry, another browser will load the page cleanly.

Check Firewall and Security Software

Firewall software on your computer can block access to local IP addresses. This is less common than browser or VPN issues, but it happens with aggressive security suites.

Windows Firewall: Open Windows Security > Firewall & network protection. Check that your network is set to “Private network.” Public network profiles restrict local network access. If switching to Private does not help, temporarily disable the firewall for testing.

macOS Firewall: Go to System Settings > Network > Firewall. Try turning it off temporarily to test. If the login page loads with the firewall off, add an exception for your browser application.

Third-party security suites: Norton, Kaspersky, Bitdefender, and McAfee all include network protection features that may block or filter requests to local IPs. Check the security software’s settings for “network inspection,” “safe browsing,” or “web protection” features. Temporarily disable them to test.

Browser extensions blocking local access: Ad blockers (uBlock Origin, AdBlock Plus), privacy extensions (Privacy Badger, NoScript), and security extensions can interfere with router pages. Disable all extensions or use incognito mode, which disables extensions by default.

Reboot the Router If Nothing Else Works

If you have confirmed the correct IP, verified your network connection, disconnected VPNs, and tried multiple browsers, the router itself may be unresponsive. Your router’s web server can hang due to firmware bugs, memory issues, or overloaded connection tables.

Soft reboot steps:

1. Unplug the router’s power cable from the wall outlet.
2. Wait 30 seconds. This clears volatile memory.
3. Plug the power cable back in.
4. Wait 2-3 minutes for the router to fully boot. Watch for the power and internet LEDs to stabilize.
5. Try the login page again.

If a reboot does not restore access, try connecting via Ethernet and using a different device. If the admin panel is still unreachable on any device, the router may need a factory reset. Hold the reset button for 10-15 seconds with a paperclip. This restores all default settings, including the admin panel. See the reset router guide for full instructions.

After a factory reset, the login page will load at the default IP address, and you can log in with the default credentials printed on the router label.