VPN Keeps Disconnecting? Troubleshoot Drops and Stay Connected

A VPN that connects successfully and then drops can be frustrating, especially when the interruption happens only after you lock your phone, switch networks, or start a particular app. The cause is not always the VPN server. Unstable Wi-Fi, mobile signal changes, battery management, a competing network filter, outdated configuration, or a client that cannot keep running in the background can all interrupt a tunnel.

Use a repeatable process instead of changing several settings at once. First note when the drop occurs, then check whether the underlying internet connection is still working. After that, test one change at a time: a different network, a different route, or another protocol offered by your client. This makes it much easier to identify the cause and explain the problem if you need support.

Identify the pattern before changing settings

Start by recording what “disconnecting” means on your device. Does the VPN app show that it has disconnected, or does the app remain connected while websites stop loading? Does the problem happen immediately, only after the screen turns off, during a video call, or when moving between Wi-Fi and mobile data? These details separate a tunnel failure from a general internet outage or an app-specific issue.

When the next drop happens, check the VPN client first. Note whether it shows a disconnected state, a reconnecting message, or an active connection. Then open a page or app that does not depend on the one where you first noticed the problem. If nothing loads, temporarily disconnect the VPN and check whether the ordinary internet connection works. Reconnect after this quick comparison. The goal is to distinguish a VPN interruption from a router, carrier, DNS, or destination-app problem—not to leave sensitive traffic unprotected for longer than necessary.

Write down the approximate time, device and operating-system version, client version, selected route, network type, and what you were doing when the interruption occurred. Avoid posting account details or a subscription link in a public forum: subscription links can function like credentials. If the client provides diagnostic logs, check whether they contain personal information before sharing them with anyone.

Look for a repeatable trigger. Drops that occur at the same place may point to weak Wi-Fi or mobile coverage. Drops that begin after the screen locks suggest background restrictions. A connection that fails only on one Wi-Fi network may be affected by the router or that network’s filtering. If the VPN indicator stays active but one website fails, the site or its app may be the issue rather than the entire tunnel.

Check your network, route, and competing connections

Test the internet connection without the VPN briefly, then compare it with the VPN connection on the same network. If ordinary browsing also fails, troubleshoot the Wi-Fi, router, or mobile connection before changing VPN settings. If ordinary browsing works but the VPN repeatedly drops, try a different route available in the client. A route that works well on one provider or network may not be the best choice on another, and a location label alone cannot predict how stable it will be for you.

For a useful comparison, keep the device in the same place and run the same ordinary task on each route. Avoid switching routes repeatedly in quick succession: that makes it difficult to tell whether a change helped, and some clients need time to establish a new connection. If a single route keeps dropping while another stays connected under similar conditions, note the difference and provide it to support. Do not assume that one brief successful connection proves the issue is permanently fixed.

Next, compare Wi-Fi with mobile data, or compare two Wi-Fi networks if available. If the connection is stable on one and not the other, the network environment becomes a useful clue. A crowded wireless channel, a router that restarts, weak signal, captive-portal login, or restrictions on long-lived connections can all affect a tunnel. On mobile data, moving between coverage areas or changing between network types can interrupt an active session. Reconnect after a network switch if the client does not recover by itself.

Check whether another app is managing network traffic. A second VPN, firewall, DNS filter, ad blocker, security app, or work-profile network tool may create a competing VPN interface or apply its own routing rules. Most devices do not let two VPN apps control the system tunnel in the way users expect. Close or pause the other network tool temporarily, test the VPN, and restore the other tool afterward if appropriate. Change only one such setting at a time so that you can identify which change matters.

If you are comparing providers or planning access while travelling, evaluate more than a location list: test connection recovery on the networks and devices you actually use. For an overview of the service and its access options, see VPNBall VPN for China Travel; for a disconnect that is already happening, continue with the device-level checks below.

Run a device-level test, then adjust background settings

Use this sequence to make a controlled test. Before starting, confirm that the client is updated through the appropriate source and that its configuration or subscription has refreshed successfully. Do not remove an account configuration or reset network settings as an opening move; those actions can erase useful information or create a separate setup problem.

1. Record the current state. Note the device, system version, VPN client version, selected route, network type, and whether the screen is on or locked when the drop occurs. If the client has a connection log, note the time of the event.
2. Confirm ordinary connectivity. Check whether other apps or sites work on the same network. If they do not, resolve the underlying connection problem first. If they do, reconnect the VPN and test more than one unrelated app.
3. Test without changing multiple variables. Keep the same device and network, then choose another route in the client. Observe whether the connection remains available during the activity that usually triggers the drop. If the issue continues, return to the original route before testing a different variable.
4. Check what happens when the screen locks. Keep the VPN connected, lock the device, and later check the client status. If it drops only in the background, review the operating system’s battery, background activity, and app-suspension settings for that VPN client.
5. Test a protocol option if available. Some clients offer more than one protocol or transport. Select an alternative only if it is actually listed in your client, reconnect, and repeat the same test. Protocol names and options vary by client and service; do not paste an unrelated configuration or force undocumented settings.
6. Save useful evidence. If the problem remains, capture the exact error message and relevant log entries. Include the time and the network and route used, but remove passwords, account tokens, and subscription links before sending anything.

On Android, open the VPN client’s app information and review battery or background-use controls. Some manufacturers add battery managers that can pause an app even when Android’s general settings appear permissive. Allow background activity for the VPN client if your system provides that option, and review any automatic app-sleep or power-saving rules. Menu names vary by device maker and Android version, so use the system’s app settings rather than following instructions for a different model blindly.

