You open a page you need right now, wait a second, and then get hit with Server Cannot Be Found. You refresh. Same result. You try again in another tab. Still nothing.
It's common to assume the website is down or your Mac has suddenly developed some mysterious network problem. Usually, neither is true. In practice, this error is often a short chain of lookup failures, stale settings, or local network interference. The good news is that you can troubleshoot it in a sensible order, starting with the easiest fixes first.
What the Server Cannot Be Found Error Really Means
When you see server cannot be found, your browser usually isn't saying “this website no longer exists.” It's saying your device couldn't translate the website name into the numeric network address it needs to reach the site.
Think of DNS as your device's digital address book. You type a website name. DNS looks up the matching destination. If that lookup fails, your browser has no map to follow, so it stops with this error.
This is a common problem, not a rare disaster. Browsers, routers, DNS resolvers, VPNs, and local security tools can all produce the same message, so the useful move is to narrow the problem one layer at a time.
What it usually does and does not mean
| Situation | What it often means |
|---|---|
| One site won't load | The issue may be site-specific, cached locally, or blocked by a setting |
| Many sites won't load | Your DNS, router, VPN, or broader internet connection may be the problem |
| Internet works on one device but not another | The failing device usually has a local configuration issue |
| Search or a major site works, but others don't | DNS or filtering problems become more likely |
Practical rule: Treat this as a lookup problem first, not proof that the whole internet is broken.
That mindset matters because it keeps you from jumping straight into complicated fixes. In most cases, the fastest path is a calm elimination process. Start with basic checks. Then move to DNS cleanup. Only after that should you touch firewall, VPN, or router settings.
Start With the Quickest and Easiest Fixes
Before changing any settings, do the low-effort checks that help narrow the problem down fast. These steps are boring, but they save time because they tell you whether the problem is the website, the browser, your Mac, or the network around it.
Check whether you're actually connected
Start with the obvious.
- Verify Wi-Fi or Ethernet: Make sure your Mac is still connected to the expected network. If you're on Wi-Fi, check that the signal is active and you didn't unintentionally reconnect to a weak guest network.
- Toggle the connection once: Turn Wi-Fi off, wait a moment, then turn it back on. If you're using Ethernet, reseat the cable if you can.
- Try one reliable website: Open a major site you know should respond. If that works, the issue may be limited to one destination.
A quick test on your phone helps too. Use the same Wi-Fi network first. If the same site fails there, the problem is probably not your Mac.
Test whether the problem follows the browser
Browsers cache a lot. Sometimes they hang onto bad data longer than they should.
Try this sequence:
- Open the site in another browser like Safari, Chrome, or Firefox.
- Quit the failing browser completely instead of just closing the tab.
- Restart your Mac if the browser relaunch doesn't change anything.
If pages fail in one browser but not another, clear the browser cache before doing deeper network work. If you need the exact steps, this walkthrough on how to clear cache on Mac is a useful companion.
If one browser works and another doesn't, don't reboot your router yet. Fix the browser first.
Use a simple decision test
| Test result | Most likely next move |
|---|---|
| Only one tab fails | Reload and try the site later |
| Only one browser fails | Clear browser data and restart it |
| All browsers fail on your Mac only | Move to DNS and network troubleshooting |
| All devices on the same Wi-Fi fail | Check router, VPN, or ISP issues |
These checks won't solve every case, but they stop you from wasting time on the wrong layer.
Troubleshoot Your DNS and Network Connection
If every browser on your Mac fails on the same site, DNS is a sensible next stop.
DNS is the system that turns a name like a website address into the numeric address your Mac can reach. When that lookup goes wrong, the browser can say server cannot be found even though your Wi-Fi still appears connected. Cached DNS records are a common cause, especially after a site changes servers, your network changes, or your Mac hangs onto old results longer than it should.
Flush the DNS cache first
On macOS, start by clearing the local DNS cache. It is quick, safe, and often fixes name lookup problems without changing any permanent settings.
Run these commands in Terminal:
sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder
Your Mac will ask for your password. Terminal usually stays quiet after these commands, and that is normal.
On Windows, the equivalent command is:
ipconfig /flushdns
Restart the apps and connection that may still hold old network state
After flushing DNS, close the browser completely and open it again. Then turn Wi-Fi off and back on.
If the result is still the same, restart the Mac before you change anything else. I recommend this order because it keeps the test clean. If you change DNS providers, reboot the router, and restart the browser all at once, you will not know which step solved the problem.
Change the DNS provider if the issue keeps coming back
If flushing the cache helps for a while but the error returns, your current DNS resolver may be slow, unreliable, or out of sync. On a Mac, changing DNS servers in network settings is a reasonable next step.
Two common options are:
- Cloudflare DNS
- Google DNS
This step helps when the resolver is the weak point. It also helps on some home internet connections where the ISP's DNS service is the least reliable part of the path. If the Mac has no working connection at all, or if a browser extension is interfering, a DNS change will not affect the root cause.
Confirm whether the site is reachable beyond the browser
If the DNS side looks cleaner but the website still does not load, test whether the service itself is reachable. IT teams often verify this at the port level instead of relying on browser messages alone. This guide for DevOps teams on TCP ports shows a practical way to check whether a service is listening and reachable.
Use this order to avoid wasted effort
- Flush DNS cache
- Quit and reopen the browser
- Reconnect Wi-Fi
- Retry the site
- Restart the Mac
- Switch DNS provider if the problem persists
- Test the same site on another device on the same network
That sequence starts with fast, low-risk fixes and saves the more disruptive changes for later. For Mac users, that usually gets you to the answer faster than jumping straight into router settings or advanced network tools.
Check for Blockages from Firewalls, VPNs, or Your Router
If DNS cleanup didn't solve it, stop thinking only about lookup errors. Start thinking about interference.
A VPN, security app, browser extension, local firewall rule, or the router itself can interrupt traffic in ways that look exactly like a website failure. The browser message doesn't always tell you which layer is blocking the request.
Turn off anything that reroutes your connection
VPNs and proxies are common culprits, especially if the error started right after you joined a work network, changed locations, or installed a privacy tool.
Try this elimination test:
- Disconnect the VPN completely: Don't just pause the app if it keeps background routing rules active.
- Disable any proxy setting you knowingly use: This matters on managed work devices more than home Macs.
- Retry on another network: If possible, switch from Wi-Fi to a phone hotspot to see whether the problem follows the Mac or stays with the original network.
If the site opens normally as soon as the VPN is off, the VPN configuration is the issue. In that case, leave DNS alone and focus on the VPN app, server selection, or split tunneling rules.
Look for local security blocks
Security software sometimes blocks browsers in ways that feel random to the user. A firewall rule can also block one browser while allowing another.
Check these places:
| Place to inspect | What to look for |
|---|---|
| macOS firewall settings | Rules that block browser traffic |
| Antivirus or endpoint security app | Web shield or network filtering features |
| Browser extension list | Privacy or filtering extensions breaking page requests |
| Corporate device management settings | Forced DNS, proxy, or security policies |
A quick test is to open the same site in Safari and then in another browser with extensions disabled. If only one setup fails, the browser environment is the likely blocker.
Don't leave your firewall or security tools disabled. Turn them off only long enough to test, then turn them back on and adjust the problem rule.
Reboot the router the right way
Routers cache state too. They can also hold onto stale connection information after ISP hiccups, firmware bugs, or long uptimes.
Do a proper power cycle:
- Unplug the router or modem.
- Wait a short moment.
- Plug it back in.
- Give it time to reconnect fully before testing again.
This isn't glamorous, but it often clears local DNS forwarding problems and stale connection tables. If every device in the house sees server cannot be found, the router becomes much more suspicious.
When this section matters most
These checks are especially useful when:
- The problem appears on multiple sites
- It started after installing a VPN or security tool
- Your Mac fails on one network but works on another
- Every device at home shows similar symptoms
At that point, you're no longer dealing with a simple browser hiccup. You're isolating the network path itself.
Deeper Troubleshooting for macOS Users
Macs have a few recovery options that are worth trying before you give up and call your provider. These aren't the first fixes I'd use, but they're excellent when the problem is persistent and hard to pin down.
Create a new network location
This is one of the cleanest Mac-specific tricks. A new Network Location gives macOS a fresh set of network preferences without forcing you to manually tear down every setting.
Open your Mac's network settings, create a new location, and reconnect to Wi-Fi there. If a hidden preference or damaged network profile is causing the failure, this often clears it.
This step is especially useful when the Mac has moved through many networks over time, including office Wi-Fi, hotel Wi-Fi, personal hotspots, and VPN-managed setups.
Reset network settings on Apple devices
For persistent cases on Apple devices, a more complete reset can help. On iPhone and iPad, you can use Settings > General > Transfer or Reset > Reset > Reset Network Settings to clear saved network settings and force the device to rebuild its connection state.
That path applies to iPhone and iPad. On macOS, the equivalent work is more manual, but the same principle applies. You're clearing out network state that ordinary reconnects don't touch.
Check the hosts file if only one site is affected
If one specific website always fails while others work, inspect the local hosts file. An incorrect entry there can override normal DNS and send your Mac to an incorrect destination.
Use Terminal to view it carefully, not edit blindly. If you want a quick refresher on working inside macOS command line tools, this article about using Terminal on Mac is a good reference.
After you've reviewed the basics, this embedded walkthrough may help if you want a visual explanation of Mac-side troubleshooting steps:
On a Mac, a fresh network location is often safer than making three or four manual changes you may need to undo later.
The point isn't to become a network engineer. It's to use the Mac tools that reset the right layers without creating new problems.
When All Else Fails and How to Stay Productive
If you've tested multiple devices, cleared local cache, restarted the router, and ruled out browser and VPN issues, the problem is probably outside your Mac. At that stage, your internet provider or upstream network has more visibility than you do.
When you contact support, don't start with “my internet is broken.” Give them a short summary they can act on: you've already tested more than one device, restarted local equipment, and ruled out common local causes. That helps you get past generic first-line scripts faster.
If you also need to check a service on another system while recovering, a practical admin reference like this guide on restarting the SSH server on Ubuntu can be handy when the browser issue is only part of a bigger troubleshooting session.
The other part most guides ignore is this. You still need to work while the connection is unstable. Drafts still need writing. Notes still need organizing. Documents still need reviewing.
That's where offline-first tools earn their keep. If your workflow depends entirely on cloud services, a network outage turns into a work stoppage. If part of your stack runs locally, you can keep moving while the connection problem gets sorted.
If you want an AI tool that keeps working when the internet doesn't, LocalChat is built for that exact situation. It runs natively on macOS, works fully offline on Apple Silicon, keeps chats private on your device, and lets you continue writing, analyzing documents, and thinking through problems even when “server cannot be found” is the only thing your browser wants to say.