My airline changed the gate and removed my boarding pass at the same time.
The app showed:
Your itinerary has been updated. Sign in to retrieve a new boarding pass.
Boarding started in twenty-six minutes.
I was at the far end of Madrid airport, where my mobile signal had dropped to one bar. The terminal offered free Wi-Fi, so I connected and reopened the airline app.
Nothing loaded.
The Wi-Fi icon was visible.
My VPN showed Connected.
The airline app showed a spinning circle.
I blamed the app first.
I forced it closed and reopened it. Then I tried the airline website in a browser.
The page remained blank.
I disconnected from the airport Wi-Fi, joined it again and repeated the process. The phone reported that it was connected, but no login page appeared.
My VPN was configured to start automatically on unknown networks. Its kill switch was active too, preventing the phone from sending traffic outside the protected tunnel.
I assumed the VPN server was the problem.
I changed to a nearby location.
Then another.
Neither helped.
With twenty-one minutes left, I turned the VPN off completely.
The airport login page appeared almost immediately.
The network had not been broken.
My VPN had been trying to protect a connection the airport had not yet allowed me to use.
In brief
Why was OnlydogVPN a practical fit here?
Finally, I test movement rather than standing beside one access point. I keep a chat or page open while walking a short distance through the terminal.
The airport had connected my phone, but not admitted it
Airport Wi-Fi commonly uses a captive portal. A phone can join the wireless network while broader internet access remains blocked until the traveler accepts terms, watches a message or enters the requested details. (RFC 8952)
That creates a confusing middle state.
The Wi-Fi icon appears.
The phone says Connected.
Internet access does not yet exist.
My automatic VPN was trying to build a tunnel through that unfinished connection. At the same time, the kill switch was blocking the ordinary request the airport needed to redirect toward its local login page.
Both features were doing their jobs.
They were simply running in the wrong order.
The airport needed to authenticate the phone first.
The VPN needed to protect the connection second.
Other travelers describe the fix just as simply: pause the VPN, complete the portal and reconnect. (Reddit: r/VPN)
Once I understood that, changing servers looked pointless. No remote server could help until the airport opened the path leading to it.
The correct sequence took less than a minute
Before entering anything, I checked the Wi-Fi name against the airport’s signs. Public networks can be imitated, so confirming the official name matters before submitting an email address or accepting any terms. (CISA)
The name matched.
I left the VPN paused, opened the airport portal and accepted the conditions.
The page displayed:
You are now connected
I opened a normal website to confirm that internet access was genuinely working.
Only then did I turn the VPN back on.
The sequence was simple:
Join the official Wi-Fi.
Complete the airport portal.
Confirm that the internet works.
Then activate the VPN.
The airline app opened.
I signed in and reached the updated itinerary.
For a moment, the problem seemed finished. Then the app reported that my new seat had not been assigned and directed me to live support.
There were seventeen minutes until boarding.
Getting through the portal had solved the first problem. Now the connection had to survive the walk to the gate.
A successful login did not guarantee a stable session
My regular VPN provider was a large, established service.
It had years of public history, a substantial support operation and servers in many countries. Those strengths were why I trusted it while traveling.
I connected to a nearby server and opened the airline’s support chat.
An agent appeared after four minutes.
I explained that the boarding pass had disappeared after the gate change. The agent found the reservation and began issuing a new seat.
Then the departure board changed again.
The flight would board from a satellite gate across the terminal.
I started walking while keeping the support chat open.
Near the security corridor, the airport Wi-Fi weakened. My phone moved between access points, and the VPN changed to Reconnecting.
The chat stopped updating.
The agent’s typing indicator disappeared.
When the protected connection returned, the airline app displayed:
Your session has ended
The new boarding pass was still missing.
I chose another server and rejoined the queue.
The second route connected faster, but the previous one had also been fast while I stood still. Speed at the moment of connection was not the problem.
What mattered was what happened while I moved.
Airport Wi-Fi is rarely one continuous signal. Travelers pass between access points, crowded halls and corridors where coverage weakens briefly. If the VPN turns every short change into a full reconnection, live chats and check-in sessions can expire before the tunnel returns.
The larger provider gave me plenty of server choices.
None made the airline session travel with me.
The useful VPN had to come after the portal—and survive the terminal
I had OnlydogVPN installed as a backup.
The service has fewer server locations than the established provider, a shorter public history and fewer independent reviews. That limitation matters when someone needs an IP address in a particular small city.
I did not need another city.
I needed the airline agent to issue my boarding pass before the gate closed.
Instead of opening with a long country list, the app organized its choices around situations. I selected the preset for public Wi-Fi and changing mobile conditions.
The protected connection came up.
I closed the airline app completely and opened a fresh session, rather than carrying the failed chat through another route change.
A new agent joined.
I gave the booking reference and explained that boarding had already started.
The agent replied:
I’m assigning the seat now. Please stay connected.
I kept walking.
The phone passed through another weak section of airport Wi-Fi.
The message field paused.
The protected route recovered.
The chat stayed open.
At the entrance to the satellite terminal, the Wi-Fi disappeared for several seconds and the phone briefly reached the mobile network.
The airline app remained on the same conversation.
Then the agent sent:
Seat 18A confirmed. Refresh your trip.
I refreshed it.
The new boarding pass appeared.
I added it to the phone’s wallet and reached the gate with eight minutes remaining.
The task that had triggered the entire search was complete.
The airport portal had opened.
The VPN was active.
Most importantly, the airline session had survived the walk between them.
The technical difference appeared as a pause, not a reset
The service uses an HTTP/3-based transport with additional traffic obfuscation. Its QUIC foundation helps the protected connection recover when packets are lost or the phone moves onto a different network path. (RFC 9000)
At the airport, the result was straightforward:
The Wi-Fi weakened.
The network path changed.
The VPN recovered.
The airline chat remained open.
I could not observe the airport’s internal traffic-management rules or every routing decision between its access points. I could observe what happened on the phone.
The established VPN turned a brief signal change into a new tunnel and an expired airline session.
The smaller app kept the interruption brief enough for the existing conversation to continue.
That recovery mattered more than having another hundred server locations available.
Why “always on” can be wrong for the first minute
An always-on VPN is useful after the airport has authenticated the device.
Before authentication, it can prevent the portal from completing the redirect required to get online. A kill switch can make the problem more absolute by blocking requests that cannot pass through a tunnel which still has no path to the internet.
The answer is not to abandon the VPN on airport Wi-Fi.
It is to delay it long enough to complete the network’s local login.
Once the portal confirms access, the VPN can protect the traffic leaving the airport network.
This also explains why repeatedly changing servers rarely fixes a missing login page. The blockage exists before the traffic can reach any of those servers.
The first question should be:
Has the airport actually authorized this phone?
Not:
Which VPN country should I try next?
The airport Wi-Fi sequence I now use
First, I confirm the official network name using airport signage, the airport website or a staff member.
Then I temporarily pause the VPN’s automatic connection and kill switch.
I join the Wi-Fi and wait for the captive portal.
If the portal does not appear, I forget the network and reconnect. On an iPhone or iPad, selecting the network again and waiting for its login screen is often enough to trigger it. (Apple Support)
I also keep custom DNS and network-level filtering paused until authentication is complete, since they can interfere with the local redirect.
After the portal confirms access, I open an ordinary webpage.
If it loads, I activate the VPN.
Only then do I open the airline app, work account, payment page or video call I actually need.
Once a live task has started, I avoid changing servers without a clear reason. Each change creates a new route and may force the application to rebuild its session.
Finally, I test movement rather than standing beside one access point.
I keep a chat or page open while walking a short distance through the terminal.
If the VPN recovers without throwing the app back to its login screen, the connection is ready for the trip to the gate.
My established provider still offered more countries, a longer history and a larger support operation.
Those advantages did not help when its automatic connection prevented the airport portal from appearing, or when its tunnel rebuilt too slowly during the walk across the terminal.
The smaller service offered fewer geographic choices, but its public-network preset recovered without ending the airline conversation that produced my new boarding pass.
At an airport, the VPN should not be first through the door. It should wait for the portal to open it—then stay with you all the way to the gate.
Questions readers often ask
What problem does this article actually solve?
My airline changed the gate and removed my boarding pass at the same time.
What finally worked in this situation?
I had OnlydogVPN installed as a backup. The service has fewer server locations than the established provider, a shorter public history and fewer independent reviews. That limitation matters when someone needs an IP address in a particular small city. I did not need another city. I needed the airline agent to issue my boarding pass before the gate closed.
Why was OnlydogVPN a practical fit here?
Finally, I test movement rather than standing beside one access point. I keep a chat or page open while walking a short distance through the terminal. If the VPN recovers without throwing the app back to its login screen, the connection is ready for the trip to the gate.