On iPhone and iPad, check whether the drop coincides with a switch between Wi-Fi and mobile data, Low Power Mode, or a change in signal. Keep the client current and reconnect after a network transition if it does not restore the tunnel. iOS controls background networking differently from desktop systems, so a setting described for Android may not exist on iOS. Avoid installing multiple VPN or profile-based network tools while diagnosing the issue.

On Windows and macOS, check whether sleep, lid closure, Wi-Fi roaming, or another network utility coincides with the interruption. A laptop may briefly lose its network during sleep or when changing access points. After waking, check both the operating system’s internet status and the client’s status before deciding which failed. On Linux, check the client’s own status and system network logs where available; desktop environments and network managers differ, so use documentation for the distribution and client you actually run.

Keep a kill switch or traffic-blocking option in mind while testing. If enabled, it may block traffic after a tunnel drops; that can look like a complete internet outage even though ordinary connectivity would otherwise return. Do not disable protective controls permanently just to make browsing resume. If you temporarily change such a setting for diagnosis, understand the exposure, perform a short test, and restore the protection afterward.

Check the client, protocol, and configuration

An outdated client, an incomplete configuration refresh, or a mismatch between the selected client and subscription format can cause connection problems. Confirm that you are using the intended client for your platform and that its configuration has been imported or updated successfully. If the client displays an update or parsing error, save the exact message before retrying. Repeatedly deleting and reimporting configuration without noting the original state can make diagnosis harder.

Protocol options are not interchangeable labels for speed. WireGuard, Shadowsocks, VMess, Trojan, Hysteria2, and other technologies have different roles and implementations; availability depends on the service, configuration, platform, and client. A third-party client may support a protocol in general but still not support a particular subscription format or feature. Use only options that are offered for your account and supported by the client you selected. If an option is absent, do not assume that a hidden menu or manually edited configuration is required.

When a protocol change is available, compare it fairly. Keep the device, network, route, and test activity the same, then record whether the client remains connected and whether traffic works. If the client reports a successful connection but applications cannot reach the internet, check for conflicting system proxies, DNS settings, or routing rules. If only one app fails, inspect that app’s proxy or network settings before concluding that the whole VPN is down.

For subscription-based configurations, refresh the subscription through the client’s normal update function if the service documentation recommends it. Do not share the link in screenshots, support chats that are not official, or public posts. If refreshing produces an error, record the client name and message and ask support which format and update method apply. A configuration refresh should not be confused with changing the account password or resetting the entire device network.

• ✅ Update the client from the intended, trusted source and note its version.
• ✅ Confirm the subscription or configuration is present and refresh it using the client’s normal workflow.
• ✅ Test another route or protocol only when it is offered by the client and account.
• ✅ Check whether a second VPN, firewall, DNS filter, or proxy is also managing traffic.
• ❌ Do not send a subscription link, password, or authentication token as a troubleshooting attachment.
• ❌ Do not import configuration files from an unknown source or edit protocol parameters at random.

It can also help to restart the VPN client after changing a system network setting. If that does not help, restart the device once and retest before reinstalling the client. Reinstallation may be reasonable when the app is damaged or an update failed, but first confirm that you can obtain the official client again and that you know how to restore the account configuration safely.

Know when to contact support: common questions

Contact support when the problem persists across more than one suitable route or network, the client reports a repeatable error, a subscription update fails, or a connection drops even after you have checked background restrictions and competing network tools. A precise report helps support distinguish an account or configuration issue from a device or network problem. Include the platform and system version, client name and version, approximate timestamps, the route and network type tested, the exact error text, and what changed after each test.

Do not include passwords, one-time codes, payment details, or a complete subscription URL in a general message. If support asks for a log, check whether the client can export a redacted diagnostic file and follow the official instructions for sharing it. Avoid sending a full screen recording if it exposes notifications, account information, or other private content.

Why does my VPN disconnect only on Wi-Fi?

That pattern suggests the Wi-Fi network, router, signal, or its handling of persistent connections may be involved. Compare with mobile data or another Wi-Fi network, and check whether the drop occurs in one location or after the router changes channels or restarts. If ordinary internet access also fails, troubleshoot the network itself. If only one Wi-Fi network causes the issue, give support that comparison rather than simply saying the VPN is unreliable everywhere.

Why does the VPN disconnect when I lock my phone?

Battery optimization or manufacturer-specific background management may be suspending the client. Review the VPN app’s battery and background-use permissions, automatic app-sleep rules, and any power-saving mode. Then repeat the same lock-screen test. If the client remains connected but apps stop loading, check whether the system is blocking traffic after a tunnel interruption or whether the device has lost its underlying network.

Should I change the protocol whenever a connection drops?

No. First determine whether the failure follows a particular network, route, device state, or app. If your client offers another protocol, testing it can be useful, but change one setting and compare under the same conditions. A protocol option that is not listed or documented for your client should not be added by guessing. Record the result so you can revert if it does not help.

What should I send to support?

Send the device and operating-system version, client and version, approximate time of the drop, network type, selected route, exact error message, and the checks you already performed. Explain whether ordinary internet access still worked and whether the issue appeared after screen lock or a network switch. Remove passwords and subscription links. If logs are requested, share them only through the service’s official support channel and review them for sensitive information first.

A VPN drop is easier to solve when the failure is narrowed down to a pattern. Check the underlying connection, compare networks and routes, review background restrictions, and test only the protocol options your client actually provides. If those steps do not identify the cause, a concise support report with safe, relevant diagnostics is the best next step.