VPN Problems with Hotel and Airport Wi-Fi Login Pages

You arrive at the hotel, join the Wi-Fi, switch on your VPN, and nothing happens. The browser spins, the VPN app says connecting, and the login page the hotel promised never appears. Or you sign in, the page says you are online, and a minute later the VPN drops and the internet seems dead. Hotels, airports, trains, malls, universities and cafes all use the same mechanism, called a captive portal, and VPNs and portals do not get along unless you give them the right order.

This article is about that exact conflict. It explains what a captive portal does, why a VPN trips over it, the order that works nearly every time, what to do when the page does not show up, and how to keep a session alive. It is not about general hotel Wi-Fi safety; for that see how to use a VPN on hotel Wi-Fi safely and staying safer on public Wi-Fi.

What a captive portal does

When you join an open or shared Wi-Fi network, your device receives an address and a way to reach the internet. A network with a captive portal quietly refuses to forward your traffic until you authenticate. Instead, it redirects the first web request you make to its own page, which asks you to accept terms, enter a room number and surname, type a voucher code, watch an advert or pay.

Behind the scenes, three tricks make this work:

• Redirects. The first plain web request, usually to an ordinary http address, is answered with a redirect to the portal page.
• DNS answers. Until you log in, the network may answer name lookups with its own address, so every site name leads to the portal. For background see the Cloudflare explanation of DNS.
• Blocked traffic. Anything else, including encrypted connections to unknown servers, is dropped or reset.

After you sign in, the network remembers your device, often by its hardware address, and allows traffic for a set time. That session can end after a few hours, at checkout or when you reconnect to the network.

Phones and laptops include a small test: after joining Wi-Fi, they request a known address and see whether the answer is what they expect. If not, they show a "sign in to network" notice or open a mini-browser. That feature is why portals sometimes pop up on their own.

Why a VPN trips over it

A VPN works by connecting to its server and carrying everything through that connection. On a captive network, the connection to the VPN server is exactly the kind of traffic the portal drops. So the order of events matters.

What you did	What happens	Result
VPN on first, then join Wi-Fi	VPN tries to connect before the network allows it	Spinner, then error
VPN with auto-connect or always-on	It retries again and again in the background	Portal popup may be blocked or confused
VPN with a kill switch	Blocks everything outside the tunnel, including the portal page	Login page cannot load at all
VPN on, trying to open the portal in a browser	Portal request goes into the tunnel, which is not up	Blank page or timeout
Portal first, then VPN	Network allows traffic, tunnel connects	Works

In addition, some portals use encrypted pages with certificates that your browser warns about. Do not click through serious warnings for a page that asks for payment or passwords. A plain "accept terms" page is different from a page that wants card details.

The order that works almost every time

Follow these steps in order. They take about a minute.

1. Turn the VPN off or disconnect it. If the app has an auto-connect or always-on option, pause it for this step.
2. Join the Wi-Fi network. Confirm the exact network name with staff first, since copycat networks with similar names exist.
3. Wait for the sign-in prompt. On a phone, a notification such as "sign in to network" may appear. On a laptop, a window may open on its own.
4. If nothing appears, open the browser and go to a plain http address (not https). The portal redirect works on plain pages. Avoid sites you have visited a lot, because the browser may load them from its cache or force https.
5. Complete the login. Enter only what the page asks for, typically a room number and surname, a code or a tick for terms.
6. Test normal browsing. Open a couple of ordinary sites. If they load, the network is open to you.
7. Connect the VPN. Pick your location, connect and wait for the connected status.
8. Check that it works. Open a page and your usual apps. If anything seems stuck, see VPN connected but no internet.

If you do this at the start of every stay, it becomes a habit. The guide to connecting to a VPN on public Wi-Fi shows the same flow in a printable checklist style.

When the login page will not appear

This is the most common frustration. Work through these fixes in order.

Turn the VPN and any private DNS off. A VPN, a private DNS setting or a secure browsing feature can all prevent the redirect. Try again with only plain Wi-Fi.

Forget and rejoin the network. Delete the network from the saved list, then join again. This resets the check your device does.

Use an http address. Browsers prefer https, which a portal cannot redirect without a certificate warning. Type "http://" in front of a plain address, or use the router address if the hotel gave it to you.

Turn off mobile data on the phone for a minute. Some phones decide the Wi-Fi has no internet and silently use mobile data, which hides the portal prompt. After the portal, you can turn it back on.

