A VPN that disconnects repeatedly can be frustrating, but the cause is often outside the VPN service itself. A weak Wi-Fi signal, a phone’s battery management, a network change, or a client setting can interrupt the tunnel. Start by identifying when the drop happens and whether the rest of your internet connection stays available. Then change one thing at a time: that makes it easier to find the cause and reverse a setting that does not help.
Identify the pattern before changing settings
First, distinguish a VPN disconnect from a general internet outage. When the VPN drops, check whether a normal website still loads after disconnecting the client. If it does not, the underlying Wi-Fi or mobile-data connection may be failing. If ordinary internet access works but the VPN client reports a disconnection, focus on the tunnel, selected route, protocol, or application settings.
Note what happens immediately before the drop. Does it occur when the screen locks, when you move between rooms, when a laptop wakes from sleep, or when the device switches from Wi-Fi to mobile data? Does it affect one network, one server, or every connection you try? A repeatable trigger is more useful than repeatedly reconnecting without recording what changed.
- ✅ Check whether other apps and websites still have internet access when the VPN disconnects.
- ✅ Record whether the drop follows a network change, sleep, screen lock, or app switch.
- ✅ Note the client’s exact status message and whether reconnecting restores service.
- ❌ Don’t change the protocol, server, DNS, and firewall settings all at once.
Also check whether the issue is limited to one app. If a browser stops loading but other apps work, the VPN tunnel may still be connected while a browser proxy, extension, or DNS setting is causing the problem. If every app loses access at the same time, look first at the network connection and the VPN client’s system-level settings.
Check the network and remove simple interruptions
Test the same device on a different connection, such as another Wi-Fi network or mobile data where available. If the VPN stays connected on the alternative network, the original router, access point, or network policy is a likely factor. If it disconnects in both places, investigate the device, client, account, or selected route instead. This comparison is more informative than restarting every device at the same time.
On Wi-Fi, move closer to the access point and see whether the connection becomes stable. A device can remain associated with Wi-Fi even when signal quality is poor or the route to the router is intermittent. If other household devices also lose access, restart the router according to its instructions and check whether its connection is stable without the VPN. Avoid changing router firewall or DNS settings unless you know how to restore the original values.
Look for network transitions. A phone may switch between Wi-Fi and cellular data as signal conditions change; a laptop may roam between access points or reconnect after waking. Some clients can reconnect automatically, but the transition can still interrupt an active session. If a drop happens only during a switch, test the VPN separately on each network and review the client’s reconnect options.
Captive portals can also interrupt a tunnel. Hotels, airports, cafés, and other managed networks may require you to accept terms or sign in before normal internet access is allowed. Disconnect the VPN, complete the network’s sign-in page, confirm that ordinary internet access works, and then reconnect. If the network blocks or limits VPN traffic, use another trusted connection or ask its administrator about permitted access rather than trying to bypass its controls.
A restricted office or school network may have similar limitations. If the VPN works elsewhere but not on that network, the network administrator may be filtering protocols or maintaining connection rules. Do not assume that changing encryption or repeatedly reconnecting will solve a policy restriction. Follow the organization’s network rules and use an approved connection method.
Review background, battery, and sleep settings
Phones often reduce background activity to conserve battery. Depending on the operating system and device manufacturer, this can delay a VPN app’s reconnect attempt or restrict its network access while the screen is off. Open the system’s battery and app settings, find the VPN client, and review whether background activity, unrestricted battery use, or automatic launch is available. The names and locations of these controls vary by device and operating-system version.
On Android, check the app’s battery usage and background-data permissions. Some manufacturers add their own battery manager that can stop apps more aggressively than Android’s standard settings. If the connection drops after the screen locks, test with battery optimization relaxed for the VPN client, then lock the screen and observe whether the behavior changes. Keep the adjustment limited to the VPN app rather than disabling battery protections for every application.
On iPhone and iPad, review the VPN app’s permissions and any available background or on-demand connection options. iOS manages background activity, and not every app can remain continuously active in every situation. A network handoff, device restart, or system update may require the client to reconnect. If the client offers a reconnect or on-demand option, enable it only if it matches your usage and the available controls are clearly described.
On Windows and macOS, test whether the VPN disconnects after sleep or when the network adapter changes state. Install operating-system updates and client updates from their official sources, then restart the device if an update requires it. On Windows, power-saving settings for a wireless adapter may affect connectivity; on macOS, check whether the drop consistently follows sleep, wake, or a change in the active network. Avoid removing a network extension or adapter unless the client’s documentation gives a clear recovery procedure.
Linux users can check whether the desktop network manager, VPN client, and any system service agree about which connection is active. A laptop may suspend its network adapter during sleep, and a client launched only within a desktop session may not reconnect in the same way as a system-managed service. Check the distribution’s network settings and the client’s own logs before changing service files or firewall rules.
Finally, close duplicate proxy and VPN tools temporarily. Two clients trying to control the system proxy, routing table, DNS, or virtual network interface can interfere with one another. Browser-only proxy extensions can also make a single browser behave differently from the rest of the device. Exit other tools cleanly, reconnect with one client, and compare the result.
For a general overview of the service and its supported platforms, see VPN61 VPN for China Travel. Keep that separate from troubleshooting: a product overview does not replace checking the device and network where the disconnections occur.
Test the client, server, and protocol carefully
Make sure the client is up to date and that its subscription or configuration is still available. If the app displays an authentication, subscription, or configuration error, address that message before testing network changes. A client can appear to connect briefly and then close the tunnel if required configuration is missing or no longer valid. Sign out and back in only if the app’s instructions recommend it, and keep any required account details secure.
Try another server or route if the client provides one. A single route can be temporarily unavailable or unsuitable for a particular network, while a different route may connect more reliably. Change only the selected route and keep the protocol and device settings the same for the first comparison. A successful connection on another route points toward a route-specific issue, but it does not prove that the original route is permanently unavailable.
If the client offers protocol choices, test another supported option and note the result. Protocols differ in how they establish and maintain a connection, and networks may treat their traffic differently. No protocol is guaranteed to work on every network. Return to the original choice if the alternative performs worse, and avoid selecting an unfamiliar protocol just because its name sounds faster or more secure.
It is also useful to distinguish a VPN tunnel from a proxy configuration. Some compatible clients can use system proxy mode, application-specific proxy rules, or a TUN interface that routes broader device traffic. If a client says it is connected but some apps do not work, check which mode is active and whether those apps are included in its rules. A browser proxy does not necessarily cover every application, and rule-based routing can intentionally send some traffic outside the tunnel.
Keep a brief record of each test: network, route, protocol, client version, and whether the connection stayed active during the condition that normally causes the drop. Avoid recording passwords, private keys, or full account credentials in notes or support messages. If you share diagnostic logs, check whether they contain personal details and use the provider’s official support channel.
Follow a practical test sequence
Use this sequence to narrow down repeated drops without changing more than necessary. After each step, reproduce the same situation that usually causes the disconnection. If the issue disappears, keep the successful setting and make a note of it before trying anything else.
- Confirm ordinary internet access. Disconnect the VPN and test a few normal apps or websites. If they also fail, troubleshoot the Wi-Fi, mobile-data connection, router, or captive portal first.
- Reconnect once and note the message. Write down the client’s displayed error or status and the action that came just before it. Avoid repeated rapid reconnects, which can make it harder to identify the original failure.
- Compare networks. Keep the same device, client, route, and protocol, then test on another trusted network. If only one network causes drops, investigate that network or its access rules.
- Check background and sleep behavior. Review the VPN app’s battery and background permissions, and test whether screen lock, sleep, or wake triggers the issue.
- Update and simplify. Update the client and operating system through official channels, restart the device if appropriate, and temporarily close other VPN or proxy applications.
- Change the route. Select another available server or route while keeping other settings unchanged. Record whether it connects and whether it survives the usual trigger.
- Test another protocol. If the client provides more than one supported protocol, compare them one at a time and return to the previous setting if the new one does not help.
- Collect useful diagnostics. If the problem remains, note the device and operating-system version, client version, network type, error text, and tests already completed. Do not send passwords or secret configuration values.
A kill switch, if enabled, may block internet access when the VPN tunnel is down. That behavior can make a drop look like a complete network outage, but the kill switch does not necessarily cause the tunnel to disconnect. Check the client’s status and reconnect the VPN before changing this protection. If you temporarily disable a kill switch to test connectivity, do so only when you understand the privacy trade-off, and restore the setting afterward.
DNS errors can also be mistaken for disconnections. If the VPN client still reports an active connection but domain names fail to load, compare a different app or check the client’s DNS and split-tunneling settings. Do not enter unfamiliar DNS addresses copied from an unverified source. If changing DNS is necessary, record the previous setting so you can restore it.
Know when to contact support
Contact the provider when the client repeatedly fails on more than one network, the same issue persists after a client update and restart, or a clear error points to an account or configuration problem. A concise report is more helpful than saying only that the VPN is unstable. Include the device platform, operating-system and client versions, the approximate circumstances of the drop, the exact error text, and which routes or protocols you tested.
Explain whether ordinary internet access remains available when the tunnel drops. Mention if the problem happens only after sleep, screen lock, or a network change, and say whether another route behaves differently. If logs are requested, provide them through the official channel and review them for sensitive information first. Support should not need your password or private key to diagnose a connection issue.
Do not install unofficial client builds or configuration files sent by unknown accounts. If you need to reinstall, use the official distribution channel and follow the provider’s instructions. Keep your existing account and subscription information available, but do not post it publicly while asking for help.
FAQ: VPN connections that keep dropping
Why does my VPN disconnect when I lock my phone?
Battery management or background restrictions may limit the client while the screen is off. Review the VPN app’s background and battery permissions, then test whether the connection remains active after locking the device. Operating-system behavior and available options vary, so use the settings provided by your device rather than applying a generic change to every app.
Why does the VPN drop only on one Wi-Fi network?
The access point may have an unstable connection, a captive portal, or rules that affect VPN traffic. Confirm ordinary internet access, complete any sign-in page, and test the VPN on another trusted network with the same route and protocol. If the issue is limited to a managed network, follow its rules or ask its administrator about permitted connections.
Should I switch protocols whenever the VPN disconnects?
Not immediately. First check the underlying internet connection, the client’s status, and whether the problem is limited to one network or route. If the client supports alternative protocols, test one at a time and compare it under the same conditions. A protocol change is a diagnostic step, not a guarantee that the connection will become stable.
Does a kill switch cause the VPN to disconnect?
Usually, its purpose is to block traffic if the VPN tunnel is already down, which can make internet access appear unavailable. Check the client’s connection status before changing the setting. If you test with the kill switch disabled, understand that traffic may no longer be blocked during a drop and restore your preferred protection afterward.