You’re connected to the hotel, airport or café Wi-Fi. Your laptop says “No internet”, and the login page that should have popped up is nowhere to be seen. This is one of the most common captive portal problems, and it almost always has a simple cause: something stopped your device from being redirected to the portal.
Here is how to force a captive portal login page to open, starting with the quickest fixes. If you’re not sure what a captive portal is, read What Is a Captive Portal? first.
1. Visit a plain-HTTP website
Captive portals work by intercepting your first unencrypted web request and redirecting it to the login page. Modern browsers go straight to HTTPS, which the portal can’t redirect without triggering a security warning, so nothing happens.
Type one of these into your browser’s address bar, including http://:
http://neverssl.com, a site that exists for exactly this purposehttp://example.com- your device’s own connectivity check page (see the table below)
If the network has a portal, you should be redirected to it straight away.
2. Open the connectivity check page for your device
Every platform probes a known address to detect portals. Opening that address yourself often triggers the redirect:
| Device | Address to open |
|---|---|
| iPhone, iPad, Mac | http://captive.apple.com |
| Android, ChromeOS | http://connectivitycheck.gstatic.com/generate_204 |
| Windows | http://www.msftconnecttest.com/redirect |
| Firefox (any OS) | http://detectportal.firefox.com/canonical.html |
3. Turn off encrypted DNS, VPNs and Private Relay, temporarily
Portals often depend on answering your DNS lookups themselves. Anything that bypasses the network’s DNS can make the redirect fail silently:
- VPN apps: disconnect until you have logged in.
- Android Private DNS: Settings → Network & internet → Private DNS → Off or Automatic.
- iCloud Private Relay: Settings → Wi-Fi → the network → turn off Limit IP Address Tracking / Private Relay for this network.
- Browser “Secure DNS” / DNS over HTTPS in Chrome, Edge or Firefox: switch it off or set it to use the current provider.
- Custom DNS (for example 1.1.1.1 or 8.8.8.8 set manually): switch back to automatic (DHCP).
Turn them back on once you’re online.
4. Open the gateway address directly
Some portals live on the router itself. Find your default gateway and open it in the browser:
- Windows: run
ipconfigand look for Default Gateway. - Mac: System Settings → Wi-Fi → Details → TCP/IP → Router.
- iPhone / Android: tap the network’s info icon and look for Router or Gateway.
- Linux:
ip route | grep default.
Then browse to http://<that address>, for example http://192.168.1.1 or http://10.0.0.1.
5. Forget the network and reconnect
Forgetting the network clears cached state and makes your device run its portal detection again. On some devices, also turn Wi-Fi off and on before rejoining.
6. Disable MAC randomisation for that network
Phones and laptops now use a random, private MAC address per network. Portals often identify devices by MAC, so a new address can look like a new, unauthorised device:
- iPhone: Settings → Wi-Fi → the network → Private Wi-Fi Address → Off.
- Android: Wi-Fi → the network → Privacy → Use device MAC.
- Windows: Wi-Fi properties → Random hardware addresses → Off.
7. Try a different browser or a private window
Cached HTTPS redirects (HSTS), extensions and ad blockers can all block a portal. A private window with extensions disabled, or a different browser, rules them out.
8. Check you’re on the right network
Hotels and airports often broadcast several similarly named networks, and attackers sometimes add their own. Ask staff which network is the official one. Read Is a Captive Portal Login Safe? before entering personal details on a portal you’re unsure about.
Still stuck?
If none of this works, the portal itself may be broken or overloaded, which is common at busy airports and conference venues. Asking staff, or trying again in a few minutes, is often the only fix.
On a phone? Our Android and iPhone captive portal login guide covers the mobile side in more detail. If a VPN or security tool keeps saying “captive portal detected”, see Understanding the “Captive Portal Detected” Error.
For network owners: make your portal easy to reach
If guests regularly can’t find your login page, a few changes on the network side help a lot:
- Advertise the portal with DHCP option 114 (RFC 8910) so modern devices open it without guessing.
- Allow-list the connectivity check domains in your walled garden only if your setup needs it. Check your controller’s documentation.
- Serve the portal over HTTPS with a valid certificate once the device has reached it, so guests don’t see security warnings.
- Keep sessions long enough that returning guests don’t have to log in on every visit.