Mac VPN Connected but No Internet? The Upload Was the Real Connection Test

The VPN said Connected. Safari said otherwise.

I was in an airport lounge with 18 minutes left to upload a revised client presentation. The MacBook showed full Wi-Fi bars, the VPN icon was green, and the 43 MB file in the browser had not moved beyond zero percent.

Slack displayed Connecting.

Mail had stopped checking for new messages.

I blamed the lounge network first. It had already asked me to accept its terms twice, and the signal weakened whenever more passengers entered the room.

Then I checked my phone. On the same Wi-Fi, websites opened normally.

I disconnected the VPN on the Mac.

Safari loaded immediately. Slack delivered three messages at once. The upload page came back to life.

The diagnosis seemed obvious, but the solution was not. I could turn the VPN off and send confidential client material over public Wi-Fi, or turn it back on and lose the internet again.

I reconnected.

The status returned to Connected.

Everything stopped.

At that moment, I was no longer asking why my Mac showed a working VPN without working internet. I needed a route that could carry the presentation before my client joined the meeting.

Three green indicators did not make one usable connection

My Mac had installed a macOS Tahoe update earlier that week, so the operating system was an easy suspect.

Other users had described the same visual contradiction after Tahoe updates: the Mac appeared connected to Wi-Fi, yet browsers and apps could not reach the internet. VPN configurations and network filters were among the recurring factors.

Apple’s own troubleshooting guidance tells users to check VPN and security software when a Mac is connected to Wi-Fi but internet services remain unavailable.

That advice made more sense once I separated the indicators on my screen.

The Wi-Fi symbol meant the Mac had joined the lounge network. The green VPN status meant the app believed its tunnel was active. Neither proved that traffic was successfully reaching the internet through that tunnel.

A VPN redirects traffic into a protected route managed by the app. When that route stops forwarding correctly, the Mac can remain connected to Wi-Fi and the VPN can remain green while Safari waits for responses that never arrive.

The status was reporting the tunnel, not the result.

Mac users have also described connections remaining broken after a VPN disconnect, sometimes until Wi-Fi was reset or the computer restarted. The practical frustration was familiar: the VPN changed the route but did not restore a usable one when conditions changed.

That matched the problem in front of me. Instead of trusting the green indicator, I began judging each connection by whether it could move the file.

The established provider gave me more ways to troubleshoot

The VPN already installed on the Mac came from a large, familiar provider.

That was why I had chosen it. The company had years of public history, a substantial support operation and servers across a long list of countries and cities. Under stable conditions, it was fast and predictable.

I opened the app and selected the nearest recommended server.

Connected.

Safari still could not load a page.

I switched to a second server. This time the client portal opened, but the upload stalled after 4 MB.

The lounge Wi-Fi weakened for a moment. The VPN briefly displayed Reconnecting, returned to Connected, and left the browser frozen.

I changed the protocol setting.

A third route restored the internet. The presentation reached 11 MB.

Then I closed the MacBook and walked to the quieter end of the lounge, where a power socket had become available. When I opened the lid again, the VPN icon was still green.

The upload had failed.

The provider’s network lock was preventing traffic from falling silently onto the public connection. That protected the file from an unnoticed leak, but it also left me with no usable route.

I disconnected and reconnected once more.

Safari returned.

Then it stopped again.

By then, the server list was no longer reassuring. It had become a collection of repairs I had to test and supervise individually.

I could not observe the lounge network’s internal filtering or determine whether the failure came from stale routing, DNS handling, movement between access points or its treatment of the VPN traffic. What I could see was enough: each brief network interruption created another manual recovery process, even after the app returned to Connected.

That changed the comparison.

I did not need a VPN with more ways to announce that its tunnel was active. I needed one that restored a working route when the network underneath it changed.

The smaller app proved the connection with the upload

I disconnected the first provider and opened OnlyDogs VPN.

Basic use did not require a conventional account with an email address and password. That removed one delay I did not have time for: no confirmation email, no password manager and no account-recovery page on an internet connection that was barely working.

The interface also avoided another round of server and protocol decisions. I selected the situation-based option for an unstable connection and let the app choose the route.

It connected.

This time, I ignored the status icon.

I opened Safari.

The client portal loaded.

I restarted the presentation upload and watched the counter move past the point where the earlier attempt had failed:

8 MB.

14 MB.

21 MB.

The lounge network dipped again. Slack briefly showed Reconnecting, then delivered a message from the client asking whether we were still on schedule.

I typed, “Uploading now,” and pressed Return.

The message sent.

The presentation continued to 32 MB.

Then the gate changed.

I closed the MacBook, put it in my bag and left the lounge. At the gate, I reopened it on the airport’s main Wi-Fi network.

The connection recovered.

Safari resumed the upload instead of returning me to the login screen.

Forty-three megabytes reached the portal with four minutes left.

The confirmation page appeared:

Upload complete.

That was the first connection status that mattered.

The established provider had repeatedly told me its VPN was connected. The smaller app proved it by completing the task the connection existed to protect.

Recovery mattered more than the first connection

Only after the file arrived did I look at the technical difference.

The service uses HTTP/3-based transport, which can keep a connection moving when the network path changes rather than treating every change as a complete restart.

That suits the way a MacBook is actually used. The lid closes. The machine wakes. Wi-Fi moves between access points. An airport user leaves one network and joins another.

The smaller app recovered through those transitions without leaving traffic trapped behind a green indicator. I did not have to reset Wi-Fi, clear DNS settings or restart the Mac while the client waited.

That was all the technical explanation the result required. The upload had survived both sleep and a network change.

“Connected” was no longer the finish line

After the meeting, I reopened the established provider and looked again at what it offered.

Its advantages were still real. It had more server locations, a longer public history and more documentation for users who wanted to tune protocols and connection behavior themselves.

The smaller service has fewer locations, fewer independent reviews and a shorter history. Someone who needs a precise exit city or extensive enterprise documentation may prefer the larger provider.

Those strengths answered a different question.

When a Mac shows VPN Connected but no internet, the immediate problem is not a shortage of server names. It is the gap between creating a tunnel and keeping a working route through it.

The established provider gave me more controls after each failure. Turning it off restored the internet but removed the protection I wanted. The smaller app recovered through the network changes and let the protected upload finish.

That morning, the right VPN for my Mac was the one that kept the 43 MB presentation moving after the green dot had stopped meaning anything.

Editorial context: OnlyDogs VPN commissioned the original article. The first-person narrative is a composite based on public reports and product testing.