Safari Not Working on Public Wi-Fi? Fix It Now

If Safari won’t load pages on airport, hotel, or other public Wi-Fi, the fix is usually to forget the network, rejoin it, and complete the captive portal login—or, failing that, to clear Safari’s cache and change its DNS settings. This guide walks through the exact steps, why public networks break Safari specifically, and what to do when the standard fixes don’t work.

Why Public Wi-Fi Breaks Safari

Public Wi-Fi networks—airports, hotels, coffee shops—almost always use a captive portal: a login page you must interact with before you get internet access. Safari, like other browsers, is supposed to detect this portal and pop it open automatically. But that detection often fails because:

The network’s DNS servers are slow or misconfigured, so Safari can’t resolve the portal’s address.
The portal page uses an older HTTP redirect that Safari’s security settings block.
Your Mac or iPhone is still holding onto a previous network’s IP address or DNS cache.
The network requires you to accept terms or enter a room number, and Safari’s automatic pop-up gets suppressed by a pop-up blocker or a previous session.

When this happens, you’ll see “Safari Can’t Open the Page” or the page just spins. The good news: the fix is almost always something you can do in under two minutes.

The Quick Fix: Forget and Rejoin the Network

Start with the simplest, most reliable reset. This clears the broken connection state and forces your device to renegotiate with the network.

On iPhone/iPad: Go to Settings → Wi-Fi, tap the blue “i” next to the network name, then tap Forget This Network. Turn Wi-Fi off and on, then tap the network name again and rejoin.
On Mac: Click the Wi-Fi icon in the menu bar, choose Open Network Preferences (or System Settings → Wi-Fi), click Details next to the network, then Forget This Network. Turn Wi-Fi off and on, then reconnect.
After rejoining, a captive portal page should appear automatically. If it doesn’t, open Safari and type captive.apple.com (or neverssl.com) in the address bar. This forces your device to check for a portal and usually triggers the login page.

If the portal still doesn’t appear, try opening Safari in a private window (private browsing disables some cached redirects), or switch to a different browser like Chrome to complete the login—once you’re logged in, Safari will often work fine.

Clear Safari’s Cache and Cookies

Sometimes Safari’s stored data from a previous network session interferes with the new connection. Clearing the cache is safe—it doesn’t delete passwords or bookmarks.

iPhone/iPad: Settings → Safari → Clear History and Website Data. This removes browsing history, cookies, and cache. You’ll need to log back into some sites, but it won’t affect saved passwords in iCloud Keychain.
Mac: Open Safari, go to Settings (or Preferences) → Privacy, click Manage Website Data, then Remove All. Or simply clear history via History → Clear History and choose “all history.”

After clearing, try the captive portal URL again. If Safari still fails, the issue is likely DNS.

Change DNS to Bypass Broken Network DNS

Public Wi-Fi often uses the hotel’s or airport’s DNS servers, which can be slow, overloaded, or even block certain domains. Switching to a public DNS like Google (8.8.8.8 and 8.8.4.4) or Cloudflare (1.1.1.1 and 1.0.0.1) can fix Safari’s inability to resolve addresses.

iPhone/iPad: Settings → Wi-Fi, tap the “i” next to the network, scroll to Configure DNS, set it to Manual, delete any existing servers, and add 8.8.8.8 and 8.8.4.4. Tap Save.
Mac: System Settings → Network → Wi-Fi → Details → DNS. Click the plus sign, add 8.8.8.8 and 8.8.4.4, then click OK and Apply.

After changing DNS, reconnect to the network and try Safari again. If the portal page still doesn’t load, you may need to complete the login using a different device or browser first, then return to Safari.

Other Common Causes and Fixes

If the above steps don’t work, consider these less obvious culprits:

Date and time settings: If your device’s clock is off, SSL certificates fail, and Safari refuses to load secure pages. Go to Settings → General → Date & Time and toggle Set Automatically.
VPN or content blockers: A VPN can interfere with captive portal detection. Turn off your VPN and any Safari content blockers, then try the login page again.
Private Relay (iCloud+): On iPhone, if iCloud Private Relay is on, it can prevent the portal from loading. Go to Settings → Apple ID → iCloud → Private Relay and toggle it off temporarily.
Restart your device: A full restart clears all network caches and background processes. It’s a cliché because it works.

If you’re still stuck, try connecting to the network’s guest SSID instead of the main one, or ask the front desk if there’s a separate login URL—many hotels have a direct link you can type into any browser.

Why Safari Fails More Than Chrome

Safari is more aggressive about blocking mixed content and tracking, and it handles captive portal detection differently than Chrome or Firefox. On public Wi-Fi, the portal often uses HTTP (not HTTPS) and redirects through a third-party domain that Safari may flag as a potential tracker. Chrome, by contrast, is more lenient with these redirects, which is why you can often log in with Chrome and then switch back to Safari. This is a known quirk, not a bug in your device.

When to Use a Different Browser or App

If Safari absolutely won’t cooperate, you have two practical options:

Use Chrome, Firefox, or Edge just for the login step. Once the network is authenticated, Safari will typically work for the rest of your session.
If you need to access a specific app (like email or banking), try opening that app directly—many apps have their own network logic and may connect even when Safari fails.

For frequent travelers, consider downloading a “captive portal helper” app, but be aware these often just replicate what Safari already does. The most reliable approach is the forget-and-rejoin method with a manual DNS change.

Frequently Asked Questions

Why does Safari say “Can’t Open Page” but other apps work?

Other apps may use different network stacks or have cached connections. Safari relies on the system’s DNS and captive portal detection, which can fail on public Wi-Fi. If other apps work, the network is fine—the issue is Safari’s connection state. Forget the network, rejoin, and clear Safari’s cache.

How do I force Safari to open the login page?

Type captive.apple.com in the address bar. This is Apple’s official captive portal check URL. If the page loads a blank or a “Success” message, you’re already connected. If it shows a login page, complete it. Alternatively, type neverssl.com, which is a plain HTTP site that always triggers a portal.

Will changing DNS affect my security?

Using Google or Cloudflare DNS is generally safe and more private than many hotel DNS servers. It doesn’t encrypt your traffic, but it does make DNS resolution faster and more reliable. For full privacy, use a VPN, but turn it off during the initial portal login.

Why does Safari work at home but not at the airport?

Home networks don’t use captive portals and usually have reliable DNS. Airports and hotels use portals that require interaction, and their DNS is often congested. The difference is the network environment, not your device. The forget-and-rejoin method is the first thing to try.

Do I need to reset my network settings?

Only as a last resort. On iPhone, Settings → General → Transfer or Reset iPhone → Reset → Reset Network Settings clears all saved Wi-Fi networks, Bluetooth pairings, and VPN settings. It often fixes persistent issues but is inconvenient because you’ll need to re-enter all your Wi-Fi passwords. Try the other steps first.

Can I use Safari after logging in with another browser?

Yes. Once the network is authenticated, the connection is at the system level, not browser-specific. After logging in with Chrome, Safari should work immediately. If it doesn’t, clear Safari’s cache and try again.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →