Quick Answer for the Impatient
Clear your browser cache and cookies for the router's IP, then reopen the login page. If that fails, use an incognito/private window or a different browser. Still stuck? Power-cycle the router and try again. Last resort: 30-30-30 factory reset.
Why This Happens
You changed the router admin password, which sounds straightforward, but older browsers love caching login pages. They'll keep serving the old login form even though the password on the router is different. I've seen this on Chrome, Edge, and Safari — it's not a router issue nine times out of ten. Sometimes it's a DNS cache problem, or you're hitting a stale IP if your router changed its subnet after a firmware update. Let's rule out the easy stuff first.
Step-by-Step Fix
- Hard-refresh the login page. On Windows/Linux: Ctrl+F5. On Mac: Cmd+Shift+R. This forces the browser to fetch the page fresh from the router, not from cache.
- Clear browser cache and cookies for the router IP only. In Chrome: click the lock icon next to the address bar → "Cookies" → delete all cookies for that domain. Then go to Settings → Privacy and Security → Clear browsing data → Advanced → select "Cookies and other site data" and "Cached images and files" → set time range to "All time" → clear. For Firefox: right-click the page → "View Page Info" → "Security" → "Clear Cookies and Site Data".
- Use an incognito or private window. This sidesteps cache and extensions. Try logging in there. If it works, the problem is 100% cache in your normal browser.
- Try a different browser or device. Hop on your phone via Wi-Fi, open a private tab, and type the router's IP. If that works, you know it's your main browser.
- Verify the router's IP address. Open Command Prompt (Windows) or Terminal (Mac/Linux) and type
ipconfig(Windows) orifconfig(Mac/Linux). Look for your default gateway — that's your router's IP. Common ones:192.168.1.1,192.168.0.1,10.0.0.1. Your router might have changed it after a firmware update, even if you didn't touch it. - Power-cycle the router. Unplug it for 30 seconds, plug it back in. Wait 2 minutes for it to fully boot. Then try again. This clears temporary glitches where the router's web server hangs.
- Try HTTP instead of HTTPS. Some older routers don't handle HTTPS redirects well. Type
http://192.168.1.1explicitly.
If the Main Fix Fails — Factory Reset
If none of that works, your router's web interface might be corrupted or the password change didn't save correctly. You'll need a factory reset. Here's the standard 30-30-30 method that works on most consumer routers (Netgear, TP-Link, Asus, Linksys):
- With the router powered on, press and hold the reset button on the back with a paperclip.
- Keep holding it for 30 seconds.
- While still holding the button, unplug the router from power.
- Keep holding the button for another 30 seconds.
- Plug the router back in while still holding the button for 30 more seconds.
- Release the button. The router should now have factory settings — username: admin, password: admin (or password).
After resetting, you'll have to reconfigure Wi-Fi name/password and any custom settings. Write those down first if you can.
Prevention Tip
Always change your router password from a device that's connected via Ethernet cable, not Wi-Fi. Wi-Fi can drop mid-change, which corrupts the password hash. Also, use a password manager to store the new password — I've seen too many people lock themselves out because they forgot the new one. And for the love of all things IT, write down the default gateway IP before you start messing with settings. Stick a Post-It on the router if you have to.
"I ran into this three times last month on client sites. 90% of the time it's browser cache. Don't factory reset until you've tried a private window first." — Marcus, Sysadmin