How to Fix Hotel and Public WiFi Login Pages Not Loading (Captive Portal Fix)

You join the hotel WiFi, your device shows “connected,” and then… nothing. No login page. No password prompt. Just a browser that spins forever or throws a “no internet connection” error. This is a captive portal failure — one of the most common and most fixable public WiFi problems.

Captive portals are the web pages that hotels, airports, coffee shops, and campuses use to authenticate users before granting internet access. When they fail to load, the fix is almost always on your device, not the network. Here’s how to solve it.

What Is a Captive Portal and Why Does It Break?

A captive portal works by intercepting all outbound web traffic and redirecting it to a login page. Your device connects to the WiFi and receives a local IP address, but internet access is blocked until you authenticate. The portal page appears automatically — in theory.

In practice, several common device settings prevent that automatic redirect from working:

VPN apps encrypt traffic before it leaves your device, so the network can’t intercept and redirect it.
Custom DNS servers (like 1.1.1.1 or 8.8.8.8) bypass the captive portal’s DNS hijacking mechanism.
HTTPS-only browser settings block the unencrypted redirect that captive portals depend on.
Browser cache tricks the browser into thinking it has a cached version of captive.apple.com or the portal URL, skipping the live redirect.
Failed DHCP means your device has a self-assigned 169.254.x.x IP address instead of a valid one from the network, making any redirect impossible.

Fix 1: Disconnect Your VPN First

This solves the problem for the majority of users. If you have a VPN app — ExpressVPN, NordVPN, ProtonVPN, or even your work VPN — it must be fully disconnected before you can authenticate with a captive portal. The VPN tunnel encrypts all traffic, including the HTTP redirect that the portal sends, so the login page can never reach your browser.

Steps: Open your VPN app and toggle it off. Disconnect from the WiFi network, then reconnect. The captive portal page should appear within 10–20 seconds. Once you’ve logged in and have full internet access, you can reconnect your VPN.

The same applies to always-on security apps like Norton WiFi Privacy, Bitdefender VPN, or any MDM (mobile device management) profile that routes traffic through a corporate proxy. Temporarily disable them before connecting.

Fix 2: Force-Open the Portal Page Manually

If the portal redirect doesn’t trigger automatically, you can force it by navigating to a plain HTTP URL. Because captive portals work by intercepting unencrypted HTTP traffic, visiting any HTTP address will trigger the redirect — HTTPS sites like Google won’t work because the portal can’t intercept encrypted connections.

Try these URLs directly in your browser address bar:

http://neverssl.com — a site specifically designed to stay HTTP-only for exactly this purpose
http://captive.apple.com — Apple’s captive portal detection URL (works on all browsers, not just Apple devices)
http://connectivitycheck.gstatic.com/generate_204 — Google’s captive portal check used by Android
Your router’s local IP in plain HTTP, e.g., http://192.168.1.1

Make sure you type the full http:// prefix. Browsers default to HTTPS if you omit it, which defeats the purpose.

Fix 3: Use a Private / Incognito Browser Window

Browser cache can interfere with captive portal detection. If your browser has cached a previous version of captive.apple.com, neverssl.com, or the portal page itself, it may serve the cached copy instead of fetching the live redirect. Private browsing windows ignore the cache.

On any device, open an incognito or private window (Ctrl+Shift+N on Windows/Chrome, Cmd+Shift+N on Mac, or from the browser menu on iPhone/Android) and navigate to http://neverssl.com. The portal should appear.

Fix 4: Clear Custom DNS Settings

Captive portals rely on DNS hijacking to redirect you to the login page. If your device is configured to use a custom DNS server like Cloudflare’s 1.1.1.1 or Google’s 8.8.8.8, DNS queries may bypass the portal’s local DNS entirely — or the query fails and the redirect never happens.

On Windows 11/10

Open Settings → Network & Internet → WiFi → [Network Name] → Edit. Under DNS server assignment, switch from “Manual” to “Automatic (DHCP).” Then disconnect and reconnect to the WiFi network.

On macOS

Go to System Settings → Network → WiFi → Details → DNS. Remove any manually entered DNS servers so the list is empty, then click OK. Reconnect to the WiFi network.

On iPhone / iPad

Go to Settings → WiFi, tap the (i) next to the network, then tap Configure DNS and switch from “Manual” to “Automatic.”

On Android

Go to Settings → WiFi, long-press the network name and choose Modify Network. Set IP settings to DHCP and leave DNS fields blank.

Fix 5: Forget the Network and Reconnect

If you’ve connected to this network before, your device may auto-join it and skip the portal redirect because it remembers a previous successful session. Forgetting and re-joining forces the full portal sequence.

On iPhone: Settings → WiFi → (i) → Forget This Network, then search for and rejoin the network manually. On Android, Windows, and Mac the process is similar: find the network in your saved connections, forget/remove it, then reconnect.

Fix 6: Flush DNS and Renew Your IP (Windows)

If you’re on Windows and the portal still won’t appear, a stuck DNS cache or a bad IP assignment is likely the culprit. Open Command Prompt as Administrator and run these commands in order:

ipconfig /release — releases your current IP address
ipconfig /flushdns — clears the DNS cache
ipconfig /renew — requests a fresh IP from the network’s DHCP server

After the final command completes, open a browser and navigate to http://neverssl.com. If your IP address was the problem, the portal will appear.

You can verify you have a valid IP (not a 169.254.x.x self-assigned address) by running ipconfig and checking the IPv4 address field.

Fix 7: macOS — Force Captive Network Assistant to Re-Launch

macOS has a built-in Captive Network Assistant that automatically opens a mini-browser when it detects a captive portal. If it fails to launch or gets stuck, you can trigger it manually.

Open Terminal and run:

sudo killall CaptiveNetworkAssistant

Then disconnect and reconnect to the WiFi. macOS will re-run the portal detection and re-launch the assistant. If the mini-browser appears but is too small or broken, click Open Browser in the bottom-left corner to open the portal in Safari at full size.

Also check that your Mac isn’t set to “Limit IP Address Tracking” for the network in question — this feature can interfere with portal detection on some networks. Go to System Settings → Network → WiFi → Details → Privacy and set it to Off temporarily.

Fix 8: Android — Tap the “Sign In to Network” Notification

Android devices display a “Sign in to network” notification in the status bar when a captive portal is detected. This notification is easy to miss or dismiss. Pull down the notification shade and look for it — tapping it opens the portal in a secure in-app browser window.

If the notification never appeared or was dismissed, go to Settings → WiFi, tap the network name, then look for a “Sign in to network” or “Captive portal” option. Alternatively, navigate to http://connectivitycheck.gstatic.com/generate_204 in Chrome — Android uses this URL for portal detection and visiting it manually triggers the redirect.

Quick Checklist

Disable VPN and security apps before joining the network
Navigate to http://neverssl.com in your browser (not https://)
Open an incognito/private browser window and try again
Switch DNS back to Automatic (DHCP) if you use a custom DNS server
Forget the network and reconnect fresh
On Windows: run ipconfig /release, /flushdns, /renew
On Mac: run sudo killall CaptiveNetworkAssistant and reconnect
On Android: look for the “Sign in to network” notification in the status bar

Captive portal failures almost always come down to one of three things: an active VPN, a custom DNS server, or a stale browser cache. Work through the checklist in order and most users are through the login page within two minutes. Once you’re online, run a quick speed test to see what speeds the network is actually delivering — public WiFi performance varies enormously.