When KuaiLian won’t connect on hotel or airport Wi-Fi, check whether the browser can open the captive portal (terms, room number, SMS). With VPN on, auth traffic often gets pulled into the tunnel—blank page or endless spin. Prefer a temporary disconnect or system-browser direct path to finish auth, then reconnect. Day-to-day split rules → split guide; long handshake failure after normal internet → connection guide; full-device cut on drop → Kill Switch—this page makes no node-speed or streaming-unlock promises.
First night on a trip, the phone joined the hotel SSID and said “Connected, sign in to network.” They opened KuaiLian; Connect spun for a minute and failed. Two country nodes later, the login page still never appeared. Front desk said the browser would pop up. They disconnected KuaiLian—the system browser finally showed terms, room number worked, internet returned—then KuaiLian connected. Not “slow nodes.” The captive portal was unfinished.
Home/office broadband, Connect stays failed → connection troubleshooting. Day-to-day wrong path (should be direct vs proxied) → split / bypass list. Full-device offline on drop → Kill Switch. Was Connected, then status flips → reconnect loop / drops. Device-limit or multi-device kick → device limit / multi-device. This page only covers public Wi-Fi that needs a captive portal.
Portal vs can’t connect vs split vs Kill Switch
- Captive portal / auth page: SSID joined, but no open internet until portal login; VPN on often blocks or fakes the page
- Can’t connect: device already has normal internet, yet KuaiLian Connect fails long → protocol, firewall, nodes—connection guide
- Split: day-to-day domain/app path rules; this page only uses temporary portal bypass—details in the split guide
- Kill Switch: leak-on-drop vs false full-device cut—not the first toggle for hotel login pages
Name the symptom: “Wi-Fi joined but nothing loads / stuck on login,” or “portal already done, internet fine, only KuaiLian handshake fails.” First case stays here; second goes to the connection article so you do not fight split and Kill Switch over the same toggles.
Confirm it is a captive portal
Prove portal state—not download peaks, not “another node will pass login.”
- OS hints: iOS/Android/Windows/macOS often say “Sign in to network” / “Login required for internet”
- With VPN off, open any http site or the venue’s login URL in the system browser—does the terms/room page appear?
- Before auth, most sites time out or redirect to a portal host (often hotel, guest, wifi, portal—use what you see)
- After success, a normal site should load on-device; then reconnect KuaiLian for contrast
If VPN off still shows no portal and no internet, ask the desk / change AP before stacking nodes in KuaiLian. If the device already browses fine and only Connect fails, leave this page for connection troubleshooting.
Temporary disconnect: let the browser finish auth
Most hotel portals only honor on-device HTTP captive probes. With a tunnel up, the probe fails and the page never pops.
1. Fully disconnect KuaiLian
Confirm status is not Connecting. If Always-on blocks that, contrast that toggle alone first.
2. Use the system browser
Skip in-app webviews. Safari / Chrome / Edge: any http URL or the desk’s login link.
3. Finish terms / room / SMS
Wait for “internet available,” then test a normal site. Change only VPN on/off—do not also flip protocol.
4. Reconnect KuaiLian
Keep the same node; watch for Connected. Still failing → temporary split next or the connection guide.
Sessions expire after lock or SSID rejoin—common venue policy. Repeat “disconnect → portal → reconnect”; do not treat it as a KuaiLian reconnect loop and hammer background settings. True mid-session flashes → reconnect loop.
After auth: temporary split around the portal host
Rarely you must keep VPN on for the page to appear, or the portal host gets captured again after connect. Use a temporary bypass contrast:
- In split / bypass, set the current portal host (what the address bar shows) to direct / exclude
- Or exclude only the system browser from the tunnel until login finishes, then revert
- Add one host or one app at a time—do not import a full domestic list “for optimization”
- After login, remove the temporary rule so it does not tangle with daily split policy
Exact labels follow the current build; full split logic: split / bypass list. Temporary bypass is only for finishing auth—no unlock, speed, or “never disconnect VPN” promises.
Still stuck: Kill Switch, connect fail, mid-session drops
- Still on the portal: VPN fully off, system browser direct; try another browser; reopen the portal tab; ask if a separate guest SSID is required
- Portal done, device online, KuaiLian still fails → connection troubleshooting—stop looping VPN on this page
- Tunnel drop kills all traffic → Kill Switch; if the lock also cuts captive probes, contrast lock off temporarily, then restore per that guide
- Connected briefly then status flips → reconnect loop—Wi-Fi roam and background first, not more portal hosts
Contrasts do not prove anti-censorship, streaming unlocks, or “that country is faster on hotel Wi-Fi.” Node/protocol changes may alter handshakes; this article makes no speed or unlock claims.
Still blocked: what to record before FAQ / download
If auth still fails or Connect fails after auth, gather this for FAQ or in-app support:
- Venue type (hotel/airport/café), SSID, whether “sign in to network” appeared
- With VPN off vs on: portal open? normal sites on-device?
- KuaiLian version and platform; Always-on, Kill Switch, any temporary split rule
- Portal host (redact room/phone; never send passwords)
Menu labels mismatch old tutorials: check the download page first. Reinstall can refresh connection/split options; it does not guarantee one-tap hotel auth or unlocks. Setup paths: Guides.