
Travel Router Won't Get Past the Hotel WiFi Login Page? Here's the Actual Fix
You plug in the travel router, connect it to the hotel WiFi, and the little status light says everything's fine. Then nothing loads. No websites, no apps, nothing. This specific failure is common enough with VPN travel routers that it's worth understanding exactly why it happens, because the fix is simple once you know the actual order of operations.
Why this happens with a VPN router specifically
A hotel captive portal works by intercepting your very first request for a web page and redirecting it to a login or terms-of-service page instead of wherever you were actually trying to go. That interception has to happen on plain, unencrypted traffic, before anything gets tunneled anywhere.
If your router's VPN client is already active when it connects to the hotel WiFi, it tries to route everything through the encrypted tunnel immediately. The hotel's network never gets the chance to intercept that first request, because there's nothing left for it to intercept, it's already wrapped up and headed somewhere else. The result looks like a dead connection, but what's actually happening is the captive portal page has no way to reach you.
The fix is almost always about sequencing: get all the way through the captive portal first, with the VPN off, then turn the VPN on once real internet access is confirmed.
The actual fix, step by step
Step 1: Connect the router to the hotel WiFi with the VPN client turned off. Use the router's repeater or client mode to join the hotel network by name and password, the same way you'd join any WiFi. Leave WireGuard or OpenVPN disabled on the router for now.
Step 2: Try to load a plain web page from a device connected to the router. If the captive portal page shows up here, log in through it normally and skip to Step 5.
Step 3: If nothing shows up at all, check for DNS Rebinding Attack Protection. This is a security feature, on by default on some routers, that can block exactly the kind of local redirect a captive portal relies on. Turning it off temporarily, just while you connect to hotel or public WiFi, often makes the login page appear immediately. Turn it back on once you're done if you'd rather leave it on generally.
Step 4: If it's still stuck, use the MAC clone method. Connect a phone or laptop directly to the hotel WiFi, not through the router, and complete the captive portal login on that device normally. Once it's working, find that device's WiFi MAC address (on most phones, it's in the WiFi network's details, or under general device settings if not shown there). Then, in the router's own admin panel, clone that MAC address onto the router's WAN or repeater connection. Reconnect the router to the hotel WiFi. Since the hotel network already trusts that MAC address from the device that just logged in, the router gets treated the same way, without needing to complete the portal login a second time itself.
Step 5: Confirm you actually have real internet access, not just a WiFi connection, by loading an ordinary website. Once that works, turn the VPN client on. Everything connected to the router from this point forward is tunneled normally.
One honest thing worth knowing
For the brief window before your VPN connects, while you're getting through the captive portal itself, your traffic is visible to the hotel's network the same way anyone's would be. That's not a flaw in this setup, it's just how logging into any WiFi network works, VPN or not, since you have to talk to their server in plain terms to get past their login page in the first place. The VPN protects everything from the moment it's actually on, which is exactly why the sequencing in Step 5 matters.
Logged in, but the VPN still won't connect?
Sometimes you get past the login page, websites load fine, and then the VPN itself refuses to connect, or connects and drops a minute later. That is a different problem. Some hotel, conference and airport networks block VPN traffic on purpose, usually by blocking UDP (which WireGuard needs) or by inspecting traffic and cutting anything that looks like a VPN. In some countries the whole national network does this.
Try OpenVPN on TCP port 443. It gets past networks that only block UDP. Our OpenVPN vs WireGuard guide explains why.
Switch the router to Stealth mode. OurVPNs Stealth uses VLESS + REALITY + XTLS Vision and Hysteria2, which look like ordinary web traffic instead of a VPN. It works on our routers, is included on every plan, and as of October 2026 we have tested it working from China, the UAE, Turkey and Russia.
Then check it worked. Run our VPN leak test to make sure your traffic is really going through the tunnel.
Why bother with a router instead of just using an app on your phone
Beyond fixing the "no internet at all" problem, routing through a travel router solves a second, more mundane hotel headache: plenty of hotel networks limit how many devices can connect per room, sometimes to just one or two. Since the hotel network only ever sees your router as a single device, everything connected behind it, your phone, laptop, tablet, whatever else you brought, gets online without tripping that limit or needing to be configured individually. Still choosing a router? Our picks for the best VPN travel routers in 2026 compare speed, power and price. Rather have one that shows up ready? Our preconfigured travel routers arrive set up for your US home IP.
Quick answers
Why does my travel router say it's connected but nothing loads? Almost always a captive portal issue. If the router's VPN is already active, it tunnels your traffic before the hotel's login page can intercept it, so the page never appears.
Do I need to turn my VPN off every time I connect to hotel WiFi? Just until you're past the login page. Once real internet access is confirmed, turn the VPN back on and everything connected to the router is protected from that point forward. On a UniFi Travel Router the login happens in the UniFi app, and our UniFi Travel Router VPN setup guide walks through that order.
What if the captive portal page still won't show up? Try disabling DNS Rebinding Attack Protection first. If that doesn't help, the MAC clone method, cloning an already-authenticated device's address onto the router, works even on stricter hotel networks.
Is my traffic exposed while I'm getting through the login page? Only for that brief window, the same as it would be for anyone connecting to that WiFi without a VPN at all. It's an unavoidable part of how captive portal logins work, not something specific to your setup.
The login worked, so why does my VPN keep failing? The network is probably blocking VPN traffic. Try OpenVPN on TCP 443, and if that fails, switch to Stealth mode.
The short version
A VPN router that seems stuck on hotel WiFi almost always has one cause: the VPN activated before the captive portal had a chance to intercept your connection. Turn the VPN off, get all the way through the hotel's login page, confirm you have real internet, then turn the VPN back on. If the portal page won't show up at all, disabling DNS Rebinding Attack Protection or cloning an already-authenticated device's MAC address onto the router almost always finishes the job.
Setting up your travel router with a real US home connection? Start your free trial and get it running before your next trip.