“Cannot connect” and “connected but slow” require different diagnoses. The first commonly involves captive portals, permissions, blocked handshakes or conflicting software. The second is more often caused by congestion, routing, Wi-Fi interference or the destination itself. Follow these steps in order and change one variable at a time.
1. Establish the scope
Does the internet work with the VPN disconnected? Is every app affected or only one service? Does the same account work on another device? Repair the underlying Wi-Fi, broadband or cellular connection before troubleshooting the tunnel.
2. Check service status and device time
Review service status for account, client or server notices. Incorrect date, time or time-zone settings can break certificate validation and login, so enable automatic time.
3. Complete captive-portal sign-in
Hotels and airports often block VPN traffic until their portal is accepted. Disconnect temporarily, open a normal webpage to trigger the portal, complete the minimum required sign-in, then reconnect. Never install an unknown certificate.
4. Reconnect, then try one nearby alternative
Disconnect, wait ten seconds and reconnect. If the problem persists, test one other server in the same region. Rapidly cycling through many servers produces noisy results and can create overlapping sessions.
5. Identify the performance symptom
- Slow clicks and page starts: latency;
- broken calls or game jumps: jitter and packet loss;
- low video quality or slow downloads: sustained throughput;
- evening-only slowdown: local or transit congestion.
6. Compare Wi-Fi, cellular and a hotspot
On a phone, compare Wi-Fi and mobile data. On a computer, try a phone hotspot. Failure on only one network points toward the router, ISP path or network policy; failure everywhere points toward the account, app or device configuration.
7. Remove network-tool conflicts
Temporarily exit other VPNs, manual proxies, packet-capture tools, ad filters, parental controls and third-party firewalls. Restore them one by one after the test. Managed security software should be handled by the administrator.
8. Change protocol only with a reason
The default is the correct starting point. Try another protocol only after handshake timeouts, a network-specific block or a support recommendation. Test stability before changing DNS or server location as well.
9. Fix “connected, no websites”
Remove stale manual browser and system proxies, refresh the network and try another server. If names fail while direct IP connectivity remains, DNS may be involved. Prefer the client's default DNS and avoid untrusted profiles or root certificates.
10. Control background load
Cloud sync, updates, uploads, battery-saving modes and weak routers distort tests. Pause heavy tasks and compare direct and VPN results on the same device, place and time. Run at least three tests and use the median.
11. Update first; reinstall last
Update from the official download page and restart the device. Reinstall only when configuration corruption or a failed update is likely. Record the version and error before removing anything.
12. Send diagnostic information safely
Tell support the platform, OS and client versions, network type, server region, failure time, affected services and steps already tried. Do not send passwords, one-time codes, full payment details or private keys.
Optimize for consistency, not one peak result
Calls need low jitter, browsing needs low latency and downloads need sustained throughput. Keep one primary server and one backup on a different route. See the FAQ for additional account and installation questions.
Video reference and editorial note
This article uses recurring concerns in an early mobile Kuaimiao review—server choice and variable speeds—as research input, then expands them into a repeatable modern workflow. Old statements about pricing, traffic or versions are not current service promises: Kuaimiao VPN mobile review.