A VPN that connects successfully but drops when you lock your phone, change Wi-Fi networks, or leave the app in the background can be frustrating. The cause is often not the VPN server itself: the operating system may pause the client, a network change may interrupt the tunnel, or another app may have changed proxy or DNS settings. Start with the checks that match when the disconnection happens, and change one setting at a time so you can identify what actually helps.
Before troubleshooting, note what “disconnecting” means in your case. Does the client show that it has disconnected, or does the client still say “Connected” while websites and apps stop loading? A dropped tunnel and a routing or DNS problem can look similar, but they need different fixes. If possible, check the client’s status and logs shortly after the issue occurs; avoid sharing logs publicly if they contain account details, subscription URLs, or other private information.
Identify when and how the connection drops
First look for a repeatable trigger. A VPN that disconnects only after the screen is locked points toward battery management or background activity. A drop that happens while moving between home Wi-Fi and mobile data is more likely to involve a network handoff. If it happens on one Wi-Fi network but not another, the router, captive portal, or network policy may be involved. If the client stays connected but only some apps fail, check routing and DNS before changing the server.
Keep the initial test simple. Use one VPN client, one selected route, and one app or website that normally works. Temporarily pause downloads or other network-heavy tasks so they do not complicate the diagnosis. Test once on the current network, then compare with another trusted connection if one is available. Do not change the protocol, DNS mode, battery settings, and router configuration all at once: if the problem disappears, you will not know which change mattered.
- ✅ Record whether the client itself reports a disconnection or only the target app stops loading.
- ✅ Note whether the drop follows screen lock, sleep, a Wi-Fi change, or a particular network.
- ✅ Check whether other apps still have internet access when the VPN appears to fail.
- ❌ Avoid running two VPN or proxy clients at the same time while testing.
Also check whether the client has a current subscription configuration and whether the selected route is still listed. If the app has a connection log, look for a new error at the time of the interruption rather than relying on an old warning from an earlier session. A log can help distinguish a network timeout from a permission problem, but the wording differs between clients, so use it as a clue rather than treating one message as a complete diagnosis.
Check background, battery, and system permissions
Mobile operating systems may limit background activity to conserve battery. If the VPN disconnects after you switch apps or lock the screen, open the system settings for the VPN client and check whether background data, background activity, or unrestricted battery use is available. The names and locations vary by device and operating-system version. Make a targeted adjustment only if your device offers one and the behavior fits your symptoms; do not disable battery protections for every app as a first step.
Android: review battery and background restrictions
On Android, open the app information page for your VPN client and review its battery and data-usage controls. If the system marks the app as restricted or pauses it aggressively, allow the level of background operation needed to maintain a connection, where that option is available. Also check whether a manufacturer-specific battery manager has a separate sleep list or automatic cleanup feature. These controls differ across Android devices, so follow the wording on your screen rather than instructions written for a different model.
Next, check Android’s VPN settings. If “Always-on VPN” or a setting that blocks connections without the VPN is enabled, confirm that it points to the client you actually use. Such controls can improve continuity, but a mismatched or outdated client selection can make all traffic appear unavailable. If you are diagnosing an issue, note the original setting before changing it, and restore it if the test does not help.
iPhone and iPad: test screen lock and network handoff
On iOS, start by checking whether the client is allowed to establish its VPN configuration and whether the system still shows an active VPN profile for that app. If the issue occurs after locking the screen, test on a stable Wi-Fi connection and leave the client open long enough to see whether it remains connected. Avoid repeatedly force-quitting the app during the test: closing it can interrupt the session and make it harder to tell whether iOS or the network caused the original drop.
If the drop happens during a move between Wi-Fi and cellular data, test each connection separately before testing the handoff again. A transition can interrupt an existing tunnel even when both networks work on their own. If the connection returns only after reopening the client, record that pattern and check for an app update or a client setting related to reconnecting. Do not remove a system VPN profile unless you know how to re-create it from the client.
Windows, macOS, and Linux: verify the active client
On desktop systems, confirm that the client is allowed to run in the background and that its virtual network adapter, network extension, or other requested system component is enabled. A VPN client may need operating-system permission to create or manage a tunnel. If the system recently updated, changed a security prompt, or reset a network permission, open the client and follow its current prompts rather than granting unrelated permissions.
Also make sure that only one application is controlling the system proxy or tunnel. A second VPN, proxy client, browser proxy extension, or manually configured proxy can redirect traffic unexpectedly. Quit the other tool and turn off its system proxy or virtual adapter before testing again. On macOS and Linux, review the active network or proxy settings; on Windows, check the client’s connection status and whether its network adapter is enabled. If you make a temporary change, write down the previous value so you can restore it.
Run a controlled reconnect test
Once you have checked the device settings, run a short, repeatable test rather than making several changes at once. This sequence helps separate an expired or incomplete configuration from a local network issue, a route issue, or a protocol compatibility problem.
- Close conflicting tools. Quit other VPN and proxy clients, and turn off any system proxy they left active. Keep the client you are testing as the only tool managing the connection.
- Check the subscription and client state. Confirm that the subscription has updated successfully, that the route list is available, and that the client has the permissions it needs. If the import appears incomplete, refresh it using the service’s own instructions rather than editing configuration values at random.
- Reconnect on one stable network. Disconnect from the VPN, wait for the client to finish closing the session, then reconnect while staying on the same Wi-Fi or mobile network. Check both the client status and an app that should use the VPN.
- Try a different route. If the connection still drops, select another available route appropriate for your location and use case. If the new route works while the original does not, the issue may be specific to that route or to how the current network reaches it.
- Test another network before changing protocols. Compare the same client and route on a different trusted network if possible. If it works there, focus on the original router or network restrictions. If it fails across networks, check the client configuration, permissions, and protocol compatibility.
- Change one protocol setting only when supported. Some compatible clients offer protocols such as Shadowsocks, VMess, Trojan, Hysteria2, or WireGuard. Availability depends on the service configuration and the client; a protocol cannot be selected simply because it appears in another app. If your subscription and client support alternatives, test one option at a time and restore the original choice if the result is worse.
These steps are also useful when choosing a setup: the VPNSPA Best VPN for China homepage outlines the supported platforms and service options, while the practical diagnosis still depends on the device, client, route, and network you are using.
For example, if the client disconnects on one home network but stays connected on mobile data, repeatedly reinstalling the client is unlikely to be the best first move. Check whether the router has changed, whether a captive portal needs sign-in, or whether the network blocks or interrupts the connection. If the client drops on every network immediately after the screen locks, focus instead on background restrictions and client behavior.
Check the network, DNS, and client configuration
If the client still reports “Connected” but browsing fails, treat the issue as a possible routing or DNS problem rather than an automatic disconnection. Check whether the failure affects every app or only selected apps. A rule-based client may intentionally send different apps or destinations through different routes. Confirm that the relevant app matches the intended rule and that the client is in the expected mode, such as system proxy or a supported tunnel mode. The exact options depend on the client and imported configuration.
On Wi-Fi networks that require a sign-in page, complete the captive-portal login before testing the VPN. Some public or managed networks restrict VPN traffic, and a successful connection on another network does not mean the VPN configuration is broken. If you are testing in a workplace, school, hotel, or public venue, follow that network’s access rules and avoid trying to bypass restrictions. Ask the network administrator whether VPN connections are permitted.
Check the subscription source if routes disappear, updates fail, or the client reports that its configuration cannot be parsed. Make sure the whole subscription link was copied and that the client supports the format being imported. Some third-party clients, including Clash Verge, sing-box, and Shadowrocket, use different configuration formats and features. A subscription that imports into one client may require a compatible import method or settings in another. Do not assume that every client supports every protocol or every service-specific option.
DNS changes can also create a misleading symptom: the VPN appears connected, but domain names do not resolve. If your client offers a DNS mode, use its documented default first and avoid entering unverified DNS addresses from forum posts. If only certain apps or domains fail, compare the client’s routing rules and DNS handling for those apps. Keep a record of your original configuration before changing it, and use the client’s own reset or update function when appropriate.
- ✅ Complete any required Wi-Fi sign-in before testing the VPN.
- ✅ Compare whether all traffic fails or only apps affected by routing rules.
- ✅ Confirm that the subscription format is supported by the client you selected.
- ❌ Do not edit several DNS, routing, and protocol fields at the same time.
Know when to update, reset, or ask for help
Update the client when the problem started after an operating-system change, when the app reports an outdated version, or when its documentation identifies a relevant fix. Use the official client source or the download route provided by the service. After updating, reopen the client, check its permissions, and refresh the subscription if the app’s instructions say to do so. Avoid uninstalling as the first response if you do not know how to restore the VPN profile or import the subscription again.
A reset can be useful when settings have become inconsistent, but distinguish a client-settings reset from deleting an account or subscription. Before resetting, note the selected route, connection mode, and any custom rules you need. If the client provides an export or backup feature, use it according to its documentation and store the file securely. A reset that removes the only copy of a custom configuration may create more work without solving a network-side issue.
When asking for support, provide a concise description of the trigger and tests: your operating system, client name and version, whether the client reports disconnected or remains connected, the network type, and the checks you already tried. Include relevant error text, but remove passwords, subscription links, account identifiers, and unrelated personal information. Mention whether another route or network changes the result. This makes it easier to distinguish a device-specific setting from a route or network problem.
If the VPN remains connected but one site or app fails, report the affected app and whether other traffic works. If the entire device loses connectivity whenever the VPN is enabled, mention whether a system proxy, tunnel mode, or always-on setting is active. Clear observations are more useful than repeatedly reinstalling clients or switching many settings without recording the results.
Frequently asked questions
Why does my VPN disconnect when I lock my phone?
Battery or background restrictions may pause the client, or the operating system may end a session that the client cannot restore automatically. Review the app’s background and battery settings, check whether the client has the required VPN permission, and test on a stable network. The available controls differ by device, so change only settings that match the behavior you observe.
Why does the client say “Connected” when nothing loads?
The tunnel may still be active while DNS, routing rules, or the underlying network prevents traffic from reaching its destination. Check whether every app fails or only selected apps, confirm the client’s proxy or tunnel mode, and complete any network sign-in page. If the issue affects only one app, inspect its routing rules before changing the VPN protocol.
Should I switch protocols to stop disconnections?
Not as the first step. First test the current configuration on a stable network, check device restrictions, and try another available route. If your subscription and client both support another protocol, test it separately and compare the result. Protocol choices are not interchangeable across all services and clients, and changing an unsupported setting can prevent the configuration from working.
Will reinstalling the VPN client fix the problem?
It may help if the installation or a required system component is damaged, but it is not a universal fix for battery restrictions, network handoffs, router policies, DNS issues, or incompatible configuration formats. Before reinstalling, confirm that you can obtain the client again and re-import your subscription. Try the targeted checks first, and keep a note of the settings you may need to restore.