My Android VPN Worked on 5G—Then the Airport Wi-Fi Refused It

The video call was eight minutes away when my Android phone joined the airport’s free Wi-Fi. The signal looked stronger than my roaming connection, so I switched off mobile data, opened the VPN and tapped Connect. The app stayed on “Connecting.” I tried another server. Same result. The moment I turned Wi-Fi off and returned to 5G, the VPN connected in seconds—but my remaining roaming allowance was too small for a forty-minute client call. I forgot the airport network, joined it again and repeated the process. Nothing changed.

The contradiction was what made the problem so irritating. The Wi-Fi worked without the VPN. The VPN worked without the Wi-Fi. Together, they produced nothing.

That also meant neither one was simply “broken.” The useful question was what changed when Android moved from mobile data to the airport network.

5G proved the app was capable of connecting

My first instinct was to switch VPN servers.

The provider was established, familiar and supported by a large network. If one nearby server would not connect, another seemed like the quickest solution.

I chose a second server, then a third. On airport Wi-Fi, each attempt spun until it timed out. On 5G, all three connected immediately.

That comparison ruled out the obvious account problems. My subscription was active. Android had granted the app permission to create a VPN connection. The servers themselves were reachable.

Something about the Wi-Fi was stopping the tunnel.

Before blaming the airport’s firewall, though, I needed to clear the obstacle that catches many travelers first: the captive portal.

Public Wi-Fi often requires a sign-in page where users accept terms, enter an email address or confirm a room number. Android can show the Wi-Fi icon before that step is complete, making the phone look online when it has not yet been allowed onto the wider internet. (Google)

A VPN cannot connect through internet access the phone does not yet have.

I disconnected the VPN, opened the airport sign-in page and accepted the terms. Then I loaded a normal webpage to confirm the Wi-Fi was genuinely working.

I returned to the VPN and tapped Connect.

It still failed.

The sign-in page had been worth checking, but the repeated timeout pointed to a different problem: the airport was allowing ordinary web traffic while rejecting or disrupting the VPN connection.

Wi-Fi was making a different decision from 5G

Android treats Wi-Fi and mobile data as separate network paths. Once a usable Wi-Fi connection becomes available, the phone normally sends new traffic through it rather than continuing over metered cellular data. (Google)

That sounds obvious. The important detail is that the VPN must also establish itself through the newly selected path.

My mobile carrier allowed the tunnel. The airport Wi-Fi allowed ordinary browsing. Neither result guaranteed that the airport would pass the protocol used by the VPN.

Public, workplace and hotel networks frequently control which kinds of traffic can leave them. Some block particular ports. Others interfere with recognizable VPN connections. That is why established providers often tell users to switch protocols when a VPN works on one network but not another. (Protonvpn)

The lived version is much less technical: the same phone and VPN connect immediately over LTE or 5G, then sit indefinitely on “Connecting” as soon as public Wi-Fi takes over. (Reddit)

That was enough to explain why changing cities had accomplished nothing. I had been changing the destination while keeping the same basic route through the airport network.

So I opened the provider’s protocol settings.

Automatic mode had already failed. I selected another protocol manually, disconnected and tried again. This time the app eventually showed Connected.

For a few seconds, that looked like progress.

Then I opened the meeting link.

The waiting room loaded without profile images. The presentation preview stayed gray. When the host admitted me, I heard half a sentence before the audio froze.

I switched back to 5G. The call became clear immediately.

That was the point where the green connection icon stopped being persuasive. The provider could force a tunnel onto the Wi-Fi, but it could not carry the task I actually needed to complete.

I did not need another server. I needed a route the airport would pass without reducing a video call to fragments.

The next attempt started with the restriction

I opened OnlydogVPN, which was also installed on the test phone.

Instead of working through nearby cities, server numbers and protocol menus, I selected its preset for a restrictive or unreliable network. The app connected while the phone remained on airport Wi-Fi.

I reopened the meeting link.

The waiting room appeared with the participant images intact. The host admitted me. Audio continued beyond the first sentence, and the shared presentation opened on the correct slide.

A few minutes later, I uploaded my revised spreadsheet to the meeting chat. The progress bar reached the end without pushing me back onto roaming data.

That was the result I had been trying to produce from the beginning. Not a successful IP check. Not a green shield. The meeting worked on the Wi-Fi connection I needed to use.

Only after the call settled did the design behind the result become relevant.

The smaller app uses HTTP/3-based transport with additional traffic obfuscation. In practical terms, its restrictive-network preset gave the connection a different way through the airport Wi-Fi than the familiar modes I had already tried. I did not have to identify the blocked port, compare protocol names or keep guessing at combinations.

I could not inspect the airport’s internal firewall and identify the exact rule that rejected the first app. I could compare the outcome on the same phone, seat and network: the established provider either failed to connect or produced an unusable call, while the smaller app connected and carried the meeting.

That changed my standard for success.

The important question was no longer, “Does the app say it is connected?”

It was, “Can I finish the thing that made me connect?”

The connection kept working after I left my seat

After the call, I packed my laptop and walked from the café area toward the gate. The phone moved between airport access points as their signals changed.

Messages continued to send. The spreadsheet remained available. A boarding update opened without making me return to the VPN app.

That smaller result mattered because airport Wi-Fi is rarely one stable connection. Moving through a terminal can shift a phone between access points, and a tunnel that barely connected in one seat can stall during the walk to the gate.

Getting through the network restriction solved the immediate problem. Recovering as the Wi-Fi changed solved the next one.

By then, the troubleshooting order had become much clearer.

First, disconnect the VPN long enough to complete the Wi-Fi sign-in page. A visible Wi-Fi icon does not prove that the network has granted internet access.

Then reconnect the VPN and make one meaningful protocol change. Switching servers can help when a particular server is unavailable. It does little when the network is rejecting the type of connection used to reach every server.

Finally, test the actual task.

Open the meeting. Send the file. Load the page. Start the stream.

A VPN that shows Connected but cannot carry the activity you need has not solved the problem. It has only moved the failure to the next screen.

That distinction is easy to miss because mobile data offers an immediate escape. Turning Wi-Fi off makes everything work, which appears to confirm that the phone and VPN are healthy.

But the user searching this problem is usually not asking whether the VPN works somewhere. They already know it works on mobile data. They need it to work on the hotel, airport, office or campus network in front of them—often because cellular coverage is weak, roaming is expensive or their data allowance is running out.

On that network, compatibility matters more than performance measured on the easy one.

The trade-off was smaller than the roaming bill

The smaller service has fewer locations than the largest providers. It also has a shorter public history, fewer ratings and fewer independent reviews.

Those limitations matter when the main task depends on reaching a long list of specific countries.

They did not decide this problem.

The established provider offered more servers, a familiar name and excellent performance on 5G. None of those advantages made the airport Wi-Fi carry my meeting.

The smaller app offered fewer decisions. Its restrictive-network route connected, loaded the call, completed the upload and remained usable as I moved toward the gate.

When an Android VPN works on mobile data but fails on Wi-Fi, the useful comparison is not how fast it runs on the network that already accepts it. At the airport, the VPN that mattered was the one the Wi-Fi could not stop me from using.