How to troubleshoot and fix Wi-Fi authentication failures on a captive portal (hotel, café, or airport network)

Network & Internet KB-421

Summary

This guide helps you troubleshoot and resolve: How to troubleshoot and fix Wi-Fi authentication failures on a captive portal (hotel, café, or airport network). Follow the steps below to fix the issue.

Quick Tip: Need immediate assistance? 💻 Open a Ticket

Common Causes

Captive portals are the splash pages you see at hotels, cafés, airports, and conference venues that require you to sign in, accept terms, or enter a room number before you can access the internet. Occasionally your device fails to load that sign-in page, gets stuck on "connecting," or authenticates but still has no internet access. This guide walks you through diagnosing and resolving the most common causes of captive portal authentication failures on Windows, macOS, iOS, and Android devices.

Quick Fix Steps

Before diving into detailed troubleshooting, try these steps in order. Most captive portal issues are resolved within the first few attempts.

Disconnect from the Wi-Fi network and reconnect.
Toggle Airplane Mode on for 10 seconds, then off again.
Open a browser and manually navigate to a non-secure site such as http://neverssl.com or http://example.com to force the captive portal redirect.
Clear your browser cookies and cache, then reload the sign-in page.
Restart your device completely (not just a screen lock).

If you have previously accepted the venue's terms on the same network, your device may skip the captive portal entirely. Disconnecting and "forgetting" the network forces a fresh sign-in prompt.

Detailed Instructions

Step 1: Confirm the Network Requires a Captive Portal

Not every public Wi-Fi network uses a captive portal. Some are simply open networks with no authentication, while others require a username and password supplied by the venue (such as a hotel room number or conference code). If you connected successfully but have no internet access, the network almost certainly uses a captive portal.

Signs you are on a captive portal network:

Wi-Fi shows Connected but browsers display "No Internet" or a venue-branded splash page.
A notification appears on your device saying Sign in to network or Tap to connect.
Your device automatically opens a browser window when you connect.

Step 2: Force the Captive Portal to Load

Modern operating systems detect captive portals and present a sign-in window automatically, but this detection can fail, especially after a previous session or when using certain browsers. Forcing a redirect is the most reliable fix.

Windows 10 and 11

Click the Wi-Fi icon in the system tray.
Confirm you are Connected to the venue network.
Open Microsoft Edge or Chrome.
Type http://neverssl.com into the address bar and press Enter.
If no splash page appears, open Settings > Network & internet > Wi-Fi, click the connected network, and ensure Connect automatically is toggled off. Disconnect, then reconnect.

macOS (Ventura and Sonoma)

Click the Wi-Fi icon in the menu bar and confirm you are connected.
Open Safari.
Enter http://neverssl.com in the address bar and press Return.
If Safari does not redirect, open System Settings > Wi-Fi, click Details next to the network, then click Forget This Network. Reconnect and try again.

iOS and iPadOS

Open Settings > Wi-Fi and tap the (i) icon next to the connected network.
Tap Forget This Network, then rejoin it.
A Sign In notification should appear. Tap it to open the captive portal.
If the notification does not appear, open Safari and visit http://neverssl.com.

Android 12 and later

Open Settings > Network & internet > Internet.
Tap the connected network, then tap Forget.
Reconnect to the network and look for a Sign in notification in the status bar.
If no notification appears, open Chrome and navigate to http://neverssl.com.

Step 3: Address Browser-Specific Issues

Some browsers handle captive portals poorly, particularly when HTTPS-only mode is enabled or when aggressive privacy settings block redirects.

Disable HTTPS-Only mode: In Chrome, Edge, Firefox, and Safari, look for an HTTPS-Only or Always use secure connections toggle and switch it off temporarily.
Try a different browser: If Safari or Chrome fails, try Firefox, or vice versa.
Disable extensions and ad blockers: Privacy extensions such as uBlock Origin, Privacy Badger, or HTTPS Everywhere can prevent captive portal scripts from loading.
Disable VPN apps: Active VPN connections route traffic away from the local network and prevent the captive portal from detecting your session. Disconnect any VPN before authenticating.

Never enter personal information, payment details, or passwords into a captive portal page unless you have verified the venue's network name with staff. Attackers sometimes set up rogue access points with names like "Free_Airport_WiFi" to harvest credentials.

Step 4: Clear Stored Credentials and Cached Data

If you have connected to the same network before, your device may be reusing expired session data.

Clear Browser Data

Open your browser's settings or history menu.
Select Clear browsing data.
Tick Cookies and other site data and Cached images and files.
Choose All time as the time range and confirm.

Reset Network Settings

If clearing browser data does not help, reset your device's network stack. This removes all saved Wi-Fi passwords, so have them handy.

Windows: Settings > Network & internet > Status > Network reset.
macOS: Removing the network from System Settings > Wi-Fi is usually sufficient.
iOS: Settings > General > Transfer or Reset iPhone > Reset > Reset Network Settings.
Android: Settings > System > Reset options > Reset Wi-Fi, mobile & Bluetooth.

Troubleshooting

The Captive Portal Loads But Sign-In Fails

If the splash page appears but your credentials are rejected:

Confirm the username and password with venue staff. Hotel networks often use your room number and surname, while conference networks may require a code printed on your badge.
Check that your device's date and time are set automatically. Incorrect time settings cause authentication tokens to fail.
Disable any pop-up blockers that might prevent the portal from submitting the form.
Try signing in using a different device. If the second device works, the issue is with your device's configuration rather than the network.

Authentication Succeeds But Internet Still Does Not Work

This usually indicates a DNS or routing issue after authentication.

Open Settings on your device and toggle Wi-Fi off and on again to renew the DHCP lease.
Manually set your DNS to a public resolver such as 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google) to bypass any broken local DNS.
Forget the network and reconnect, accepting the captive portal terms again from scratch.
Restart your device to clear any stale routing or session information.
If other devices on the same network work normally, the issue is specific to your device and may require a full network settings reset.

Captive Portal Does Not Appear at All

If no splash page loads even after trying the steps above:

Confirm with venue staff that the Wi-Fi network you are connected to is the correct one. Rogue or neighbouring networks can have similar names.
Move closer to the access point. Weak signals can prevent the captive portal detection from completing.
Check whether your device has a static IP address configured. Captive portals require DHCP. Switch to automatic (DHCP) addressing.
Try connecting from a different device to determine whether the issue is with the network or your device.

If you have tried all of the above and the captive portal still will not load, contact the venue's front desk or IT support. They can verify that the access point is functioning, reset your session on the authentication server, or provide an alternative network.

Still Having Issues?

Need more help? If the issue persists after trying these steps, please open a support ticket and our team will assist you.

💻 Open a Ticket