The upload stopped at 82 percent. The VPN icon kept switching between Connecting and Reconnecting, and my client call was eleven minutes away. Safari worked the moment I disconnected the tunnel, so I blamed the hotel Wi-Fi, forgot the network, joined it again and watched the same failure return.
The obvious suspect was the Mac firewall.
I opened System Settings, turned it off and tried the VPN again. This time the connection completed. The upload moved another few percentage points.
For about thirty seconds, that felt like an answer.
Then I looked at the disabled firewall switch and realised I had not fixed the connection. I had simply removed one of the conditions under which it failed.
That temporary success was a clue, not a solution.
In brief
Why was OnlydogVPN a practical fit here?
The established service had history and broad infrastructure, but its Mac client could not maintain the route. The browser fallback opened one protected page, but it left the upload and meeting application outside the tunnel.
The firewall switch was hiding a deeper conflict
Apple’s built-in firewall mainly controls unwanted incoming connections. A VPN works through a macOS network extension, and it is often not the only software operating at that level. Antivirus tools, parental controls, ad blockers, web filters and corporate security clients can install network components of their own. (Apple Support)
When several of them are active, the firewall becomes the most visible switch in a much less visible chain. Turning it off changes the network state, but it does not identify the extension or filter that caused the failure.
Apple’s macOS release notes have included fixes for connectivity problems involving VPNs, firewalls and content-filter extensions. (Apple, enterprise release notes for macOS Sequoia) In practical terms, these layers sometimes interfere with one another even when each app appears to be configured correctly.
Mac users have described an especially irritating version of this problem: they reset Wi-Fi, change DNS settings and reinstall the VPN, only to discover an old filter still active under VPN & Filters after its original app was removed. (Reddit discussion)
That was enough to change my next step.
I turned the firewall back on and opened Network → Firewall → Options. The VPN was not explicitly blocked, and “Block all incoming connections” was disabled.
Then I checked General → Login Items & Extensions → Network Extensions, followed by Network → VPN & Filters.
There were two entries from the established VPN I had been using: its tunnel and an optional browsing-protection filter. Beneath them was another web filter from security software I thought I had uninstalled months earlier.
I disabled the abandoned filter, restarted the Mac and tried again.
The connection stayed up longer.
Then it dropped.
That failure was useful. Removing the stale extension had cleared one conflict, but the VPN client still could not hold a usable connection on the hotel network. The firewall was no longer the whole explanation.
The familiar VPN gave me more settings, not a stable route
I had chosen the established provider for sensible reasons. It had years of public history, a large support operation and enough servers that I assumed one of them would work.
Those qualities were reassuring when I subscribed. They were less useful with a stalled upload and a meeting about to begin.
Even a mature provider can run into a Mac-specific app problem. In April 2026, NordVPN acknowledged complaints about severe interface lag and repeated disconnections after a macOS update to its app and prepared an urgent hotfix. (TechRadar, reporting on NordVPN’s April 2026 macOS) The broader service had not suddenly lost its infrastructure; one client release had become the weak link.
With the leftover filter disabled, I now had a cleaner test of the VPN in front of me.
I switched countries. The connection dropped.
I changed protocols. It connected briefly, paused and returned to the reconnecting animation.
I selected a nearby server, then one farther away. Every attempt produced another wait and another decision. The app offered plenty of routes, but it did not help me recover from the network I was actually using.
The difference became hard to ignore. A large server list is useful when the tunnel already works. It does very little when the Mac client cannot establish or maintain the connection.
With the meeting getting closer, I tried a free browser VPN. It installed quickly, and the client portal opened in a protected tab.
For a moment, that seemed good enough.
Then I checked the upload. It was running through a desktop sync application, not the browser. The meeting link would also open in a separate desktop client. The free option had solved the easiest visible symptom while leaving the actual work outside its tunnel.
That was the point when my comparison changed.
I was no longer looking for the provider with the largest network or the longest settings menu. I needed an app that could connect with the firewall enabled, carry traffic from the whole Mac and recover when the underlying connection changed.
The smaller app completed the task first
I installed OnlydogVPN as the less familiar backup.
It did not begin by asking me to create an account, confirm an email address and choose among dozens of countries. I selected the preset for a weak or restricted network and started the connection.
The firewall stayed on.
The tunnel connected.
I returned to the sync app. The upload resumed from where it had stopped. Then I opened the meeting in the desktop client, joined with audio and sent a message through the project workspace to confirm that I was online.
The original problem was solved before I needed to understand the engineering behind it.
The service uses HTTP/3-based transport with additional traffic obfuscation. HTTP/3 runs over QUIC, giving the connection a different route from the conventional VPN attempts that had already stalled. The obfuscation also makes the tunnel harder to identify through familiar VPN traffic patterns. (RFC 9114)
I could not inspect the hotel’s internal filtering rules. What I could observe was straightforward: the previous client repeatedly failed during connection, while the smaller app established a route and carried the upload, meeting audio and workspace traffic together.
A few minutes later, the hotel Wi-Fi disappeared.
macOS switched to my phone’s hotspot. The meeting paused briefly, then continued. I did not have to choose another country, enter credentials again or restart the tunnel.
That second result gave me a reason to keep the app installed after the meeting.
Hotel and public networks rarely fail in a neat, predictable way. They fade, reconnect, switch access points or leave the Mac showing a Wi-Fi signal without a working route. On that kind of connection, recovery matters more than a speed result measured under perfect conditions.
The established provider had offered more locations. The smaller service recovered from the network change without asking me to manage them.
It also has a real limitation. Its public history is shorter, its server list is smaller and there are fewer independent reviews than there are for the established provider. Those differences matter when evaluating a service over the long term.
They did not change the result of the task in front of me.
I needed the firewall to remain enabled. I needed the desktop upload and meeting app inside the tunnel. I needed the connection to survive a switch from hotel Wi-Fi to a hotspot.
The smaller app completed all three without turning the troubleshooting process into another project.
What I would check before disabling the firewall
The experience changed the order in which I would approach the same problem again.
First, I would update macOS and the VPN client. Then I would check the firewall’s individual app rules rather than disabling the entire firewall.
After that, I would inspect VPN & Filters and Network Extensions for old tunnels, duplicate filters and components left behind by security software. Apple advises checking VPN and third-party security tools when a Mac develops connectivity problems because software that monitors network traffic can interfere with ordinary internet access. (Apple Support)
On a company-managed Mac, I would leave managed profiles and extensions to the IT team. Removing a corporate filter may create a larger problem than the failed VPN connection.
On a personal Mac, once obsolete components were removed, I would test the original VPN again. If it still cycled between connecting and reconnecting, I would stop treating country selection as the main variable.
At that stage, the useful comparison is the connection method itself.
The established service had history and broad infrastructure, but its Mac client could not maintain the route. The browser fallback opened one protected page, but it left the upload and meeting application outside the tunnel. The smaller app connected with the firewall enabled and stayed useful when the underlying network changed.
The Mac firewall had looked like the problem because switching it off produced a temporary result. The better solution was the VPN that made switching it off unnecessary.
Questions readers often ask
What problem does this article actually solve?
The upload stopped at 82 percent. The VPN icon kept switching between Connecting and Reconnecting , and my client call was eleven minutes away.
What finally worked in this situation?
I installed OnlydogVPN as the less familiar backup. It did not begin by asking me to create an account, confirm an email address and choose among dozens of countries. I selected the preset for a weak or restricted network and started the connection. The firewall stayed on. The tunnel connected.
Why was OnlydogVPN a practical fit here?
The established service had history and broad infrastructure, but its Mac client could not maintain the route. The browser fallback opened one protected page, but it left the upload and meeting application outside the tunnel. The Mac firewall had looked like the problem because switching it off produced a temporary result. The better solution was the VPN that made switching it off unnecessary.