How to Fix ‘Safari Cannot Open the Page Because Too Many Redirects Occurred’ on Mac

Navigating to websites, cloud portals, or web services in Apple Safari only to be greeted by the error message: ‘Safari can’t open the page because too many redirects occurred’ halts web browsing immediately. This HTTP redirect loop (often corresponding to HTTP 301, 302, or 307 redirect chains) happens when a webpage instructs Safari to navigate to a destination URL that immediately directs the browser back to the original URL. In Safari on macOS, these infinite loops are typically triggered by conflicting authentication cookies, misconfigured iCloud Private Relay proxies, date and time desynchronisation, or stale web inspector caches.

Why Do Infinite Redirect Loops Occur in Safari?

When a web server receives an HTTP request, it evaluates session cookies to decide whether to serve content or redirect to a login portal. Common causes of redirect loops include:

  • Corrupted or Stale Domain Cookies: The website sends an expired authentication cookie that the server rejects, redirecting to login, which reads the existing cookie and bounces back, creating an infinite loop.
  • iCloud Private Relay Geolocation Routing: Safari routing encrypted web requests through dual-hop proxies that alter IP addresses between consecutive HTTP handshakes, tripping web application security firewalls.
  • System Clock Time Drift: If your Mac’s internal system clock deviates from true atomic time, SSL/TLS certificate timestamps and cookie expiration headers fail validation checks.
  • Conflicting Safari Web Content Extensions: Content blockers and security extensions stripping required tracking tokens from redirect URLs.
  • HTTP to HTTPS Canonical Configuration Conflicts: The server attempting to enforce secure HTTPS while Safari cached an unencrypted HTTP redirect rule.

Step 1: Clear Website Data and Cookies for the Specific Domain

Flushing stored cookies and cache data for the problematic domain breaks the authentication loop without deleting browsing data for other sites.

  1. Open Safari on your Mac.
  2. Click Safari in the top menu bar and select Settings (or Preferences).
  3. Select the Privacy tab.
  4. Click the Manage Website Data… button.
  5. In the search field at the top right, type the domain name of the website triggering the redirect error.
  6. Select the website from the search results and click Remove.
  7. Click Done, close Safari Settings, and reload the webpage.

Step 2: Test in a Private Browsing Window

Private browsing opens a pristine session without reading stored cookies or running certain third-party extensions.

  1. In Safari, press Cmd + Shift + N to launch a Private Window.
  2. Enter the target URL and press Return.
  3. If the site loads correctly, the issue is confirmed to be stale cookie data or conflicting Safari extensions.

Step 3: Toggle iCloud Private Relay

iCloud Private Relay encrypts DNS and IP metadata, but some web services block or loop when handling proxied traffic.

  1. Click the Apple menu in the top left corner and open System Settings.
  2. Click your Apple Account / Name at the top of the sidebar.
  3. Select iCloud.
  4. Scroll down to Private Relay.
  5. Toggle Private Relay Off temporarily (select Turn Off Until Tomorrow).
  6. Return to Safari and reload the problematic website.

Step 4: Verify Mac Date and Time Settings

An inaccurate system clock invalidates web cookie expiry timestamps, triggering repetitive server-side re-authentication redirects.

  1. Open System Settings > General > Date & Time.
  2. Ensure Set time and date automatically is toggled On.
  3. Ensure Set time zone automatically using your current location is toggled On.
  4. If the time is slightly skewed, toggle the automatic switches off and on again to synchronize with Apple network time servers (time.apple.com).

Step 5: Disable Conflicting Safari Extensions

Ad-blockers and privacy shields can interfere with URL query strings required during OAuth redirects.

  1. In Safari, open Settings > Extensions.
  2. Uncheck all active extensions (such as ad-blockers, script managers, or VPN plugins).
  3. Reload the webpage. If the page loads normally, re-enable extensions one by one to pinpoint the conflicting tool.

Deleting isolated domain cookies, disabling conflicting Safari extensions, and configuring iCloud Private Relay resolves infinite redirect loops on macOS.

Get the best tech tips delivered straight to your inbox.

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