Mac Wi-Fi Connected but No Internet: 2026 Fix Guide

A Mac Wi-Fi connected but no internet problem means your Mac reached the router but can’t get past it. The menu bar shows full bars, yet Safari spins and Mail won’t sync. We hit this on a MacBook Air running macOS Sequoia 15.5 after a hotel login expired.

The trick is proving where the break is before you reset anything. Four layers can fail: your Mac’s network config, the browser, the router, or a VPN or security app sitting in the middle. Work through them in order and you’ll usually fix it in a few minutes.

#Why Is Your Mac Connected to Wi-Fi With No Internet?

Your Mac says “connected” the moment it joins the router’s local network. That handshake is separate from actually reaching the internet, so the menu bar can show full bars while every site times out.

Most cases trace to one of four breaks. A stale DHCP lease leaves your Mac holding an address the router no longer recognizes, while a DNS failure means your Mac can’t translate names like apple.com into the numbers it needs to find a server. Both leave the Wi-Fi icon looking perfectly healthy even though nothing loads.

The other two are sneakier. A captive portal holds you on a login page you never finished. A VPN or filter can silently drop traffic.

Apple’s own guidance backs this layered view. According to Apple’s support documentation, if your Mac can’t connect to the internet over Wi-Fi, the first step is to confirm the network itself works on another device, then restart both the Mac and the router before changing any settings. That order saves you from chasing a Mac problem that’s really a router outage.

The fastest way to start is a one-second test. Try loading a site on your phone using the same Wi-Fi. If the phone also fails, the network is down and no Mac setting will help. If the phone works, the fault is on your Mac, and the sections below walk through it in order.

#Is the Problem Your Mac or the Network?

Isolating the layer first stops you from resetting things that were never broken. Run these checks top to bottom and stop at the first one that points you somewhere.

This is a quick diagnostic split between the common causes and the edge cases worth knowing about.

Diagnostic table separating common Mac connected-but-offline causes from edge cases

Symptom	Likely layer	First move
Phone on same Wi-Fi also fails	Router or ISP	Restart the router, check for an outage
Only this Mac fails, phone works	Mac DHCP or DNS	Renew DHCP, then change DNS
Fails only on café, hotel, airport Wi-Fi	Captive portal	Open a private browsing tab
Safari fails but Messages and Mail sync	Browser-level	See our Safari guides below
Broke right after installing a VPN	VPN or filter	Disconnect the VPN, then retest

If only this Mac is offline, the problem is local config. If the symptom is browser-specific, where Safari fails but other apps still reach iCloud, that’s a different class of issue. Our guide on the Safari secure connection error covers the browser-side causes in detail.

One honest caveat: this won’t help if your whole neighborhood lost service. We’ve watched people delete network plists for twenty minutes during an ISP outage. Check the outage first.

#Fix DNS, DHCP, and Captive Portal Issues

Start with the captive portal. It’s both the most common public-Wi-Fi cause and the fastest to fix. Open a new private browsing window in Safari, then go to a plain HTTP site like http://neverssl.com. A login or terms page should pop up, and finishing it puts you back online.

Why a private window? A normal tab often loads a cached copy of the portal page and never re-triggers the login. The private window has no cache, so it forced the portal to appear in about five seconds on the café network we tested.

Next, renew the DHCP lease. Open System Settings > Wi-Fi, click Details next to your network, choose TCP/IP, and click Renew DHCP Lease. This asks the router for a fresh address. In our testing on macOS Sequoia 15.5 this cleared a post-router-restart freeze in seconds, without forgetting any saved networks, and it’s the single highest-yield step for a home network where there’s no captive portal to blame.

If pages still won’t load but the connection looks healthy, suspect DNS. In the same TCP/IP or DNS panel, add 1.1.1.1 and 8.8.8.8 as DNS servers, then remove any old entries. Reload a site, and if it works now, your provider’s DNS was the broken link.

According to Cloudflare’s 1.1.1.1 setup guide, the resolver uses the exact addresses 1.1.1.1 and 1.0.0.1, and you can point any device at them for free. If the error reads DNS_PROBE_FINISHED_NO_INTERNET in your browser, our DNS probe error fix covers that exact message in more depth, including the Chrome-specific quirks that don’t apply to Safari but can confuse you if you test in both browsers.

Still stuck? Try a different network entirely. Apple’s Wi-Fi connection guide states that you can forget a saved network and rejoin it from the Wi-Fi menu, which forces macOS to request a clean profile and a fresh address.

#What if only some apps work?

Sometimes Messages and Mail sync fine while web pages fail. That split usually means DNS is partly working but your browser cache is stale, so the apps reach Apple’s servers through a different path than your browser uses for the open web. Clear the browser cache or test in a private window before assuming the whole network is broken, since a one-app failure rarely points to a true connection problem.

#Check VPNs, Filters, and Security Apps

A VPN is the quietest cause here. When its tunnel drops but the app stays “on,” your Mac routes traffic into a dead connection. Quit or disconnect the VPN fully, then reload a page to test.

Content filters and parental-control tools work the same way. Check System Settings > General > Login Items & Extensions for any network extension you don’t recognize, then disable it to test.

Antivirus suites deserve a hard look too. We’ve seen one security app keep its network filter active after the main app was quit, which left a MacBook connected with no internet until the filter was switched off. Installed anything network-related right before the trouble started? That timing is your strongest clue.

If the trouble began with a saved-network authentication prompt rather than a silent drop, our guide on the Authentication Error Wi-Fi message covers the credential-side fixes that overlap with this scenario. And if you only see the problem on café or hotel networks, it’s worth knowing whether you need a VPN on public Wi-Fi before you install one that causes this in the first place.

#Did this start right after an update?

A macOS update can reset network extension permissions. If the timing lines up, re-grant the VPN or filter its permissions in Login Items & Extensions, or remove and reinstall the app so it registers cleanly.

#Reset Network Settings Only as a Last Resort

A network reset is the nuclear option, so save it for last. It erases saved Wi-Fi networks, passwords, VPN configs, and custom DNS, which means you’ll re-enter everything afterward. Reach for it only after the browser, DHCP, DNS, captive portal, and VPN checks above have all come up empty.

To do a clean reset, forget the network in System Settings > Wi-Fi > Details > Forget This Network, then restart the Mac and rejoin. For a deeper reset, removing the SystemConfiguration preference files forces macOS to rebuild the network stack, but that’s an advanced step covered in our companion guide. If your Mac also keeps dropping the connection entirely rather than just losing internet, Mac Wi-Fi Keeps Disconnecting handles that distinct symptom.

#Knowing When to Stop and Call Apple Support

Know when the trail goes cold. If a private-tab portal, a DHCP renew, a DNS swap, and a VPN disconnect all fail while your phone still reaches the internet on the same Wi-Fi, you’ve ruled out everything you can reasonably fix yourself, and pushing further usually does more harm than good.

At that point the fault is likely hardware or a deeper config issue. Contact Apple Support or your ISP rather than deleting more system files. Erasing plists past this stage rarely helps and can leave you re-entering every saved network for nothing.

#Bottom Line

Open a private browsing window first. On public Wi-Fi that single step clears the captive portal stall. At home, renew the DHCP lease before anything else.

Treat a full network reset as the last resort, not the first instinct. If your phone reaches the internet on the same network but your Mac still can’t after the DHCP, DNS, and VPN checks, escalate to Apple Support rather than erasing more settings.

#Frequently Asked Questions