A VPN that connects and then drops can fail for several different reasons: the underlying network may be unstable, the device may suspend the app, the selected protocol may not suit the current connection, or a particular server may be temporarily unreachable. Start by identifying when the disconnect happens instead of changing several settings at once. A repeatable pattern—such as drops only after sleep or only when moving from Wi-Fi to mobile data—often points to a more useful test than the connection icon alone.
Bottom line: change one variable at a time. Record what network you are using, what the device was doing just before the drop, and whether the VPN reconnects by itself. Then test the network, app settings, protocol, and server in that order. This helps distinguish a VPN problem from a device or internet connection problem.
Identify when the connection drops
First, note the circumstances around the failure. Does the VPN disconnect while the device is idle, after the screen turns off, during a video call, or as soon as you change networks? Does it happen on one Wi-Fi network, or on both Wi-Fi and mobile data? Does the client show a disconnected state, or does it remain connected while websites and apps stop loading? These are different symptoms and should not be treated as the same fault.
Check whether ordinary internet access works when the VPN is off. If the device also loses access without the VPN, focus on the router, mobile signal, captive portal, or internet service first. If the internet works normally without the VPN but stops after connecting, examine the VPN client, selected route, and device settings. If only one app fails, its own network behavior or routing rules may be relevant even when the VPN tunnel is still active.
Keep a short record rather than relying on memory. Include the device and operating system, client name, network type, approximate time of the disconnect, whether the device had gone to sleep, and what action restored the connection. Avoid recording passwords, private keys, or subscription URLs. This simple log can reveal whether the failures follow a network change, an idle period, or a particular route.
- ✅ Compare VPN-on and VPN-off behavior on the same network.
- ✅ Note whether the client reports a disconnect or only an app failure.
- ✅ Check whether the problem follows one device, one network, or one server.
- ❌ Don’t change several client settings before recording the original behavior.
Rule out network instability
A VPN depends on the device’s underlying internet connection. If Wi-Fi briefly drops, a router changes channels, or mobile reception fluctuates, the tunnel may need to reconnect. A VPN client can sometimes recover automatically, but it cannot make an unavailable local network carry traffic. Start with a basic comparison: use the VPN on the current network, then test it on another trusted connection if one is available. Keep the device and client settings the same during this comparison.
On public Wi-Fi, check whether a sign-in or acceptance page is required. Open a browser with the VPN disconnected and complete the network’s normal access process before reconnecting. Some networks restrict or interrupt encrypted connections; in that case, the issue may be specific to that network rather than a general fault with the client. Avoid entering sensitive information into a sign-in page unless you have verified that it belongs to the venue or network operator.
If the problem appears after switching between Wi-Fi and mobile data, test each connection separately before testing the transition again. Some clients reconnect automatically when the network changes, while others may need a manual reconnect. Confirm that the device still has internet access on the new network, then disconnect and reconnect the VPN client. If only the transition causes trouble, check the client’s reconnect or network-change options rather than repeatedly replacing the subscription or reinstalling the app.
For a home network, restart the router only when ordinary connectivity is also unreliable, and follow the router maker’s instructions. If other devices have the same connection problem, the VPN app is unlikely to be the sole cause. If only one device is affected, compare its Wi-Fi behavior with another device and check for system-level network tools, firewalls, or other VPN clients that could interfere.
Check sleep, background, and client settings
A disconnect that follows screen lock or sleep often points to power management or background restrictions. Mobile operating systems may limit background activity to conserve battery, while laptops may suspend network interfaces during sleep. The exact controls vary by operating-system version and client, so use the settings available on your device rather than following instructions for a different platform.
On Android, review the VPN app’s battery or background-usage settings and check whether a battery-saving mode is active. On iPhone or iPad, check the client’s own reconnect options and the device’s network behavior; available controls differ by app and iOS version. On Windows and macOS, check whether the computer sleeps or turns off its network adapter when idle. Make one adjustment at a time, then repeat the same sleep-and-wake test that previously caused the drop.
Also check whether another application manages the device’s network. Running two VPN clients at once can create competing routes or tunnel controls. Security software, firewall rules, DNS tools, and proxy settings may also change how traffic is handled. Temporarily disable only a tool you understand and are authorized to manage, then test and restore it if it is not the cause. Do not leave security protections turned off as a permanent workaround.
Update the client using its official distribution channel and check whether the subscription or configuration needs refreshing. If a profile was imported into a third-party client, confirm that the client still has the expected configuration and that the subscription has not been disabled or replaced. Import instructions and supported formats differ between clients such as Clash Verge, sing-box, and Shadowrocket; a configuration intended for one app should not be assumed to work unchanged in another.
Hands-on test: isolate the cause step by step
Use this sequence when the VPN keeps disconnecting but the cause is unclear. The aim is not to make every setting more permissive; it is to find the smallest change that alters the result. If a step makes no difference, return any temporary setting to its previous value before continuing.
- Record the current setup. Write down the device, operating system, VPN client, selected server or route, protocol if shown, and network type. Note whether the disconnect follows sleep, a network change, or a particular app.
- Check the base connection. Disconnect the VPN and confirm that ordinary browsing works. If it does not, resolve the local network issue first. If a public network requires a sign-in page, complete that process before reconnecting.
- Retest on the same network. Reopen the VPN client, connect to the same route, and reproduce the action that normally precedes the drop. Keep other settings unchanged so the result remains useful.
- Test a different trusted network. Keep the same device, client, and route where possible. If the VPN is stable on another network, the original network may be restricting or interrupting the connection. If it drops on both, continue checking the client and device.
- Test another available server. Change only the server or route, then repeat the same activity. A result that changes with the route suggests the issue may be specific to that route or its current path, not necessarily to the whole client.
- Review protocol and reconnect options. If the client offers protocol choices, compare only those it supports and that are available for your configuration. Protocols such as WireGuard, Shadowsocks, VMess, Trojan, and Hysteria2 have different designs and are not interchangeable labels. Use the client’s documentation to determine which choices apply, and avoid copying a protocol-specific setting from another app.
- Test sleep or network switching separately. If the problem is tied to idle time, test sleep and wake without also changing the server. If it is tied to Wi-Fi-to-mobile switching, test that transition without changing other options. This identifies whether background behavior or network handoff is the trigger.
- Save the outcome and restore unnecessary changes. Keep the change that clearly resolves the issue, if it is safe and supported. Revert tests that make no difference. If you contact support, provide the symptom, client and operating system, network type, and steps already tested—never send passwords or private credentials.
When comparing providers or checking where to find the current client and account guidance, Q8VPN Best VPN for China is the starting point for the service information; the troubleshooting tests above should still be performed on your own device and network.
Useful result: If a different network fixes the issue, investigate the original network. If a different route fixes it, avoid assuming every server is affected. If the same failure follows the device across networks and routes, focus on its client, power settings, or other network software.
Compare protocols and servers carefully
A protocol can behave differently across network environments, but switching protocols without checking client support may create a new problem. Choose only options presented by your VPN client or documented for the configuration you imported. Don’t manually add protocol names, ports, or transport settings based on a generic online guide; those values are specific to the service, client, and configuration.
Server selection matters too. A route that fails once may be temporarily unreachable, while another route may work under the same conditions. Test a different available route and compare the result at the same time and on the same network. Do not infer a guaranteed speed or uptime from one successful test. If a route repeatedly fails while others remain stable, report the route name and the circumstances to the service’s support channel.
If you use rule-based routing, check whether the affected application is set to go through the VPN or use a direct connection. A client can display an active tunnel while a particular app follows a different rule. Review the app’s routing mode and domain or application rules before concluding that the entire VPN connection has dropped. For a basic diagnosis, use the client’s documented default or global mode only if it is safe and appropriate for your setup, then restore your preferred rules afterward.
When to contact support
Contact support when you can reproduce the disconnect, have confirmed that the underlying internet works, and have tested the client on another route or network without resolving it. A useful report is concise and specific: state the operating system and client, describe what the client shows when the drop happens, identify whether it occurs after sleep or a network change, and list the tests that changed or did not change the result.
If the client provides connection logs, check whether they can be exported safely and follow the service’s instructions before sharing them. Logs may include device details, server names, or other information you do not want to disclose. Remove account credentials, subscription URLs, authentication tokens, and private keys. Screenshots should also be reviewed for personal information before sending.
Reinstalling the client is not the first diagnostic step. It may remove a useful configuration or erase evidence of the failure without addressing a network or power-management cause. Consider reinstalling only after checking that you can restore the configuration from an official source and that simpler tests point to a damaged or inconsistent app setup.
Frequently asked questions
Why does my VPN disconnect when the screen locks?
Battery or background restrictions may suspend the VPN client, or the device may reduce network activity while idle. Check the client’s reconnect settings and the operating system’s background or power controls. Change one setting at a time and repeat the same lock-and-wake test.
Why does the VPN say connected while apps stop working?
The tunnel may still be active while the underlying internet has failed, a selected route is not responding, or a routing rule sends the affected app somewhere else. Check ordinary internet access with the VPN disconnected, then review the client’s route and app rules.
Should I change the VPN protocol?
Only test protocol options that your client and current configuration explicitly support. Protocols are not interchangeable, and settings from one client may not apply to another. Compare one supported option at a time and record whether the result changes.
Should I reinstall the VPN app?
Not as the first step. First compare VPN-on and VPN-off behavior, test another trusted network or route, and check sleep and background settings. If you do reinstall, confirm that you can restore the configuration from an official source and do not expose credentials while doing so.
Final takeaway: A reliable diagnosis comes from reproducing the drop and narrowing down one cause at a time. Separate internet problems from tunnel problems, test sleep and network changes deliberately, and use only client-supported settings. If the issue persists, a clear symptom record is more useful to support than a list of untracked changes.
Start Free