How to Fix ‘Safari Cannot Open Page Because Network Connection Was Lost’

Browsing websites in Safari on an iPhone, iPad, or Mac can suddenly abort with the frustrating connection prompt: Safari cannot open the page because the network connection was lost (POSIX error NSPOSIXErrorDomain: 100 or kCFErrorDomainCFNetwork: 303). Even when Wi-Fi signal indicators show full strength and other networked applications stream content without interruption, Safari terminates HTTP requests mid-stream. This networking failure occurs when an active TCP/IP socket or QUIC (HTTP/3) transport tunnel is abruptly dropped by the network gateway, host web server, or local VPN filter before the webpage payload can finish transferring.

Eliminating this connection drop requires flushing local DNS resolver caches, managing experimental HTTP/3 protocols in Safari, disabling third-party security filters, and renewing local network DHCP leases.

Why Does Safari Report That the Connection Was Lost?

Modern web browsers maintain persistent keep-alive sockets to accelerate webpage delivery. The network connection was lost error is triggered by several specific breakdown points:

  • Premature TCP Socket Termination: A Wi-Fi router, firewall, or web server abruptly closes an open TCP handshake while Safari is actively awaiting response headers.
  • Experimental HTTP/3 (QUIC) Transport Failures: Web servers supporting QUIC over UDP drop packets when cellular or broadband routers block non-standard UDP ports, causing Safari HTTP/3 handshakes to fail.
  • VPN and Private Relay Socket Collisions: iCloud Private Relay or third-party VPN proxies encounter packet latency desynchronisation, causing local socket timeouts.
  • Corrupted DNS and Network Leases: Stale DNS cache tables hold obsolete IP addresses for content delivery networks (CDNs).
  • Third-Party Content Blockers: Ad-blocking extensions sever websocket or dynamic resource connections mid-stream, triggering connection abort notifications.

Step 1: Toggle Aeroplane Mode to Reset Network Interfaces

A quick radio reset clears deadlocked socket connections across cellular and Wi-Fi adapters:

  1. On iPhone or iPad, swipe down from the upper-right corner to open the Control Centre.
  2. Tap the Aeroplane Mode icon to enable it.
  3. Wait 15 seconds to allow the baseband processor to release all open TCP sockets.
  4. Tap the icon again to disable Aeroplane Mode.
  5. Allow your device to reconnect to Wi-Fi or cellular mobile data, and reload your webpage in Safari.

Step 2: Disable iCloud Private Relay Temporarily

Apple iCloud Private Relay routes Safari traffic through dual encrypted relays. When relay servers experience routing delays, socket timeouts occur:

  1. Open Settings on your iPhone or iPad.
  2. Tap your Apple Account profile name at the top.
  3. Tap iCloud > Private Relay.
  4. Toggle Private Relay to Off (select Turn Off Until Tomorrow).
  5. On a Mac, navigate to System Settings > Apple Account > iCloud > Private Relay and toggle it off.
  6. Refresh Safari to test whether standard direct network routing resolves the connection drop.

Step 3: Flush DNS and Renew DHCP Lease

Refreshing your local IP assignment eliminates stale gateway routing tables:

  1. On iPhone/iPad: Open Settings > Wi-Fi. Tap the informational (i) icon next to your connected network. Scroll down and tap Renew Lease.
  2. On Mac: Open Terminal and flush the local directory service DNS cache by executing:
    sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
  3. Press Return and enter your Mac administrator password.

Step 4: Manage Experimental HTTP/3 Features in Safari on Mac

If the error occurs specifically on modern web applications utilizing HTTP/3 over UDP:

  1. Open Safari on your Mac.
  2. Go to Safari > Settings > Advanced.
  3. Check the box at the bottom for Show features for web developers.
  4. Click the new Developer menu in the top menu bar.
  5. Navigate to Feature Flags.
  6. Search for HTTP/3.
  7. Temporarily uncheck HTTP/3 to force Safari to use reliable TCP-based HTTP/2 transport.
  8. Restart Safari and load the affected site.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.