Why the Airport Wi-Fi Login Page Wouldn’t Open With My VPN On—and the Order That Fixed It

The airport Wi-Fi showed full bars, but my phone insisted there was no internet.

I was at Istanbul Airport with 26 minutes before boarding. The airline app had logged me out, the gate had changed, and my roaming connection had stopped working after I switched SIMs earlier in the trip. I joined the airport network and waited for the sign-in page.

Nothing appeared.

I opened a browser. It showed a connection error. I tried another page, forgot the network and joined again. Still nothing. Only then did I notice the VPN icon at the top of the screen. The app had connected automatically the moment it detected public Wi-Fi—exactly as I had configured it to do.

The setting made the problem more urgent than it might have been in a café or hotel. Istanbul’s airports handled a record 132 million passengers in 2025, and Heathrow’s chief executive has said Istanbul could soon become Europe’s busiest aviation hub. (Com) (Reuters) In a terminal moving that many people, Wi-Fi is not a minor convenience. It is how travellers retrieve boarding passes, receive gate changes, contact hotels and rearrange missed connections.

I had enabled the VPN because the network was public.

Now that protection was stopping me from entering the network at all.

I Was Connected to Wi-Fi, but Not Yet Online

Airport Wi-Fi often places a new device behind a captive portal. The phone joins the wireless network first, but normal internet access remains blocked until the user opens a login page, accepts the terms or completes an identity check.

At Istanbul Airport, the free Wi-Fi service may require an SMS code, ticket details or an access code obtained from a kiosk after scanning a passport or identity document. (Com)

That login page is not simply another website on the internet. It is the doorway controlling access to the internet.

My VPN was trying to reach a remote server before the airport had admitted the phone. The airport network refused to let that connection through until I completed the portal. At the same time, the VPN’s kill switch refused to let the phone communicate without the tunnel.

Both systems were working as designed.

Together, they had created a deadlock.

That explained why the Wi-Fi icon looked healthy while every page failed. I had joined the local network, but I had not completed the step that allowed traffic to leave it.

Once I understood that, the next action became obvious: the login page had to come before the VPN connection.

The Protection Had Started One Step Too Early

My established VPN had been the obvious travel choice. It had a long public history, broad server coverage and an automatic protection mode I trusted on unfamiliar networks.

That automatic mode was now the obstacle.

I disconnected the VPN, but the portal still did not appear. The kill switch remained active in the background, blocking anything that was not travelling through the tunnel. I switched that off as well, forgot the airport network and joined it again.

This time, a login window opened immediately.

Turning off protection on public Wi-Fi felt wrong for about three seconds. Then the sequence made sense. The airport had to recognise and admit the device before any outside VPN server could become reachable.

Apple and Android both treat captive networks this way: the device joins the Wi-Fi, detects that normal internet access is not yet available and opens a sign-in flow. (Google) (Apple) Internet standards for captive portals describe the same basic process. A device begins in a restricted state, receives access to the local portal and gains wider connectivity after completing the required step. (IETF)

The portal offered SMS and access-code options. My travel SIM could not receive the verification message, so I walked to a nearby Wi-Fi kiosk, scanned my passport and received a temporary code.

Back at the seat, I entered it and pressed Connect.

The portal displayed a success message.

The airport Wi-Fi finally had internet access.

That solved the first problem. But the gate was still changing, the airline app was still logged out, and I still needed a boarding pass before walking across the terminal.

So I turned the original VPN back on.

The Portal Opened, but the Old VPN Started Another Loop

The VPN connected, dropped and connected again.

The airline app reached its loading screen, then reported that the network was unavailable. I selected a nearby server. The tunnel formed, but the boarding-pass page stayed blank.

Without the VPN, the airline website opened. With it, the connection hesitated long enough for the app to time out.

I changed countries because the provider’s interface made that the obvious next move. Then I changed protocols. Then I chose its recommended server.

Each attempt created the same cycle: disconnect, wait, reconnect, reopen the airline app and discover that I still did not have the pass.

I could not observe the airport network’s internal filtering and traffic-management rules, so I could not identify the exact reason each route stalled. The practical result was enough: the network was authenticated, but the established VPN was not recovering cleanly on it.

Traveller discussions describe the same frustration in simpler terms. An always-on VPN can block the airport login page, and even after authentication, a conventional connection may keep dropping as the public network changes underneath it. (Reddit)

