Skip to content
FixingBook
Sign In
Verifiedbeginnerest. 15 minutes

Fix Safari Cannot Open the Page Because the Server Cannot Be Found

Resolve the 'server cannot be found' error in Apple Safari by flushing DNS and adjusting settings.

SafariNetworkErrormacOS

Confirmed working on: macOS

Before you begin

Match the environmentUse this guide only for macOS or a clearly compatible setup.
Protect recoveryBack up important data and save encryption or account recovery keys before changing system state.
Know when to stopMake one change at a time and stop if the result differs from what the guide describes.

Problem overview

Safari fails to load a website, displaying an error that it cannot open the page because the server cannot be found. This means Safari is unable to translate the website’s domain name into an IP address.

Common causes

  • A stale or corrupted macOS DNS cache
  • Unreliable DNS servers provided by your ISP
  • Overly aggressive Content Blockers or extensions
  • Local Wi-Fi or router connectivity drops

Solution 1: Flush macOS DNS cache

Clearing your Mac’s DNS cache forces Safari to look up fresh IP addresses for websites.

  1. Open Terminal (found in Applications > Utilities, or by pressing Cmd + Space and typing Terminal).
  2. Type the following command and press Return: 
    sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
  3. Enter your Mac administrator password when prompted (the characters will not appear as you type).
  4. Restart Safari and try loading the page again.

Solution 2: Change DNS servers

Switching to a reliable public DNS service like Cloudflare (1.1.1.1) or Google (8.8.8.8) often bypasses ISP routing issues.

  1. Open System Settings (or System Preferences) and click Network.
  2. Select your active network connection (e.g., Wi-Fi) and click Details… (or Advanced).
  3. Select the DNS tab.
  4. Click the + button under DNS Servers and add 1.1.1.1 and 1.0.0.1.
  5. Click OK, then apply the changes.
Expert Tip

If you are on a restricted corporate or school network, changing DNS settings might be blocked. Contact your IT administrator if the issue persists.

Solution 3: Disable Content Blockers and extensions

Ad blockers or privacy extensions can malfunction and block legitimate server requests.

  1. Open Safari and click Safari in the menu bar, then choose Settings (or Preferences).
  2. Go to the Websites tab.
  3. Select Content Blockers in the left sidebar.
  4. Set the dropdown next to the problematic website to Off.
  5. If the site still fails to load, go to the Extensions tab and temporarily uncheck all extensions to isolate the problem.

Confirm the result

  1. Repeat the exact action that originally triggered the problem.
  2. Confirm the original error or symptom is gone and no new warning has appeared.
  3. If the guide changed a driver, service, package, or system setting, restart once and test again.
  4. If the result is worse or unexpected, stop. Reverse only the last change using its documented restore option; if none is documented, use your backup or qualified support.

Questions about this fix

Why does this error only happen in Safari?

Safari relies heavily on macOS system-level networking and DNS caches, which can sometimes desynchronize from other browsers.

Are Content Blockers the same as extensions?

Content Blockers are a specific type of Safari extension optimized to block ads and trackers with minimal performance impact.

Did this fix work for you?

Weighted Consensus Protocol

Consensus0%
Required100% (Weight 3)
Contributors0
Verified By YouNo
Your Weight--

Did this solution resolve your issue?

Confirming if this works strengthens verification statistics on the registry.

Sign In to VerifySign in required to verify

FixingTeam10,000 rep

Official Project Maintainers

The core engineering and moderation team behind FixingBook. We curate, verify, and maintain the standards of the troubleshooting ledger.

Spotted something outdated? Suggest an edit. Maintainers review submissions within 48 hours.
Share:XReddit

Discussion (0)

No comments yet. Share your experience or verify if this fixed your issue!

Join the Discussion