When Lvcha VPN shows Connected but browsers spin, work this order: Kill Switch off → global mode on → flush DNS → clear leftover system proxies → change nodes last. Most people locate the fault in ten minutes without reinstalling.
“The node is dead” is the story you hear. The usual causes are DNS, split tunnel, permissions, and the kill switch. Confirm you actually granted VPN permission in the install guide, and that the build matches the download page.
A one-minute fork: total blackout vs partial
| Test | Do this | Read it as |
|---|---|---|
| Egress page | Open https://1.1.1.1/help | No page: tunnel or Kill Switch. Page loads, IP unchanged: fake connect |
| DNS | Ping 1.1.1.1 vs ping a hostname | IP works, name fails = DNS |
| Split | Global vs smart | Only smart fails = rules |
| Proxy leftovers | Windows/macOS proxy panel | Manual or PAC? Turn it off |
If even the tests never load, disconnect Lvcha VPN. If the LAN is dead too, fix Wi-Fi or the bill before touching nodes. Cloudflare’s primer on what DNS is is enough background; you do not need to rewrite resolv.conf for a first pass.
DNS: packets flow, names do not
Enable leak protection in the client. On Windows run ipconfig /flushdns and reconnect. On phones, toggle airplane mode for five seconds. Router-forced DNS is common in rentals—compare against cellular once.
Split tunnel sent the browser around the VPN
Bypass-mainland or per-app lists that omit Chrome produce “foreign sites dead, local apps fine.” Global mode is the lab. If global works, put the system WebView back on the tunnel list, then add rules one at a time. Office transparent proxies fight split mode; test at home or on cellular.
Kill Switch is supposed to cut you off
During roam, sleep, or node switch, the lock blocks all traffic so your home IP does not leak. Disable it once. If the web returns immediately, the tunnel is flapping—pick a quieter node or change UDP/TCP, then re-enable the lock.
When to stop
| Symptom | Do | Skip |
|---|---|---|
| Global + lock off still dead | Two or three nodes, protocol change, update | Editing hosts |
| Only smart mode fails | Reset bypass lists | Reinstalling the OS stack |
| One device only | Compare another device on the same account | Password thrashing |
Account and device-limit questions sit in the FAQ. Refresh the client from the download page and keep the guides for platform quirks.
Field questions tied to this guide
- Every site fails while the app says Connected. Kill Switch may be blackholing traffic during a flap, or DNS never entered the tunnel. Turn the switch off, set global mode, reconnect, then open 1.1.1.1/help.
- Local sites work, foreign ones time out. Split rules are sending the foreign names direct. Global mode for three minutes tells you whether the node is fine.
- Android dies after the screen locks. The OS likely froze the process. Exempt Lvcha VPN from battery optimization and watch whether the key icon vanishes.
- Should I hard-code 1.1.1.1 in Windows? Prefer the in-app 'VPN DNS / leak protection' toggle. Manual NIC DNS often fights the tunnel. Flush with ipconfig /flushdns after you switch.
Change one control, then retest
While working through “Lvcha VPN says Connected but pages never load: DNS, split tunnel, Kill Switch”, write the download-page version, mode, protocol, and node name on the first line of a note. After each toggle, run one check only: 1.1.1.1/help or the exact page that failed. Changing Kill Switch, split rules, and nodes together makes the next failure un-debuggable. Get Lvcha VPN packages only from the download page; permissions and device limits live in the FAQ and guides.
On office or hotel networks, finish captive portals and clear leftover PAC entries before you decide this article’s failure mode applies. A cellular A/B exposes router DNS and parental filters quickly. Avoid hammering login on a second device during the test so session kickouts are not mistaken for radio drops.
Pin the combination that works—SSID, node, protocol—and reuse it on that network instead of starting from Auto every time. Keeping slug lvcha-connected-no-traffic as your note title makes the write-up searchable later.
When to stop and change layers
After five identical failures, stop. Recheck the documented build, confirm a single tunnel client, ensure Kill Switch was not blocking a portal, and verify the browser is not Direct in a split list. Stopping is how you escape the wrong layer.
When you ask for help, include time, SSID, mode, protocol, node names, and steps already tried. After recovery, verify egress in a clean browser so cache does not fake success, then write the split list or favorites back into your notes before the next reinstall.