Safari 15.4 'Cannot Open Page' – iCloud Private Relay fix

The 30-second fix: Toggle iCloud Private Relay off

This is the most common reason Safari 15.4 on macOS Monterey throws 'Cannot Open Page' — iCloud Private Relay conflicts with your network. Usually happens on corporate networks, public Wi-Fi, or any setup with custom DNS filtering (like Pi-hole or Cisco Umbrella). Private Relay tries to encrypt and route your traffic through Apple's relays, but if your network blocks those relay endpoints, Safari gives up and shows you that useless error.

1. Open System Settings (or System Preferences on older Monterey builds).
2. Click your Apple ID (top left).
3. Click iCloud.
4. Find Private Relay — it's under iCloud+ features.
5. Toggle it off.

That's it. Test Safari immediately. If pages load, you're done. The error won't come back until you turn Private Relay on again. If you still see the error after this, move to the 5-minute fix below.

The 5-minute fix: Whitelist Private Relay endpoints or use a different DNS

If you actually want to keep Private Relay on (for privacy) but still fix the error, the problem is often DNS. Private Relay uses two separate IP ranges for its relay servers, and some networks block or misroute those. The cleanest fix: change your DNS to a public resolver that Private Relay plays nice with.

1. Open System Settings > Network.
2. Select your active connection (Wi-Fi or Ethernet).
3. Click Details.
4. Go to DNS tab.
5. Remove any existing entries, then add these:

   8.8.8.8
   8.8.4.4
   1.1.1.1
   

6. Click OK, then Apply.

Google's or Cloudflare's DNS doesn't get in Private Relay's way the way some corporate DNS servers do. If you're on a company network and can't change DNS, you'll need to talk to your IT team — they might need to allowlist Apple's relay IP ranges. Tell them to whitelist 17.0.0.0/8 and 10.0.0.0/8 (Apple's relay blocks). That fixes it 90% of the time.

The 15-minute advanced fix: Diagnose with network tools and disable Private Relay forcefully

If neither of the above works, something deeper is wrong. Could be a VPN conflict, a stuck network proxy, or a corrupted Safari profile. Let's isolate it.

Step 1: Check if Private Relay is actually the problem

Open Console.app (search in Spotlight). Filter for safarid and com.apple.sharing. Reload Safari and reproduce the error. Look for lines containing privateRelay or relay1. If you see errors like connection refused or timeout, that's the smoking gun.

Step 2: Force disable Private Relay via terminal

Sometimes the toggle in Settings doesn't fully kill the relay processes. Run this:

sudo defaults write /Library/Preferences/com.apple.networkservices PrivateRelayEnabled -bool NO
sudo killall -HUP cfprefsd

Then reboot. This nukes the relay config system-wide, even overriding user settings.

Step 3: Reset Safari completely

If you still get the error, Safari's cache or state is corrupt. Don't bother with clearing history — go nuclear.

1. Quit Safari completely.
2. In Finder, press Cmd+Shift+G and go to:

   ~/Library/Safari

3. Delete these files:

   SafeBrowsing.db
   SafeBrowsing.db-shm
   SafeBrowsing.db-wal
   WebpageIcons.db
   

4. Relaunch Safari. It'll rebuild these files fresh.

Step 4: Check for VPN or proxy conflicts

Private Relay won't work if you have a VPN active — Apple designed it that way. Disconnect any VPN, then test. If pages load, you need to switch to a VPN that supports Private Relay (rare — only a few like Windscribe claim compatibility). Or just accept you can't use both simultaneously.

For proxies: System Settings > Network > select your connection > Proxies. Make sure nothing is checked unless you intentionally set it up. A stray proxy setting from an old VPN or malware will break Private Relay and Safari together.

Step 5: Last resort — create a new user account

If everything above fails, your user account's Safari plist is probably hosed. Create a fresh user in System Settings > Users & Groups, log into that account, and test Safari. If it works there, migrate your data over. This takes 15 minutes but guarantees a clean environment.

Why this happens

iCloud Private Relay routes your Safari traffic through two separate proxies. The first one hides your IP from Apple, the second hides the site you're visiting from your ISP. If either proxy is unreachable — blocked port, bad DNS, firewall rules — Safari doesn't fall back gracefully. Instead of loading the page over a direct connection, it just errors out with 'Cannot Open Page'. It's a design flaw Apple hasn't fixed in Monterey 12.3 or 12.4. Ventura handles it better, but if you're stuck on Monterey, these steps are your only way out.

Pro tip: If you're in a region where Private Relay is blocked by law (China, Belarus, etc.), don't bother diagnosing — it'll never work. Just turn it off permanently.