Disable the browser's secure-DNS feature temporarily. If the browser asks its own DNS server, it skips the portal's answers. After login, re-enable it.

Try another browser or a private window. A stored redirect or cached page can block the portal.

Ask the front desk. Some hotels give out a per-room code or put the portal on a different page, and some require registering each device.

If none of this works, switch to mobile data for the VPN and use the hotel Wi-Fi only for devices that do not need protection, such as a TV.

Keeping the session alive

Even after a good start, portal sessions end. You might see this as sudden internet loss with the VPN still showing connected, or as the VPN dropping and failing to reconnect.

• Check for expiry. Portals often limit sessions to a number of hours, until midnight or until checkout.
• Disconnect the VPN, then sign in again. The portal page may need the plain connection again.
• Set the portal to remember the device if it has a checkbox, and use the same device name.
• Beware of MAC address changes. Some phones use a different private address per network or after some time. If a portal remembers hardware addresses, a change can force a new login. Keep that setting stable for the network you use all week.
• Avoid joining a second device to the same room code if the hotel limits the number of devices. Some portals count a VPN reconnect as a new session.

If a session keeps ending, move the work onto mobile data for important tasks. Read about the kill switch in what a VPN kill switch is, because a kill switch can make every portal expiry look like a total outage.

Special cases: planes, trains, campuses and conferences

In-flight Wi-Fi. Planes use portals as well, often with a voucher or a paid plan. Sign in without the VPN, then connect it. Speeds and latency can be limited, and the VPN will feel slower, so choose what to send.

Trains and buses. Moving vehicles switch between mobile towers, and portals may time out at each change. If the VPN drops often, reconnect after each hand-over and keep the app allowed to run in the background.

University or workplace guest networks. These may require a registration or login with an account. Some block VPN traffic altogether as a matter of policy. If the VPN will not connect after a proper login, ask the network staff what is allowed. Do not try tricks to defeat a network's rules.

Conferences and large venues. Many people share one access point, so the portal can be slow, and the VPN may time out while connecting. Try again after a minute, or use mobile data.

Smart TVs and streaming sticks in hotels. These devices cannot always show portal pages. Hotels sometimes use special casting systems. Follow the hotel's own instructions, and do not expect a VPN on the TV to fix a portal problem.

Staying safe while you sign in

The portal step happens before the VPN is up, so it is a moment worth a little care.

• Confirm the network name with staff.
• Keep the sign-in short. Never enter banking or email passwords on a portal page.
• Check that the page looks like a normal hotel or airport page and does not ask for unusual details.
• Do not install a "required" app or profile from a portal page.
• Connect the VPN as soon as the portal allows traffic, before opening mail or banking.

The US Federal Trade Commission explains the risks of public Wi-Fi networks, and the Cloudflare piece on HTTPS shows why encrypted pages still matter even on shared networks. A VPN does not tell you whether a portal page is genuine; it only protects traffic after the tunnel is up. You can read more in what a VPN cannot protect you from.

Scenarios

A hotel guest in the evening. Mei joins the hotel network with her VPN set to auto-connect. The VPN spins and the portal never appears. She disconnects the VPN, forgets the network, rejoins, and the sign-in page appears at once. She enters her room number, then connects the VPN and goes on with email. Next time she pauses the auto-connect before joining.

A traveller at a gate. Tom's phone shows "no internet" on airport Wi-Fi. He opens the browser, types a plain http address, and gets the airport's terms page. After tapping accept and connecting the VPN, everything works. Forty minutes later the session ends and the VPN drops. He disconnects, accepts the terms again and reconnects.

A remote worker in a campus guest network. Ravi cannot connect the VPN even after the portal login. The campus network says personal VPN use is not allowed on guest Wi-Fi. He switches to his phone hotspot for work and leaves the guest network for casual use. The rule is the venue's choice, so he follows it.

Summary

A captive portal makes the network refuse almost everything until you sign in, and a VPN that tries to connect first, or a kill switch that blocks the plain connection, stops the sign-in page from appearing. The reliable order is: VPN off, join the right network, complete the portal, test normal browsing, then connect the VPN. If the page does not show, forget and rejoin the network, use a plain http address and turn off private DNS for a minute. Expect sessions to expire, and reconnect in the same order. Keep the portal step short and cautious, and then protect the rest of your session.

For travel, the pricing page shows prepaid passes that match a trip, and the download page lists the official apps to install before you leave home.