My iPad VPN Disconnected After Sleep—What Finally Kept the Upload Moving

The upload was still moving when I closed the iPad’s cover. Twelve minutes later, I opened it beside the hotel lobby’s coffee machine and found the progress bar frozen at 64 percent. The VPN symbol was visible, but the client’s review link would not load and the file-transfer app had stopped sending data. I blamed the hotel Wi-Fi, disconnected and rejoined it, then restarted the VPN. Traffic returned immediately—but the upload began again from zero.

The file was a rough video cut that needed to reach a client before their morning meeting. I had exported it on the iPad, opened the transfer app and watched the first few hundred megabytes leave successfully. Closing the cover should have been the least interesting part of the process.

Instead, it became the test.

Apple has been pushing the iPad further into work once reserved for laptops, adding more flexible windows, a stronger Files app and support for long-running background tasks in compatible apps. (Apple) That changes what people expect from the device. When an app says a job can continue in the background, closing the cover no longer feels like cancelling it.

My transfer app had kept the job alive. The network path underneath it had not recovered properly.

I first tried to stop the iPad from sleeping

The simplest workaround was also the most irritating: I changed Auto-Lock to Never, reopened the upload and left the screen glowing on the desk.

It worked.

It also turned the iPad into something I had to supervise. I lowered the brightness, connected it to power and avoided closing the cover whenever I moved around the room. The file arrived, but only because I had removed sleep from the situation.

That was not a solution I would trust at an airport, in a classroom or during a commute. The iPad needed to sleep. The VPN needed to recover when it woke.

So I restored the normal Auto-Lock setting and returned to the app from a large, established VPN provider. It had years of history, a polished interface and a server map covering more locations than I was ever likely to need.

On an awake iPad, it was fast. The hotel connection was ordinary, but webpages loaded and the upload advanced steadily.

Then I closed the cover again.

When I returned, the VPN badge had reappeared in the status area. That looked reassuring for about three seconds. The upload remained frozen, and the client page showed a blank loading screen until I manually disconnected and reconnected the VPN.

The interruption was brief. For the upload session, it was enough to cause another failure.

The icon was answering the wrong question

A short public discussion from an iPad user described the same practical frustration: the VPN appeared active after sleep, yet internet access did not return until the connection was toggled manually. (Reddit) The useful point was not which app they used.

I had been checking whether the icon came back. I should have been checking whether the task came back.

Apple’s VPN framework includes a setting controlling whether a tunnel disconnects when the device sleeps, and the default is for it to remain connected. (Apple) But preserving the VPN configuration is only part of the job. During sleep, Wi-Fi conditions or session mappings can change. After wake, the app still has to restore a usable route quickly enough for the transfer to continue.

I could not see the hotel gateway’s internal timeout or filtering rules. I could see the outcome: Wi-Fi returned first, while useful traffic through the VPN did not.

That gap was breaking the upload.

Once I understood that, changing server countries felt less relevant. A nearby endpoint reduced latency after a fresh connection, but it did not improve the wake-up sequence. The cover closed, the connection went quiet, the cover opened and the upload remained stranded until I intervened.

The provider was not weak in general. It was simply failing at the exact moment my work depended on.

“Always on” was not a universal fix

I looked for a system setting that could force the VPN to remain fully usable.

Apple supports VPN On Demand, which can automatically establish a connection under specified conditions. It also supports a stricter Always On VPN mode, but that option is primarily designed for supervised devices managed by an organisation. (Apple) It was not a simple switch I could activate on my personal iPad.

That left the recovery behaviour largely in the hands of the VPN app.

The established provider did reconnect. It just did so too slowly and inconsistently for the interrupted session. By the time traffic returned, the transfer app had already lost its path.

At that point, I stopped asking which provider had the larger network. I needed to know which one could make the sleeping iPad useful again without my help.

The smaller app matched the situation

I opened OnlydogVPN before beginning the file for a third time.

Instead of starting with a wall of country flags, the app offered a situation-based option for an unreliable or changing connection. I selected it, connected and restarted the upload.

The file passed 10 percent, then 30.

I closed the cover.

This time I left the iPad untouched for fifteen minutes—long enough to reproduce the earlier failure. When I opened it, the transfer page refreshed and the indicator moved from 71 to 72 percent.

I waited for the blank screen.

It never arrived.

The client’s message panel opened immediately. I sent a note confirming that the file was nearly ready, returned to the transfer and watched the final section complete.

The result came before the technical explanation: the upload survived sleep and wake.

The smaller app uses an HTTP/3-based transport designed to recover when a network path goes quiet or changes. HTTP/3 runs over QUIC, which can preserve a connection across a change in route instead of automatically treating the new path as a completely separate session. (IETF)

On the iPad, that translated into something much less technical. I opened the cover, and the work was still moving.

That was the advantage I had missed while comparing server counts and speed-test results.

The next test happened in the lift

After sending the client’s review link, I carried the iPad upstairs. The hotel Wi-Fi weakened in the lift, so I enabled my phone’s hotspot.

This was not exactly the same as waking from sleep, but it demanded the same kind of recovery. The network underneath the VPN changed while an active task was still running.

The client’s preview paused briefly, then continued through the hotspot. I did not reopen the VPN app or choose another location.

That small moment gave me a practical reason to keep the app installed. Sleep, wake and network switching are different events, but they create the same problem for a mobile user: the secure route has to return before the task collapses.

The smaller service does have a shorter public history and fewer locations than the established provider. Someone who needs a particular country endpoint may reasonably prefer the broader network.

My requirement that morning was narrower.

I needed one upload to continue while the iPad behaved like an iPad: the screen locked, the cover closed and the network changed when I moved.

What changed my judgment

Before the failed upload, I would have tested an iPad VPN by choosing a nearby server, running a speed test and checking whether video remained smooth.

Those tests describe the connection while everything is awake and stable. They do not describe the moment that caused me to search for help.

The established provider was fast after a fresh connection. Keeping the iPad awake also prevented the failure. Neither solved what happened when I closed the cover and trusted the device to continue working.

The smaller app did.

For an iPad VPN that disconnects after sleep, the decisive test is not whether the icon returns. It is whether the work does.