A VPN that repeatedly disconnects can interrupt browsing, streaming, downloads, and work calls. The cause is not always the VPN service itself: Wi-Fi roaming, a sleep or battery setting, a network change, a conflicting security tool, or a client configuration can all break an otherwise usable connection. Start by identifying when the drop happens, then change one setting at a time so you can tell which adjustment matters.
This guide covers seven checks that apply across Windows, macOS, Android, iOS, and Linux, although menu names differ by client and operating system. A VPN app may create a system-level tunnel, while compatible proxy clients can route traffic in other ways; the exact recovery behavior depends on that implementation. A browser that reconnects successfully does not necessarily mean every app has recovered, so test the apps you actually use.
Identify the Drop Pattern Before Changing Settings
First note what “disconnecting” means on your device. The client may show that its tunnel has ended, the tunnel may remain connected while websites stop loading, or only one app may lose access. These symptoms point to different layers of the connection. A tunnel that closes suggests checking the network, client, protocol, or operating-system settings. A connected status with failed browsing may instead involve DNS, routing rules, or the destination app.
Record the circumstances in plain language: whether the drop happens after waking the device, switching between Wi-Fi and mobile data, locking the screen, joining a meeting, or using a particular network. Also note whether other websites and apps continue working without the VPN. Avoid changing several items at once or repeatedly reinstalling the client before you know what the failure looks like; doing so can remove useful clues without addressing the cause.
7
checks in this guide
5
platforms covered
1
change to test at a time
Keep a short log rather than relying on memory. Include the approximate time, network type, device state, client status, and the action that restored access, if any. Do not record passwords, private keys, subscription URLs, or other credentials in that log. If the problem later needs support, a concise record is more useful and safer than sending a screenshot that exposes account details.
Seven Practical Fixes to Try
Fix 1: Check the underlying network
When the VPN drops, temporarily disconnect it and check whether the device can use the network normally. If the connection also fails without the VPN, investigate the Wi-Fi, router, mobile-data signal, or network login page first. A captive portal at a hotel, school, or public hotspot may require sign-in before a tunnel can remain connected. Complete that sign-in through the network’s normal process, then reconnect the VPN.
If the base connection works, compare another trusted network when practical, such as a different Wi-Fi access point or mobile data. Do not assume that every network permits the same tunnel behavior: managed, public, and workplace networks can apply different firewall or access rules. If a connection works on one network but repeatedly drops on another, preserve that comparison for troubleshooting instead of changing unrelated client settings.
Fix 2: Check sleep, battery, and background activity
Phones and laptops may restrict background activity to conserve power. On Android, review the VPN app’s battery usage and background restrictions; menu labels vary by manufacturer. On iOS, check whether the app is allowed to operate as configured and whether Low Power Mode or a network transition coincides with the drop. On Windows and macOS, note whether the failure follows sleep, lid closure, or a power-saving state, then review the relevant power and network options.
Make a small, reversible test rather than disabling battery management across the device. Allow the VPN client the background access it needs, reconnect, lock or sleep the device in the same way that previously triggered the issue, and check whether the tunnel recovers. Restore the original setting if the test makes no difference. Avoid broad battery exemptions for unrelated apps.
Fix 3: Test a different supported protocol or route
Networks can handle protocols differently. Depending on the service and client, a configuration may use a protocol such as WireGuard, OpenVPN, IKEv2, Shadowsocks, VMess, Trojan, or Hysteria2; support varies, and these protocols are not interchangeable. Only select an option that both your service configuration and client explicitly support. If the client offers a supported alternative, test it under the same network conditions and note whether the symptom changes.
A protocol change can affect compatibility, but it is not a universal fix. Likewise, switching to another available node or route can help identify whether a particular endpoint is involved, but a single successful connection does not prove the old route was permanently at fault. Change one option, observe the result, and return to the previous setting if the new one performs worse or prevents connection.
Fix 4: Check for conflicting VPNs, proxies, and security software
Two VPN clients active at once can compete for the system tunnel, routing table, DNS settings, or virtual network interface. Close other VPN and proxy apps before testing one client by itself. Also check whether a manual system proxy, firewall rule, antivirus network filter, or corporate endpoint tool changed around the time the drops began. Do not disable essential security controls on a work-managed device; ask the administrator whether the configuration is expected.
On desktop systems, virtual adapters left by an old client can sometimes complicate network behavior. Prefer the client’s normal disconnect and exit controls first. Avoid deleting adapters, resetting firewall rules, or removing system certificates unless the client’s official instructions or a qualified administrator specifically recommends it. These changes can disrupt other network tools and may be difficult to reverse.
Fix 5: Refresh the configuration and inspect routing
If your client uses an imported configuration or subscription, confirm that the intended profile is selected and that its update completed. A profile can be present without being current, and a client may display several similarly named entries. Refresh it using the provider’s documented process, then reconnect. Never paste a private subscription link or authentication details into a public forum or an untrusted configuration checker.
Compatible clients such as Clash Verge, sing-box, and Shadowrocket use their own configuration and routing features; names and behavior vary by version and setup. A routing rule may send some traffic directly, through a proxy, or to a blocked route. If the tunnel status remains active but a specific app fails, check whether its traffic matches the intended rule before concluding that the entire VPN connection has dropped. Do not edit unfamiliar rules blindly: save a backup and change only the rule you understand.
For readers comparing service options and setup approaches, VPNGF Best VPN for China is the site’s home page. For this troubleshooting step, however, focus on the configuration already in use and verify that it is compatible with the client that imported it.
Fix 6: Check DNS and local network access
Sometimes the tunnel is still established but names no longer resolve, making the problem look like a disconnection. Compare access to more than one destination and, if available, check the client’s connection status and logs for DNS or routing errors. A temporary DNS failure, a rule sending DNS requests along the wrong path, or a local network conflict can affect browsing even when the tunnel indicator has not changed.
If the client has a documented DNS setting, record the current value before testing an alternative supported option. Also consider whether you need to reach a local printer, router, file server, or company intranet. Some configurations deliberately route local addresses directly; others may handle them differently. Avoid applying random DNS addresses or disabling leak protection without understanding the consequences. If only one website or app fails, check its own network requirements too.
Fix 7: Update and restart in a controlled order
Check that the VPN client and operating system are supported and up to date through their official distribution channels. If the problem began immediately after an update, note the version and timing; do not assume that reinstalling an older build is safe or supported. Restart the client first, then test. If that does not help, restart the device and repeat the same test on the same network.
Before reinstalling, make sure you know how to restore your configuration and regain account access. A clean reinstall can remove profiles, certificates, or custom routing rules. Follow the client’s instructions, and avoid downloading installers from unofficial mirrors. If the client repeatedly exits, preserve relevant logs before removing it, while checking that those logs do not include credentials or private configuration data.
- ✅ Compare the connection with and without the VPN to separate network faults from tunnel faults.
- ✅ Record when the drop happens, then test one reversible setting at a time.
- ✅ Use only protocols and configuration options supported by both the client and service.
- ❌ Do not run two VPN clients simultaneously while diagnosing a tunnel problem.
- ❌ Do not share subscription links, passwords, private keys, or unredacted diagnostic logs.
Run a Repeatable Test on Your Device
Once you have checked the likely causes, use a simple comparison so the result is meaningful. Start on the network where the issue usually occurs and keep the device in the same power state. Do not change the protocol, route, battery setting, and DNS option together: if the connection improves, you would not know which change mattered, and if it worsens, returning to a known configuration becomes harder.
- Confirm the baseline. Check that ordinary internet access works with the VPN disconnected. If it does not, address the underlying network or sign-in requirement first.
- Connect and observe. Select the intended profile and route, connect once, and note whether the client reports an established connection. Test a few ordinary apps that represent your actual use, rather than relying on one webpage.
- Reproduce the trigger. If drops usually follow screen locking, sleep, Wi-Fi roaming, or a particular app, repeat that condition without changing other settings. Note whether the tunnel disconnects, stays connected without traffic, or reconnects automatically.
- Change one setting. Choose the setting most closely related to the symptom, such as background permission after screen lock or a supported protocol on a particular network. Save the original value so you can restore it.
- Compare and revert when needed. Repeat the same test under similar conditions. Keep a change only if it addresses the problem without breaking other needed access; otherwise restore the original value and test the next likely cause.
This process helps distinguish an intermittent base network from a client recovery issue. It cannot guarantee that every drop will be reproduced: networks change, and a brief interruption may not happen during a short test. If the behavior is inconsistent, keep the log over the times you normally use the device and avoid describing a single successful reconnect as proof that the issue is permanently fixed.
When to Contact Support
Contact the VPN provider or client maintainer when the base network works, the configuration appears current, and the tunnel still drops consistently after the relevant checks. Provide your operating system and version, client name and version, the network type, the approximate time of the failure, and whether it happens after a specific action. Say whether the client reports a disconnection or stays connected while traffic stops. These details help narrow the issue without requiring you to send sensitive information.
If the problem occurs only on a workplace, school, or public network, ask its administrator whether VPN traffic is restricted or whether a device policy controls the network. If it happens only on one device, compare its settings with another device using the same network and configuration, where permitted. If it happens across multiple devices on one network, the network path is a more useful lead than repeatedly reinstalling every client.
Share diagnostic logs only through an official support channel and inspect them first. Redact account identifiers, access tokens, subscription URLs, internal addresses, and any other private information. Do not send a full configuration file unless support explains why it is needed and provides a secure way to receive it. If the device is managed by an employer or school, follow its support process before changing system-level routing, certificates, or security settings.
VPN Disconnection FAQ
Why does my VPN disconnect when I lock the screen?
Battery or background restrictions may pause the client, but the cause can also be a sleep policy, Wi-Fi transition, or client-specific recovery behavior. Check whether the drop happens only while locked, review the app’s background permissions, and repeat the test without changing unrelated settings. On a managed device, an administrator may enforce these policies.
Why does the VPN say connected when apps cannot reach the internet?
The tunnel indicator describes the client’s connection state, not necessarily successful DNS resolution or correct routing for every app. Check more than one destination, review DNS and routing rules, and see whether the affected app is expected to use the proxy. If only one app fails, check its own proxy support and network requirements.
Should I switch VPN protocols to stop disconnections?
Only test another protocol if the service configuration and client both support it. Different networks may handle protocols differently, so a controlled comparison can be informative, but switching is not a guaranteed remedy. Record the original option and change only that setting during the test.
What information should I send to support?
Share the device and operating-system version, client version, network type, time and pattern of the drop, and whether the client disconnects or remains connected without traffic. Redact credentials and private configuration details from screenshots or logs. Never post a subscription link, password, access token, or private key publicly.
If the connection still drops after these checks, keep the original configuration available and send the concise troubleshooting record through an official support channel. This gives support a clear starting point while avoiding unnecessary changes to your device.