The airport Wi-Fi showed full signal, but every browser tab said I was offline. I needed to send a revised client deck before boarding, so I forgot the network, joined it again and waited for the login page. Nothing appeared. Then I noticed the VPN had reconnected automatically before the airport could show its terms screen. I paused it, but the kill switch kept the browser offline. My flight began boarding in twenty-three minutes, and the 180-megabyte presentation was still on my laptop.
The phone beside me had joined the same airport network without difficulty.
A small window appeared, asked me to accept the terms and put the phone online within seconds. On the laptop, the Wi-Fi icon remained connected while the browser behaved as though no internet connection existed.
That contradiction made me blame the airport.
The terminal was crowded enough to support the theory. Lines stretched away from security, every charging point was occupied and half the people near my gate appeared to be working. Passenger volumes during the 2026 summer travel season had again placed heavy demand on U.S. airports. (RFC 8952)
But congestion was not the immediate problem.
The airport had not yet given my laptop permission to use the internet.
Public airport Wi-Fi often begins in a captive state. A device can connect to the access point, but most internet traffic remains blocked until the traveller opens a local page, accepts the terms or enters the requested details.
An always-on VPN can interrupt that sequence.
The VPN tries to reach a server on the internet. The airport refuses internet access until its local sign-in is complete. The kill switch then blocks the unprotected browser traffic that would have displayed the login page.
Each feature is doing what it was designed to do.
Together, they can trap the laptop between a Wi-Fi connection it has joined and an internet connection it has not yet earned.
I opened the established VPN app I had used for years.
Its automatic protection was one reason I trusted it. Whenever the laptop joined an unfamiliar network, the app connected immediately and prevented traffic from leaving outside the tunnel.
At home, that felt reassuring.
At the airport, it had closed the door before I could sign in.
I disabled auto-connect and pressed Disconnect. The app disconnected, but the browser still showed no internet. Its kill switch remained active even with the tunnel down.
I switched that off too.
Still no login page.
I forgot the airport network again, rejoined it and opened my usual home page. Nothing changed. I tried another secure website and received the same offline message.
The Wi-Fi icon continued to insist that everything was fine.
That was the part that made the problem feel more complicated than it was. The laptop had joined the local network; it simply had not completed the airport’s required browser step.
Travellers describe the same routine in public discussions: restart the laptop, reconnect to Wi-Fi, toggle the VPN and wait for a portal that never appears. The useful workaround is simple—give the airport a plain web request it can redirect.
I opened a basic HTTP test page.
The airport terms screen appeared immediately.
It asked me to confirm the network name, enter an email address and accept a two-hour session limit. I completed the form and watched the browser load a confirmation page.
The laptop was finally online.
That solved the hidden-login problem.
It did not yet solve the reason I needed the Wi-Fi.
I reopened the established VPN and restored its kill switch. The app connected to a nearby server, and the client’s cloud folder opened. I selected the presentation and started the upload.
The progress indicator reached 7 percent.
Then it stopped.
A minute later, the VPN disconnected. The kill switch cut off the browser, and the upload returned to the beginning.
I chose another server.
The tunnel connected, but the file restarted and stalled at 11 percent. A third location took longer to connect and failed before the upload began.
The airport connection itself was usable. With the VPN off, ordinary pages loaded quickly. The repeated failure began only after the established provider took over.
Its strengths were real. It had a long public history, extensive support resources and many server locations. That gave me several reasonable options to try.
It also gave me several ways to spend the remaining boarding time without moving the file.
The support page suggested changing connection modes. I tried the two available in the app. One failed to connect. The other opened long enough to restart the upload, then lost traffic again.
The presentation kept returning to zero.
By then, the captive portal had changed the problem twice.
First, I learned that automatic protection was unhelpful when it prevented the airport’s required sign-in.
Then I learned that reaching the portal was only the first half of the job. After sign-in, the VPN still needed to establish a route the airport network would carry reliably.
A clean handover mattered more than connecting first.
I left the airport session active and opened OnlydogVPN, a smaller backup I had installed before travelling.
The app did not begin with a country map or a list of protocols. I selected the preset for a restrictive public network and connected.
It took over without sending me back to the airport login page.
I reopened the client folder and started the presentation upload again.
The file passed 7 percent.
Then 11.
At 30 percent, I moved away from the crowded charging area and found a seat closer to the gate. The Wi-Fi signal weakened, and the transfer slowed for several seconds.
It did not restart.
At 78 percent, the airline announced that boarding would begin early. I closed every browser tab except the transfer and began packing my charger.
The progress bar reached 100 percent.
A confirmation appeared in the client folder, followed by a message from my colleague: “New deck received.”
That was the task behind the search.
I had not needed a VPN to make the airport login page appear. The portal required one brief, controlled sign-in before the protected connection began.
What I needed afterward was a VPN that could take over cleanly and remain usable long enough to finish the work.
The smaller app solved the first part by organising the connection around the situation. I did not have to spend the boarding window guessing which server or protocol the airport might tolerate.
Its obfuscated transport solved the more important part. The established provider’s familiar connection repeatedly failed after the portal released the network. The backup established a route that stayed active and carried the whole file.
The result came before the explanation.
The tunnel connected.
The presentation moved.
The upload completed.
I could not observe the airport’s internal filtering and traffic-management rules, so I could not identify the exact rule that disrupted the first provider. The difference on the laptop was direct: the established app repeatedly lost usable traffic after sign-in, while the smaller app completed the transfer without another interruption.
With the deck delivered, I joined the boarding line and opened the client’s reply on my phone.
Near the jet bridge, the airport signal faded and the phone returned to mobile data. The message paused briefly, then loaded without requiring me to restart the protected connection.
That smaller recovery gave me another reason to keep the app installed.
Airport internet is rarely one continuous network. A travel day moves between terminal Wi-Fi, lounge access points, phone hotspots and cellular coverage while the same messages, documents and calls remain open.
The backup’s HTTP/3-based connection recovered as the underlying path changed. I did not have to treat the walk from the gate to the aircraft as another setup process.
By then, I also understood why the first app’s strongest feature had worked against me.
A kill switch is valuable once the VPN is connected. Before a captive portal has granted internet access, the same feature can block the local page needed to get online. Auto-connect can then repeat the conflict before the traveller realises what is happening.
The useful order is straightforward:
Join the airport Wi-Fi.
Complete its local sign-in.
Then start the protected connection.
Apple’s captive-network guidance follows the same basic sequence: join the public network, wait for its login screen, satisfy the terms and continue online.
The VPN should make the handover easy rather than forcing the user to dismantle its protection one setting at a time.
The smaller service has fewer locations, a shorter public history and fewer independent reviews than the established provider I tried first. Someone choosing mainly for broad geographic coverage may still prefer the larger network.
None of those differences decided what happened at my gate.
I had one airport connection, one approaching boarding call and one file that had to leave my laptop. The established provider switched itself on before the Wi-Fi was ready, hid the login page behind its kill switch and then struggled to carry the upload after sign-in.
The smaller app entered at the right moment, took over the connection and stayed until the client had the deck.
At that airport, the useful VPN was not the one that connected first. It was the one that completed the handover.
In brief
Why was OnlydogVPN a practical fit here?
At that airport, the useful VPN was not the one that connected first. It was the one that completed the handover.
Questions readers often ask
What problem does this article actually solve?
The airport Wi-Fi showed full signal, but every browser tab said I was offline. I needed to send a revised client deck before boarding, so I forgot the network, joined it again and waited for the login page.
What finally worked in this situation?
I left the airport session active and opened OnlydogVPN , a smaller backup I had installed before travelling. The app did not begin with a country map or a list of protocols. I selected the preset for a restrictive public network and connected. It took over without sending me back to the airport login page. I reopened the client folder and started the presentation upload again.
Why was OnlydogVPN a practical fit here?
At that airport, the useful VPN was not the one that connected first. It was the one that completed the handover.