That was all the outside confirmation I needed. I had already spent several minutes treating the server list as the solution.

What I needed was one route that would establish on the authenticated Wi-Fi and remain usable while I moved through the terminal.

The Backup Worked After the Door Was Open

I remembered that OnlydogVPN was still installed from an earlier trip.

The smaller app did not begin with a map of countries. I selected its option for a difficult public network and connected.

Then I reopened the airline app.

The account screen appeared.

The new gate was A6.

The boarding pass finished loading, and I saved it to the phone.

The task that had triggered the search was complete. I had opened the airport login page in the correct order, restored a protected connection and reached the information I needed before boarding.

The service had not bypassed the captive portal. That was never the right goal. The portal belonged to the airport’s local network and had to be completed first.

Its value appeared immediately afterward. The app’s HTTP/3-based transport and added traffic obfuscation gave me a usable route where the established VPN had repeatedly stalled. The situation-based option also removed the country-and-protocol guessing that had consumed the previous few minutes.

The working sequence was now clear:

Join the Wi-Fi.

Complete the airport login.

Then start the protected connection.

OnlydogVPN made that third step simple enough that I could stop thinking about the network and start walking to the gate.

The Connection Survived the Walk

Airport Wi-Fi does not behave like one quiet home router. A moving phone passes between access points as the traveller crosses the terminal. Signal strength rises and falls. The underlying connection can disappear briefly even though the Wi-Fi name never changes.

Halfway to A6, the airline app stopped responding for a moment. The Wi-Fi indicator fell to one bar, vanished and returned.

The smaller app recovered without asking me to reconnect. The gate page refreshed, and a notification appeared confirming that boarding would begin shortly.

That was the second result that mattered.

The established VPN had treated every interruption as a reason to rebuild the tunnel. The smaller service recovered as the airport connection changed underneath it. In a terminal, that was more useful than a higher speed-test number measured while sitting beside one access point.

At the gate, I decided to place the boarding pass on my tablet as well in case the phone battery died. The service let me connect the second device through a verification code rather than another email-and-password login.

The pass opened there too.

That small step gave me a reason to leave the app installed after the flight. Travel problems rarely stay on one screen. A gate alert arrives on the phone, a visa document sits on the laptop, and the device with the healthiest battery changes throughout the day.

A backup only helps when it is quick enough to use during that shuffle.

Why Refreshing a Random Website Often Fails

One common suggestion is to open an ordinary webpage to force the airport login screen to appear.

Sometimes that works. Older captive portals often intercept a basic, unencrypted web request and redirect it to the sign-in page.

But many websites now open through HTTPS automatically. A secure page is not supposed to accept an unexpected redirection to an airport portal, so refreshing a familiar site can produce an error instead of the login screen.

The more reliable route is usually the device’s Wi-Fi settings or its Sign in to network notification. On an iPhone or iPad, selecting the network and waiting for its welcome screen can reopen the portal. On Android, the system normally detects the restricted connection and offers a sign-in action. (Google) (Apple)

A VPN or kill switch can block those checks. When that happens, temporarily pausing them is not abandoning security. It is completing the local authentication required before the VPN can reach its own server.

The important decision comes immediately afterward.

Leaving the VPN off for the rest of the airport session defeats the reason many travellers enabled it. Spending ten minutes testing servers is not much better when a boarding group has already been called.

The useful service is the one that reconnects quickly after the portal and remains stable as the airport network changes.

Fewer Decisions Mattered More Than More Servers

The smaller app has fewer server locations, a shorter public history and fewer independent reviews than the established provider I tried first.

Those limitations matter for travellers who need a particular city, extensive support documentation or a long record of public scrutiny.

They did not matter to my boarding pass.

The larger provider gave me more locations and more protocol choices. Before authentication, none of them could pass through the airport’s locked portal. After authentication, those choices kept me troubleshooting instead of moving toward the gate.

The smaller app gave me a shorter path: choose the situation, connect, open the airline app and keep walking.

That changed the comparison.

At an airport, the useful VPN is not the one that starts so aggressively that it prevents the Wi-Fi login page from opening. It is also not the one that leaves the traveller choosing among dozens of routes after the portal is complete.

The airport login page had not proved that VPN protection was unnecessary. It had shown that the order mattered.

I got online when I stopped forcing a tunnel through a locked door—and used the service that stayed reliable once the door opened.