A VPN that connects successfully but drops again and again is frustrating, but the cause is often a setting or a change in the network rather than a problem with the account. Start by noting when the drop happens: after the screen locks, when Wi-Fi changes to mobile data, while using one particular network, or at apparently random times. Then check battery restrictions, update the client, test a supported protocol, and compare another network or server. Change one thing at a time so you can tell which action made a difference.
Identify the Kind of Disconnection
First establish what “disconnecting” means on your device. Some clients lose their connection to the VPN server and show a disconnected status. Others remain connected, but a website or app stops loading. These look similar from the user’s perspective, yet they point to different causes. If the client says it is disconnected, investigate the network path, app permissions, and connection settings. If it still says connected, check routing, DNS, the destination app, and whether the issue affects one service or all traffic.
Record the time and circumstances of each failure. Note whether the device was idle, waking from sleep, switching between Wi-Fi and cellular data, or joining a network that requires a sign-in page. Also note whether the failure affects every app or just one. A brief log is more useful than repeatedly reconnecting without tracking changes; it gives you and support a way to distinguish a recurring trigger from a one-off network interruption.
Before changing settings, confirm that the device itself still has internet access. Disconnect the VPN briefly and try an ordinary webpage or another known working app. If the connection is also unavailable without the VPN, troubleshoot the router, mobile signal, captive portal, or local network first. If the internet works normally without the VPN but fails through it, continue with the checks below.
- ✅ Note the client’s status and the time of each drop.
- ✅ Check whether the failure follows the device, the network, or one app.
- ✅ Confirm that ordinary internet access works when the VPN is disconnected.
- ❌ Avoid changing several settings at once; doing so obscures the cause.
Check Power and Background Settings
Battery optimization is a common reason a mobile device pauses a VPN client when the app is in the background or the screen is off. The operating system may restrict background activity to conserve power, and the client may then be unable to maintain or quickly re-establish its connection. Menu names vary by operating system and manufacturer, so look for settings related to battery usage, background activity, app sleeping, or automatic optimization.
On Android, review the VPN app’s battery setting and allow background activity if the system offers that option. Also check whether a device-specific battery manager has placed the app in a sleeping or restricted list. On iPhone and iPad, confirm that the VPN profile remains enabled and that the client is permitted to operate as configured; available controls differ by iOS version and client. On laptops, inspect power-saving behavior around sleep and network adapters. A computer may suspend its network connection when the lid closes or when it enters a low-power state, interrupting an active tunnel.
Do not assume that turning off every power-saving feature is necessary. Make a targeted exception for the VPN app, then test whether the drop still occurs when the screen is locked or the device is idle. If the problem appears only after sleep, compare a short test with the device awake and another after allowing it to sleep. This helps identify whether background suspension, rather than the server or protocol, is the likely trigger.
Also check for conflicts with another VPN, firewall, security suite, private DNS tool, or network-filtering app. Many operating systems allow only one active VPN interface at a time, and network filters can affect DNS or routing even when they do not display themselves as VPNs. Close or pause competing tools only for a controlled test, and restore protections afterward. If the device is managed by an employer or school, do not alter its security policy without permission.
Update the Client and Test the Network
An older client can have compatibility problems with a recent operating-system update, a network change, or a server-side configuration. Check for an update through the official source you used to obtain the app. If an update is available, install it, restart the device if requested, and test again before changing advanced options. If the client offers a configuration or subscription refresh, use its normal refresh function rather than copying settings from an unknown source.
Next, compare the connection on another network that you are authorized to use. For example, if the VPN drops on home Wi-Fi, test briefly on a trusted mobile connection; if it drops on mobile data, try a trusted Wi-Fi network. A connection that fails on only one network may be affected by the router, local firewall, DNS handling, signal quality, or restrictions on that network. If it fails on different networks in the same way, the client, device settings, selected server, or account configuration becomes more relevant.
Network changes deserve particular attention. Moving from Wi-Fi to cellular data changes the device’s route and address, and a client may need to reconnect or renegotiate its tunnel. Some clients reconnect automatically; others may pause, wait, or require you to start a new connection. If the drop occurs only during a handoff, check the client’s options for reconnecting on network changes and test the transition while watching its status. Avoid repeatedly toggling airplane mode or resetting all network settings before you have identified a reproducible trigger.
When considering which service to use for recurring connection problems, compare its client support, troubleshooting guidance, and available connection choices rather than relying on an unverified speed claim. The VPNCar VPN for Students in China homepage is one place to review the service information and supported platforms before deciding whether its setup fits your device and network.
For this test, write down the network type, selected server, client version, and whether the connection stayed up. Do not record passwords, authentication tokens, or private subscription links in notes you intend to share. If a problem appears only on a public or managed network, follow that network’s rules and avoid trying to bypass restrictions you are not permitted to change.
Try a Supported Protocol or Server
If the app is current and the connection still drops, test another protocol only if the client or service explicitly offers it. Protocols use different connection methods, and a network may handle one method more reliably than another. There is no universally best choice for every device and network, so treat this as a controlled comparison rather than a promise that a particular protocol will solve the problem. Keep a note of the original selection so you can restore it.
Change the protocol, reconnect, and observe the same conditions that previously produced a drop. If you also switch servers, networks, and power settings at the same time, you will not know which change mattered. Use the client’s own documented choices, and do not paste an unofficial configuration or alter low-level parameters unless the provider’s instructions specifically call for it. A connection that stays active but cannot reach particular sites may point to DNS or routing behavior rather than a tunnel failure.
Testing another server can help determine whether the issue is route-specific. Choose a server that is available to your account and appropriate for your intended use. If one server drops while another remains stable under the same network conditions, report the affected server and the comparison to support. If several servers fail only on one network, the local network may be blocking or interrupting the connection. If the same failure occurs across multiple networks and servers, share that pattern with support instead of cycling randomly through the list.
Some clients provide a connection log or diagnostic screen. If available, check the entries around the time of the drop for repeated reconnection attempts, timeouts, authentication errors, or a network-change event. The wording varies by client, and a log line is not by itself proof of the cause. Share only the relevant excerpt through the provider’s supported channel, and remove personal details or tokens if they appear. Do not publish a full configuration file or subscription URL in a public forum.
If the client includes a kill switch, understand its behavior before testing. A kill switch may block ordinary traffic when the VPN tunnel is unavailable, which can make a short interruption look like a complete internet outage. This is intended to reduce accidental traffic outside the tunnel, not necessarily evidence that the client has frozen. Do not turn the feature off permanently to hide the symptom; instead, check the client status and logs, then decide whether the setting matches your needs.
Follow a Repeatable Troubleshooting Sequence
Use a short, consistent sequence to narrow the cause without repeatedly resetting the device. Start with the least disruptive checks, then move to connection choices. After each change, test under the same conditions that caused the original failure: the same network, the same background or sleep state, and the same app or task. If the connection remains stable, repeat the test before concluding that the issue is resolved.
- Confirm the symptom. Check whether the client reports disconnected, or whether only one app or destination has stopped working. Test ordinary internet access with the VPN off.
- Check power and permissions. Review background activity, battery restrictions, VPN permissions, and any setting that pauses network access during sleep.
- Update and restart. Install an official client update if available, restart the device when appropriate, and reconnect using the existing configuration.
- Compare networks. Test on another trusted network, then note whether the fault follows one network or the device.
- Compare one connection choice. Test a supported protocol or another available server, changing only one choice at a time.
- Collect evidence and ask for help. If the pattern remains, provide support with the device and operating-system details, client version, approximate time of failure, network type, selected server, and relevant redacted log lines.
This order also helps prevent unnecessary actions. Reinstalling an app or resetting all network settings can remove useful configuration and make it harder to reconstruct what happened. Consider those steps only after checking the simpler causes and following the client’s official instructions. If a reinstall is necessary, make sure you can sign in and restore the configuration before removing the existing app.
Contact support when the same failure is reproducible after these checks, when the client repeatedly reports authentication or server errors, or when the logs contain messages you cannot interpret. Include what you tested and what changed, not just “the VPN is unstable.” A concise comparison—such as “drops only after sleep” or “fails on one Wi-Fi network but works on another”—gives support a useful starting point. Never send a password, one-time code, or complete private subscription link in a support request unless the official process explicitly requires a secure method for handling it.
- ✅ Keep a record of the original settings before testing.
- ✅ Repeat each test under comparable conditions.
- ✅ Share timestamps and relevant, redacted diagnostics with support.
- ❌ Do not post credentials, private links, or complete unredacted logs publicly.
Frequently Asked Questions
Why does my VPN disconnect when my screen locks?
The operating system may restrict background activity or suspend the network connection to save power. Check the VPN app’s battery and background permissions, and review any device-specific app-sleep settings. On a laptop, compare behavior while awake with behavior after sleep. If the client stays connected but apps stop loading, check whether a kill switch or routing rule is blocking traffic during the interruption.
Why does the VPN drop when I change networks?
A Wi-Fi-to-cellular handoff changes the device’s network route, so the existing tunnel may need to reconnect. Check whether the client supports automatic reconnection after network changes. If it does, note how long reconnection takes and whether the client reports an error. If the drop occurs only on one destination network, that network’s settings or restrictions may be involved.
Should I change the protocol immediately?
Not necessarily. First confirm that the device has working internet access, check background restrictions, and update the official client. Then test another protocol only when it is offered and documented by the client or service. Change one option at a time and compare results under the same conditions; protocol availability and behavior depend on the client and network.
When should I contact support?
Ask for help when the problem repeats across reasonable tests, the client shows persistent errors, or you need help interpreting diagnostic logs. Include the client and operating-system versions, network type, approximate failure time, selected server, and steps already tried. Redact personal information and never include your password or a private subscription link in a public post.