Hotel & Café WiFi Won't Connect? The Captive-Portal Fix

What a captive portal actually is

A captive portal is the login or "accept the terms" web page that hotel, café, airport, and coworking WiFi force you through before they'll give you real internet. The technical reality is sneakier than it looks: your device does join the network and does get an IP address — but every packet you send is held "captive" and silently redirected to that login page until you complete it. That's why your laptop shows full WiFi bars yet nothing actually loads.

When the portal works, it's invisible: you connect, a page pops up, you tap "Connect," and you're online. When it breaks, you get the maddening modern symptom — "Connected, no internet" — with no obvious way forward. This is the single most common WiFi complaint we hear from travelers, and the cause is almost never the router. It's a collision between how captive portals are built and how today's devices browse.

Why the login page won't load — the real cause

Here's the part almost no troubleshooting article explains. A captive portal works by intercepting an unencrypted web request and redirecting it to the login page. For years that was easy, because the first thing your device loaded was an ordinary http:// page. The network would catch that request and swap in the portal.

Then the web went encrypted. Today your phone and laptop default to https:// for nearly everything, and an HTTPS connection is, by design, tamper-proof — the network cannot intercept or redirect it without triggering a scary certificate-error warning. So when your device quietly tries to reach an https address in the background, the portal can't hijack it, the login page never appears, and you're stuck connected-but-offline.

Several things make this worse abroad:

• DNS-over-HTTPS / private DNS. If your browser or phone is set to encrypted DNS, the portal can't perform the redirect it relies on.
• An always-on VPN. A VPN tries to build its tunnel before you've passed the portal, so it can't connect and it hides the portal — a double block. (We cover this in depth in why your VPN won't connect abroad.)
• Cached redirects. Your browser remembers that a site uses HTTPS (HSTS), so it refuses to load the http version that would have triggered the portal.
• Auto-connect. Your device rejoins a network it "knows," skipping the portal check entirely.

Understand that one mechanism and the fixes below all make sense: every one of them is just a way to force an unencrypted request the portal can catch.

How to force the login page to appear (works on any device)

This is the master trick. Open your browser and type a deliberately plain http:// address — one that has no HTTPS version to redirect to:

• http://neverssl.com — built for exactly this purpose; it never upgrades to https.
• http://example.com or http://captive.apple.com as backups.

Do not type a Google search, a bare domain like "facebook.com," or anything with https — your browser will silently upgrade it to HTTPS and the portal won't appear. The unencrypted request to neverssl gives the network something it's allowed to intercept, and the login page pops right up. This one move solves the majority of cases. Below are the device-specific steps when it doesn't.

Step-by-step: Windows

1. Click the network icon in the taskbar and confirm you're connected to the right WiFi (not a similarly named decoy).
2. Open a browser and go to http://neverssl.com to trigger the portal.
3. If nothing appears, forget the network: Settings › Network & Internet › WiFi › Manage known networks › Forget — then rejoin.
4. Disable any VPN and turn off "Private DNS" / DNS-over-HTTPS in your browser settings.
5. Renew your IP: open Command Prompt and run ipconfig /release then ipconfig /renew, followed by ipconfig /flushdns.
6. If the portal still won't show, set DNS to automatic (DHCP) — a hard-coded DNS like 8.8.8.8 can stop the redirect cold.

Persistent Windows-only WiFi failures (driver issues, a stuck adapter, a corrupted network stack) are a quick fix over a remote session — see Windows support.

Step-by-step: Mac

1. macOS usually pops the captive-portal window automatically. If it didn't, turn WiFi off and back on from the menu bar.
2. Open Safari and visit http://captive.apple.com — it should immediately bounce you to the login page.
3. If you see "Success" instead of a portal, you may already be online; if not, forget the network in System Settings › Wi-Fi › (network) › Forget, then rejoin.
4. Disable any VPN and check System Settings › Network › DNS for a manual entry — remove it so DHCP assigns the portal's DNS.
5. Hold Option and click the WiFi icon to see the real signal and IP; "self-assigned IP" means the network never finished setup — forget and rejoin.

MacBook-specific WiFi quirks — a flaky adapter, a bad network location profile — are exactly what remote MacBook support resolves fast.

Step-by-step: iPhone & Android

Step	iPhone	Android
Trigger portal	Join WiFi; the login sheet usually auto-opens. If not, open Safari to http://captive.apple.com	Join WiFi; tap the "Sign in to network" notification, or open Chrome to http://neverssl.com
Turn off mobile data	Settings › Cellular › off (so the phone uses WiFi for the portal check)	Quick settings › toggle Mobile data off
Disable private DNS	Settings › WiFi › (i) › turn off "Limit IP Address Tracking" / private relay	Settings › Network › Private DNS › Off
Forget & rejoin	Settings › WiFi › (i) › Forget This Network	Settings › WiFi › long-press › Forget
Kill the VPN	Settings › VPN › off before connecting	Settings › VPN › disconnect before connecting

The mobile-data step matters more than people expect: if your phone has a cellular signal, it may run its "is there internet?" check over mobile data and decide the WiFi is fine without ever opening the portal. Turning cellular off forces it to deal with the WiFi.

If it still won't connect

You've forced the portal, killed the VPN, fixed DNS, and you're still offline. At that point it's one of a handful of deeper causes:

• The portal itself is broken (the hotel's billing server is down). Ask the front desk to reset your device's access or give you a fresh voucher — sometimes the fix is entirely on their end.
• MAC-address limits. Some networks bind one login to one device; your laptop may be locked out because your phone already claimed the slot. Forget on one device.
• A firewall or security suite on your laptop is blocking the portal's scripts. Temporarily disable it, log in, re-enable.
• Malware or a hijacked DNS redirecting your traffic — more common than you'd think on devices that picked something up abroad. If pages load to the wrong places, get a malware check.

This is everyday work for our WiFi and network team, and we do it for digital nomads, Airbnb hosts setting up guest networks, and remote workers across all 130+ cities → we cover. Connection problems are why a remote service exists — we meet you wherever, and whenever, you're stuck.