Hotel Wi-Fi is where VPNs go to struggle. Between captive login portals, blocked ports, shared bandwidth across hundreds of rooms, and network gear that hasn’t been updated in years, a VPN connection that works perfectly at home can refuse to connect at all from a hotel room. Here’s how to fix the actual causes, not just retry the same connection.
Why hotel Wi-Fi breaks VPN connections
Three things are usually responsible, often at the same time.
Captive portals. Most hotel networks route new devices through a login page before granting real internet access. Your VPN app tries to connect before that handshake completes, fails, and sometimes leaves your device thinking it’s online when it isn’t actually passing traffic anywhere.
Blocked or restricted ports. Some hotel networks, particularly larger chains with more aggressive network management, block or throttle the ports commonly used by VPN protocols, either deliberately (to push guests toward paid “premium” Wi-Fi tiers) or as a side effect of intrusion-prevention systems that flag encrypted tunnels as suspicious traffic.
Shared, congested bandwidth. Hotel networks split limited bandwidth across every connected guest. Even where a VPN connects fine, the encryption overhead on an already-slow connection can make a marginal network unusable.
Step 1: connect to Wi-Fi and clear the captive portal first
Before opening your VPN app, connect to the hotel’s Wi-Fi network normally and let the captive portal load in a browser. Complete whatever login step it requires (room number, last name, an email address) and confirm you have working internet without the VPN active. Only then open your VPN app. Trying to connect your VPN before the portal handshake finishes is the single most common reason a VPN “won’t connect” on hotel Wi-Fi when it’s really the network, not the VPN, at fault.
Step 2: switch protocols if the first one fails
If the VPN still won’t connect once you have clean internet access, don’t assume the network is impossible. Switch protocols inside your VPN app before giving up.
WireGuard is fast but uses a fixed, well-known port that’s easier for restrictive networks to block. OpenVPN over TCP port 443 is slower but disguises your VPN traffic as ordinary HTTPS traffic, the same port used by every secure website, which makes it far harder for hotel network gear to selectively block without breaking the internet for every other guest too. Most major VPN apps let you force this fallback manually in settings, sometimes labeled “Automatic” or “Obfuscated” mode, which is worth trying even before manually picking OpenVPN TCP.
Providers with dedicated obfuscation features, covered in more depth in our guide on obfuscated servers, are built specifically for exactly this kind of restrictive network, and hotel Wi-Fi is one of the more common places that feature actually gets used outside authoritarian countries.
Step 3: try a different DNS setting
Some hotel networks intercept or redirect DNS requests as part of how the captive portal works, and that redirection can linger even after login, confusing your VPN’s own DNS handling. If your VPN app has a manual DNS option, try switching it, or toggle any built-in DNS leak protection off and back on to force it to re-resolve cleanly against the hotel’s actual network path.
Want to compare all VPNs side by side? Check our full VPN comparison table with scores across 18 criteria.
Step 4: use a travel router for a persistent fix
If you travel often and hit this problem repeatedly, a small travel router changes the equation entirely. You connect the travel router to the hotel Wi-Fi once, complete the captive portal on the router itself, and then connect all your own devices to the router’s private network instead of the hotel’s. The VPN runs on the router, not on each individual device, so your laptop, phone, and tablet all get consistent, already-tunneled internet without repeating the captive portal or protocol-switching dance on every device separately.
Our guide to setting up a GL.iNet travel router walks through the full setup, and it’s the most reliable fix for anyone who stays in hotels regularly rather than once or twice a year.
Step 5: check for port restrictions specific to the property
Larger hotel chains and business-focused properties sometimes contract out network management to companies whose whole business model is throttling or blocking VPN and streaming traffic to push guests toward paid Wi-Fi upgrades. If none of the above works and you suspect this is deliberate, ask the front desk directly whether a “premium” or “business” Wi-Fi tier is available. It’s a frustrating ask, but it’s often genuinely the only network tier where VPN ports aren’t restricted, since it’s usually billed and managed separately from the free guest network.
What to expect even when it works
Even a successfully connected VPN on hotel Wi-Fi will usually be slower than your home connection, because of the shared bandwidth every other guest is also using. This isn’t a VPN problem to troubleshoot further; it’s the nature of hotel networks generally. If speed matters for video calls or large downloads, connecting during off-peak hours (early morning, mid-afternoon) tends to help more than any VPN setting will.
When to just skip the hotel network entirely
Sometimes the fastest fix isn’t a fix at all: tether to your phone’s mobile data and run the VPN over that instead. Mobile networks rarely block VPN ports the way hotel Wi-Fi sometimes does, since carriers aren’t trying to upsell you a separate “premium” data tier the way some hotel Wi-Fi providers are. This costs mobile data, so it’s not a permanent solution, but for a short video call or an urgent email while you’re still troubleshooting the hotel network, it’s often quicker than working through every step above under time pressure. It’s also a useful fallback if you land in a country where a VPN roaming eSIM, covered in our travel eSIM guide, makes more sense than fighting hotel infrastructure at all.
A quick checklist for next time
Before you travel, confirm your VPN app supports manual protocol switching and has an obfuscation or “stealth” mode available, since not every provider offers this on every platform. Test your VPN once on a public network (a coffee shop, an airport) before you actually need it in a hotel room where troubleshooting is more inconvenient. And if hotel Wi-Fi is a recurring issue on your trips, a travel router is worth the one-time setup cost rather than repeating this troubleshooting process at every check-in.
Most "VPN doesn't work on hotel Wi-Fi" problems are actually captive portal or port-blocking problems. Clear the portal first, switch to OpenVPN over TCP 443 or an obfuscated mode if your first protocol fails, and check DNS settings if the connection still won't stabilize. For frequent travelers, a travel router with the VPN configured once at the router level is the more permanent fix.
For more on staying protected while traveling, see is it safe to use a VPN on public Wi-Fi and VPN and travel eSIM: do you need both.