You type an address, Safari finds the site’s name just fine, and then it stalls and shows “Safari Can’t Connect to the Server.” That specific wording matters. It means your Mac resolved the address (DNS worked) but the connection was then refused, blocked, or timed out — a different problem from “Server cannot be found” (a DNS lookup failure) or a secure-connection error (a TLS/certificate failure). Work through these in order and stop at the one that fixes it.
First: is it one site, or every site?
Open a second tab and load a big, reliable site like apple.com. If only one site fails, the problem is almost always that site (it is down, overloaded, or blocking you) — skip to the FAQ. If every site fails but your Wi-Fi shows connected, it is your Mac, your network, or something in between, and the fixes below apply.
The fixes, fastest first
1. Reload, and try a Private window
Press ⌘R to force a reload. Still stuck? Open File › New Private Window and load the same page. A Private window ignores cached data and most extensions — if it works there, the problem is old site data or an extension, handled in steps 3 and 4.
2. Confirm you are actually online
Click the Wi-Fi menu. “Connected” is not the same as “has internet.” Try loading a page in another browser, or turn Wi-Fi off and back on. On a captive network (hotel, airport, cafe) you may need to open the login page first — browse to any plain http:// address and the sign-in page should appear.
3. Clear this site’s data
Go to Safari › Settings › Privacy › Manage Website Data, search the site, and remove it. A stale cookie or cached redirect can keep pointing Safari at a server that no longer answers. Reload afterward.
4. Disable extensions and content blockers
In Safari › Settings › Extensions, turn everything off, then reload. Ad blockers, VPNs, and “privacy” extensions can silently drop the connection to a server. If the page loads, re-enable extensions one at a time to find the culprit.
5. Check your VPN, proxy, and firewall
A connected VPN routes traffic through another server; if that server is down or blocking the site, you get exactly this error. Disconnect the VPN and retry. Then check System Settings › Network › your connection › Details › Proxies — if a proxy is enabled that you did not set, turn it off. Also open System Settings › Network › Firewall; if it is on, make sure it is not in “Block all incoming connections” and that Safari is allowed.
6. Flush the DNS cache and try a public DNS server
Open Terminal and run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. Then, in System Settings › Network › Wi-Fi › Details › DNS, add 1.1.1.1 and 8.8.8.8. This mostly helps name-resolution problems, but a broken resolver can also leave connections half-open, so it is worth a shot here.
7. Check date, time, and Screen Time limits
A wrong system clock breaks the handshake with many servers. Set System Settings › General › Date & Time to update automatically. If you use Screen Time › Content & Privacy › Web Content, a restriction there can block a specific site — confirm the address is not on a limited list.
8. Restart the Mac and the router
Unglamorous, but it clears half-open connections on both ends. Power the router off for 30 seconds, restart the Mac, and try once more before assuming the worst.
The honest part: when it is not something you can fix in software
If every browser on every device on your network fails to reach one site, that site is down — wait it out. But if your Mac keeps dropping connections that other devices hold fine, and it comes with random Wi-Fi drops, sleep-wake network failures, or a fan that never stops, you may be looking at an aging Wi-Fi card or a tired logic board on an older Intel Mac. At that point, sinking money into diagnostics rarely pays off.
A clean Apple-silicon MacBook fixes the whole class of flaky-network problems at once. A refurbished M1 MacBook Air starts at $450 and a 2022 M2 Air at $549 — both far cheaper than a logic-board repair, and every unit on our Apple clearance page is tested and backed by our own warranty. If your current Mac still powers on, we’ll also take it as a trade-in toward the upgrade.
Frequently Asked Questions
What’s the difference between “Safari can’t connect to the server” and “Server cannot be found”?
“Cannot be found” is a DNS failure — your Mac could not even look up the address, covered in our Server cannot be found guide. “Can’t connect to the server” means the address resolved but the connection was refused or timed out, which is what this page fixes.
Why does Safari fail but Chrome loads the same site?
Almost always a Safari-specific extension, content blocker, or a stale cookie for that site. Do steps 3 and 4 above; a Private window that works is the giveaway.
The page loads but is painfully slow — is that the same thing?
No. Slowness with an eventual load is a different problem — see Safari slow or pages not loading. This error is a connection that never completes at all.
Does this error mean the website is down?
It can. If the site fails on every device and browser on your network, it is down or blocking your region — wait, or try a different network. If only your Mac fails, work the fixes above.
Could my antivirus or a firewall be blocking Safari?
Yes. Third-party security suites and the built-in firewall can block outgoing connections. Temporarily disable the suite and, in System Settings › Network › Firewall, make sure Safari is allowed (step 5).