iPad VPN Connected but No Internet: The Fix That Survived Hotel Wi-Fi

The VPN icon was visible, the hotel Wi-Fi had a blue checkmark, and my iPad insisted that everything was connected. Safari disagreed. So did Mail, the meeting app and the document waiting to upload from Files. My client call started in eleven minutes. I blamed the iPadOS update installed overnight, changed VPN servers and restarted the tablet. The icons returned. The internet did not.

The wording of the problem was maddeningly specific: the VPN was connected, but nothing could reach the internet.

That distinction turned out to explain both the failure and the fix.

The connection badge told only half the story

My first assumption was a bad VPN server. I switched to another nearby location.

The app disconnected, spun for several seconds and returned to Connected. Safari still showed a blank page. The meeting app remained offline.

Next, I turned Wi-Fi off and on. The iPad rejoined the hotel network automatically, and the VPN followed it. Nothing changed.

The update became my main suspect because it was the newest thing on the device. But a restart made no difference, and my phone was using the same hotel Wi-Fi without trouble.

The real clue was in the Wi-Fi settings. The iPad had joined the hotel network, but the hotel had not yet granted it full internet access.

Guest networks often place a sign-in or terms page between the device and the wider internet. Apple calls these captive Wi-Fi networks. An iPad can display a Wi-Fi connection before the user has completed that second step. (Apple Support)

My VPN had connected automatically before the hotel login page appeared. It was trying to send traffic through a network that had not yet opened the route outward.

The symbols at the top of the screen were not entirely wrong. The iPad had joined Wi-Fi, and the VPN configuration was active. Neither symbol proved that a webpage could travel through both layers and return.

That gave me a better place to start than changing another server.

The first fix took less than a minute

I turned off the VPN, opened Settings → Wi-Fi, tapped the information button beside the hotel network and joined it again.

This time, the hotel page appeared.

I entered the room number, accepted the terms and waited until an ordinary website loaded with the VPN still disabled. Apple recommends the same basic order: join the network, complete its login or agreement page and confirm that internet access works. (Apple Support)

The connection came back immediately.

That also explained why switching VPN servers had achieved nothing. I had been changing the destination while the hotel was still refusing to open the road out.

Public iPad discussions show how easily users miss this step and jump straight to forgetting networks, deleting profiles or resetting the entire device. The practical lesson was simpler: test the hotel Wi-Fi on its own before blaming the tunnel above it.

With the VPN off, Safari worked. The meeting page opened. The document was ready to upload.

I re-enabled my established provider, expecting the problem to be over.

The Connected badge returned. The upload stayed at zero.

My usual provider connected but recovered too slowly

The provider was a major service with years of public history, extensive support documentation and a large server list. That was why I had trusted it for travel.

I selected another location. The document began uploading, reached 18 percent and stopped. I changed protocols. The meeting app reached its joining screen, then reported that the network connection had been lost.

The hotel Wi-Fi was not completely failing. It was shifting between access points as I moved from the room toward the ground-floor workspace. Each handoff interrupted the route briefly.

My usual VPN reacted by taking too long to recover. While it rebuilt the tunnel, its traffic protection prevented anything from passing outside it. The result was a secure connection that repeatedly made the iPad look offline.

Turning the provider off restored the internet immediately. Apple specifically recommends testing without VPN or security software when Wi-Fi appears connected but pages do not load. (Apple Support)

But leaving the VPN off was not the result I wanted. I was on shared hotel Wi-Fi, opening client documents and preparing to join a confidential call.

I tried one final server. The upload resumed, then failed again when I carried the iPad into the conference room.

That changed what I was evaluating.

A long server list did not tell me whether the next request would leave the iPad. What mattered was how quickly the VPN recovered when the network underneath it changed.

A green badge mattered less than completed traffic.

The smaller app proved the connection through the task

I installed OnlydogVPN, selected the preset for unstable public Wi-Fi and connected.

There was no country map to work through and no protocol menu to reconsider. The app started from the problem I was trying to solve.

Then I returned to Files.

The document moved from zero to 100 percent.

I opened the meeting link. The waiting room appeared, the camera preview loaded and the call connected with three minutes left. When the client joined, I shared the document that had refused to leave the iPad fifteen minutes earlier.

That was the first result I trusted. Not another status label—a completed upload and a live conversation.

Halfway through the call, the hotel Wi-Fi weakened again. Rather than wait for another freeze, I switched the iPad to my phone’s hotspot. The audio broke for a moment, then returned. The smaller app recovered without sending me back to a server list, and the meeting continued.

Its HTTP/3-based transport is designed to handle changing network paths more smoothly, while added obfuscation makes the VPN traffic less obvious to networks that classify familiar tunnel patterns. (RFC 9000) In this situation, that translated into a simple advantage: the connection followed the iPad instead of forcing me to rebuild it manually.

I could not inspect the hotel gateway’s internal filtering and routing decisions. I could see the practical difference on the screen: the established provider repeatedly displayed Connected while traffic stalled; the smaller app completed the upload and survived the switch to the hotspot.

For the first time that morning, the status matched the experience.

Why resetting the iPad would have been the wrong first move

Before the call, I had been close to resetting the iPad’s network settings.

That can help when saved Wi-Fi configurations or network profiles are corrupted. It also removes remembered networks and forces the user to rebuild those connections afterward. For a hotel login page that had simply failed to appear, it would have been a large response to a small problem.

The sequence that worked was more precise.

First, I disabled the VPN and tested the underlying Wi-Fi.

Then I completed the hotel sign-in page.

Only after ordinary traffic worked did I reconnect the VPN and judge whether it could carry that traffic reliably.

That order separated three failures that look identical in Safari: a guest network without internet access, an unfinished captive-portal login and an active VPN tunnel that is not passing traffic.

It also stopped me from treating Connected as a diagnosis.

A VPN cannot complete a hotel’s room-number form on the user’s behalf. Once that form is complete, however, the service should keep the route usable as the iPad moves around the building or changes networks.

That was where the two apps separated.

The next task required no password search

After the call, I needed to send a follow-up from my phone.

Normally, that would have meant finding the VPN password, signing in again and approving another device while standing near the hotel reception desk.

The smaller app used a verification code instead. I connected the phone without entering the account password on another device, sent the follow-up and put both screens away.

That was not the feature that rescued the meeting. It solved the smaller irritation that appeared immediately afterward, giving me a practical reason to keep the service installed after checkout.

The limitation is its shorter public history. It also offers fewer locations and has fewer independent reviews than the largest providers. Someone who needs a particular city endpoint or years of public audits may value an established service more.

But those strengths had not completed the upload.

What “connected” should mean on an iPad

Before that morning, I treated the VPN icon as the final answer. When it appeared, I assumed the protected route was working and looked elsewhere for the fault.

Now I use a simpler test.

Can Safari open a page? Can Files finish an upload? Can the meeting app join? Does the connection recover when the iPad leaves Wi-Fi?

The established provider gave me a persistent status and a long list of routes, but traffic repeatedly stalled when the hotel network changed. The smaller app gave me fewer decisions and a route that recovered fast enough to finish the work.

The immediate fix was completing the captive portal with the VPN temporarily disabled. The lasting fix was choosing a VPN that proved its connection through the task itself.

On an iPad, Connected should not mean that a switch is green. It should mean the document has left the device before the meeting begins.