You have established a connection with the Wi-Fi at a hotel, airport, or café. However, your computer displays “No internet”, and the expected login page does not appear. This is a frequent issue involving captive portals, usually caused by a single factor: your device failed to get redirected to the portal.
Follow these steps to compel a captive portal login page to display, beginning with the fastest solutions. Should you be uncertain about the definition of a captive portal, consult What Is a Captive Portal? initially.
1. Visit a plain-HTTP website
Captive portals operate by capturing your initial unencrypted web request and sending you to the login page. Current browsers navigate directly to HTTPS, meaning the portal cannot redirect that traffic without causing a security alert, resulting in no action.
Enter one of the following into your browser’s address bar, which includes http://:
http://neverssl.com, a location designed specifically for this reasonhttp://example.com- the connectivity verification page provided by your device (refer to the table below)
Should the network include a portal, redirection should occur immediately.
2. Open the connectivity check page for your device
Each operating system checks a specific address to identify portals. Manually visiting that address frequently initiates the redirection process:
| 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
These systems frequently rely on handling your DNS queries directly. Using services that skip the network’s DNS server can cause the redirection to fail without notice:
- VPN applications: sever your connection until you are authenticated.
- Private DNS on Android: Settings → Network & internet → Private DNS → Off or Automatic.
- Private Relay on iCloud: Settings → Wi-Fi → the network → disable Limit IP Address Tracking or Private Relay for that network.
- “Secure DNS” or DNS over HTTPS in browsers: disable this feature in Chrome, Edge, or Firefox, or configure it to use the current provider.
- Manually configured DNS (such as 1.1.1.1 or 8.8.8.8 entered by hand): revert to automatic (DHCP) settings.
Reactivate these features after gaining internet access.
4. Open the gateway address directly
Certain portals reside within the router hardware. Locate your default gateway and access it via the browser:
- Windows: execute
ipconfigto locate the Default Gateway entry. - Mac: Navigate through System Settings → Wi-Fi → Details → TCP/IP → Router.
- iPhone / Android: Press the network details icon to find Router or Gateway information.
- Linux:
ip route | grep default.
Next, navigate to http://<that address>, such as http://192.168.1.1 or http://10.0.0.1.
5. Forget the network and reconnect
Removing the network from saved connections wipes cached data and forces your device to detect the portal anew. For certain hardware, switch Wi-Fi off and then back on prior to reconnecting.
6. Disable MAC randomisation for that network
Smartphones and computers use a randomized, private MAC address for each network. Since portals frequently recognize devices via their MAC address, a fresh address may appear as an unauthorized new unit:
- iPhone: Go to Settings → Wi-Fi → the network → set Private Wi-Fi Address to Off.
- Android: Select Wi-Fi → the network → Privacy → choose Use device MAC.
- Windows: Access Wi-Fi properties → disable Random hardware addresses → set to Off.
7. Try a different browser or a private window
Stored HTTPS redirect data (HSTS), installed extensions, and content filters may prevent the portal from loading. Using an incognito window without extensions, or switching to another browser, eliminates these issues.
8. Check you’re on the right network
Establishments like hotels and airports frequently transmit multiple networks with similar names, while malicious actors may introduce their own. Inquire with staff to identify the legitimate network. Consult Check if Captive Portal Login is Safe? prior to inputting personal information on an uncertain portal.
Still stuck?
If these steps fail, the captive portal could be malfunctioning or congested, a frequent occurrence at crowded airports and convention centers. Contacting support staff, or waiting briefly before attempting again, is usually the only solution.
Using a smartphone? Our Android and iPhone captive portal login guide covers the mobile aspect in more depth. Should your VPN or security tool keep reporting “captive portal detected”, consult Understanding the “Captive Portal Detected” Error.
For network owners: make your portal easy to reach
When visitors frequently cannot locate your login page, several adjustments on the network side assist significantly:
- Broadcast the captive portal using DHCP option 114 (RFC 8910) enabling modern devices to access it automatically rather than searching.
- Whitelist the connectivity check domains within your walled garden solely when required by your configuration. Review your controller’s documentation for specifics.
- Deliver the captive portal via HTTPS with a valid certificate after the device arrives there, ensuring visitors do not encounter security alerts.
- Maintain session duration sufficient so returning visitors are not required to authenticate for each entry.