Hotel WiFi Captive Portal Stuck in a Login Loop — Here's the Actual Fix
A captive portal stuck in a login loop is almost always one of four specific causes: a stale DNS cache still pointing your browser at the wrong server, cookies from a previous visit confusing the portal's session tracking, your browser or an extension actively blocking the redirect it needs to load the page, or your device's randomized MAC address making the network treat you as a brand-new, unauthenticated device every time you reconnect. Each has a distinct fix, and none of them require rebooting the router or calling the front desk. This page covers this one narrow failure mode specifically — for wifi problems more broadly, see our wifi abroad troubleshooting guide.
What this guide covers
- What a Captive Portal Actually Does (and Why It's Fragile)
- Stale DNS Cache Pointing You at the Wrong Server
- Old Cookies Confusing the Portal's Session Tracking
- Your Browser or an Extension Actively Blocking the Redirect
- MAC Address Randomization Making You a "New" Device Every Time
- Stop Fighting the Same Login Screen Every Ten Minutes
What a Captive Portal Actually Does (and Why It's Fragile)
A captive portal works by intercepting your device's very first web request after joining the network and redirecting it to a login or terms-acceptance page, then releasing your traffic to the real internet once you've authenticated. It relies on your device's connection-testing behavior (Apple's Captive Network Assistant, Android's connectivity check, Windows' NCSI) triggering that redirect cleanly exactly once.
Because it's essentially a controlled hijack of your first request, anything that interferes with that single moment — a cached DNS answer, an old cookie, a browser extension, or ad-blocker — breaks the handoff and leaves you stuck reloading a page that never fully loads or keeps bouncing you back to the start.
Stale DNS Cache Pointing You at the Wrong Server
If you connected to this same hotel's wifi on a previous stay, or your device cached a DNS response from a different network entirely, your browser may be trying to resolve the portal's address using outdated information, which causes it to either hang indefinitely or load a broken page. Flushing your device's DNS cache (on Mac: dscacheutil -flushcache; on Windows: ipconfig /flushdns) forces a fresh lookup and is often the single fastest fix for a loop that never resolves.
If flushing DNS doesn't help and you're also seeing broader connectivity problems beyond just the portal page, our wifi abroad troubleshooting guide covers the wider set of network diagnostics worth running.
Old Cookies Confusing the Portal's Session Tracking
Many captive portals set a session cookie to track whether you've already authenticated, and if that cookie is stale, corrupted, or was set during a partial/failed login attempt, the portal can get confused about your session state and loop you back to the start instead of granting access. This is especially common if you tried logging in multiple times in a row after an earlier failure — each attempt can leave behind conflicting cookie data.
Clearing cookies specifically for the portal's domain (not your entire browser history) usually resolves this without losing your other saved logins. If you're not sure which domain the portal is using, opening it in a private/incognito window as a test — which starts with a clean cookie slate — quickly confirms whether cookies are the culprit.
Your Browser or an Extension Actively Blocking the Redirect
Ad blockers, privacy extensions, and "HTTPS-only" or forced-encryption browser settings can all interfere with the specific way a captive portal needs to intercept an unencrypted first request to inject its redirect. If your browser is configured to upgrade every connection to HTTPS automatically, or an extension is blocking third-party redirects by design, the captive portal literally cannot complete its handoff, and you'll see either an endless spinner or a security warning instead of the login page.
The fastest diagnostic is trying the exact same network in a different browser with no extensions installed, or in your phone's browser instead of your laptop's. If it works cleanly there, the cause is confirmed to be a browser-side block rather than a network problem, and we can help you adjust the specific setting without leaving your browser generally less secure.
MAC Address Randomization Making You a "New" Device Every Time
Modern phones and some laptops randomize their MAC address by default for privacy each time they join a new network, or in some cases each time they reconnect to the same network. Captive portals typically track authenticated devices by MAC address, so if yours is randomizing, the network genuinely sees a brand-new, unauthenticated device every time your phone reconnects — even though it's the same device you already logged in with ten minutes ago — forcing you through the login screen repeatedly.
The fix is disabling private/randomized address specifically for that one wifi network (both iOS and Android allow a per-network setting for this), which lets the portal recognize you as the same authenticated device across reconnects without weakening your privacy on every other network you join.
Stop Fighting the Same Login Screen Every Ten Minutes
We'll pinpoint whether it's DNS, cookies, your browser, or MAC randomization and get you online in one session.
Book a remote fix — $149.99Frequently asked questions
Why does the hotel wifi login page keep reloading without ever finishing?
This is usually a stale DNS cache or a cookie conflict interfering with the portal's one-time redirect handoff. Flushing DNS and clearing cookies for that specific domain resolves it in most cases.
Why does my phone get logged out of hotel wifi every time I lock the screen?
This is often MAC address randomization — your phone presents a new, unrecognized address each time it reconnects. Disabling private address for that one network keeps you recognized as the same device.
Is this the same issue as general slow or dropped wifi abroad?
No, it's a narrower, specific failure in the captive portal's login handoff, distinct from general connectivity issues. For broader wifi troubleshooting, see our wifi abroad guide.
Can an ad blocker really cause a captive portal to fail?
Yes. Ad blockers and privacy extensions can block the specific redirect a captive portal needs to inject its login page, especially combined with forced-HTTPS browser settings. Testing in a clean browser with no extensions quickly confirms this.
Should I forget the network and rejoin from scratch?
It can help since it clears some cached state, but it won't fix a MAC randomization or cookie issue on its own. We usually address the specific cause directly rather than relying on a full reset.
Is it safe to log into a captive portal with my email or personal details?
Most legitimate hotel and airport portals only ask for a room number or basic details, not sensitive credentials — treat any portal asking for a password you use elsewhere as suspicious. If you're also concerned about the network's general safety, see our malware on hotel wifi guide.