To enable KuaiLian Kill Switch (network lock), open whatever your build labels as Kill Switch / network lock / disconnect protection, turn it on, connect until a test site loads, then manually disconnect once. If almost nothing loads after the drop, the lock is likely working; if the same site still opens on a local-looking path, you have a leak or the toggle did not stick—reconnect and re-test before you burn time switching nodes.
Mid-meeting, the VPN drops and the docs tab keeps loading on the ISP path—that is a leak. Another person turns the lock on, the tunnel flickers, and chat plus browser die; they assume “connected but no internet.” Both involve the lock, but the fixes are opposite: prove it blocks after disconnect, or prove it is not strangling a still-live tunnel.
If you are connected but almost nothing loads and you are unsure the lock is stuck, start with connected but no internet (includes a temporary lock-off check). Cannot connect at all? See connection troubleshooting. Wrong path for one app? See split tunnel / bypass. Client never launches or never auto-connects? See auto-connect / startup. This article is only for Kill Switch checks and side effects—no streaming unlock or node-speed claims.
Kill Switch vs “connected but no internet”
- Connected, nothing loads: UI still says connected, pages mostly fail → DNS, nodes, system proxy first; the lock may be one interferer
- Disconnect leak: VPN is down or flickered, yet the destination still opens like local → lock off or not applied
- False offline cut: lock on, tunnel not ready or just dropped, whole device looks dead → lock-off contrast, then decide whether to re-enable
Name the symptom before you flip the switch: “still browsing after disconnect” vs “looks connected but everything is dead.” Neither starts with a node pile.
Find the real menu name in your build
Labels differ. Look under settings / security / advanced for Kill Switch, network lock, disconnect protection, or block non-VPN traffic. Use what you see—not a screenshot from another phone.
1. Snapshot the toggle
On/off, plus any “Wi-Fi only” sub-options. Screenshot before edits so you can roll back.
2. Check if connect is required
Some builds grey out the lock until a tunnel is up, or fail to save while disconnected.
3. Change only the lock
Do not flip protocol, clear split lists, and swap nodes together—you will not know what worked.
4. Reconnect after save
Disconnect and connect once so routes pick up the policy; tapping Save alone is often not enough.
How to enable: switch verification steps
- Open KuaiLian settings, find Kill Switch / network lock, and turn it on
- Connect to any working node and confirm a browser test site loads
- Leave Wi-Fi on; disconnect VPN from inside the client
- Hit the same test site immediately: expect near-failure (lock blocking). If it still opens freely, re-check the toggle and quit a second proxy / other VPN
- Reconnect, confirm the test site works again, then decide whether to leave the lock on day to day
On locked-down office Wi-Fi, “fails after disconnect” may be policy, not the lock. For leak tests, prefer a domestic site that also opens with VPN off.
Disconnect leaks: prove the lock actually blocks
A leak feels like: client disconnected or quit, yet the destination still loads. Focus on proving the block, not speeding nodes.
- Run the fixed sequence—lock on → connect → manual disconnect → immediate visit—before and after any change
- Force-quit the browser on mobile so cached sockets do not look like “still online”
- If the client shows a security or connection log, check whether the lock reports active at the drop
- Clash, system proxy, or a second VPN can bypass KuaiLian’s lock—test with KuaiLian alone
Still leaking and menus do not match older screenshots? Check the download page for the current build; older packages may lack a full lock.
False offline cuts: lock on, device looks dead
During tunnel flicker, node swaps, or a UI that still says connected while the tunnel is gone, the lock can choke all traffic. That looks a lot like bad DNS—separate them with a lock-off contrast.
- Turn Kill Switch off in settings; change nothing else
- Disconnect and reconnect the same node; if access returns immediately, the lock was stuck blocking—not a login issue
- If you still want leak protection, wait until the tunnel is stable (test site loads) before turning the lock back on
- If lock-off still fails almost everything, move to connected but no internet for DNS and system proxy—stop toggling the lock
On Windows / macOS, also check whether system proxy rules are stuck; that is a separate line from the network lock.
When split tunnel / exclude stacks with the lock
App exclude, bypass lists, and Kill Switch together can disagree on disconnect: excluded apps may still go direct on some builds, while non-excluded traffic is blocked. That is priority, not a “broken lock.”
- After changing either setting, reconnect and test disconnect once for an excluded app and once for a normal browser
- Do not assume “Kill Switch on = every app dies on disconnect”
- List and domestic-direct details: split tunnel / bypass guide
Still wrong: what to record before FAQ / download
If contrast tests still fail, gather this for FAQ or in-app support:
- Device, OS, KuaiLian version, and install source
- Kill Switch on/off; which test site you used before and after
- Class: leak (still online after drop) vs false cut (lock on, device dead)
- Whether split exclude, system proxy, or another VPN was also running (never send passwords)
Missing menus or a toggle that does nothing: check the download page first. Reinstall can clear a stuck state; it does not guarantee speed or unlocks. Setup paths: Guides. Auth errors belong in login troubleshooting—do not “fix” passwords by flipping the lock.