VPN Keeps Disconnecting? Troubleshooting Steps That Work

A VPN that repeatedly disconnects is frustrating, but the cause is often something local: a change between Wi-Fi and mobile data, an operating-system power setting, or a client that cannot keep running in the background. Start by identifying when the drop happens instead of changing several settings at once. That makes it easier to distinguish a device problem from an unstable network, an outdated configuration, or a service-side issue.

Identify when the VPN disconnects

“The VPN drops” can describe several different symptoms. The client might show that it has disconnected, remain connected while websites stop loading, or reconnect after a network change but take too long to restore traffic. Those symptoms point to different parts of the connection. Before resetting an app or replacing its configuration, note what the client reports and what else changes at the same time.

Try to observe the pattern over more than one occurrence. Does the drop happen when the screen locks, when you leave home Wi-Fi, when a laptop wakes from sleep, or only on a particular network? Does it affect every app or just one website? A brief interruption during a network handoff is different from a connection that fails repeatedly on an otherwise stable Wi-Fi network.

• Test the ordinary connection: Disconnect the VPN briefly and check whether the same websites or apps load. If they also fail without the VPN, troubleshoot the Wi-Fi, mobile data, router, or captive portal first.
• Check the client status: Look for a disconnect message, a reconnecting indicator, a permission prompt, or a subscription update notice. If the status says connected but all traffic stalls, the issue may be a route or DNS setting rather than a lost tunnel.
• Compare networks: If it is safe and practical, test on another trusted network. A problem limited to one Wi-Fi network may involve its router, firewall, or network policy.
• Record the trigger: Note whether the screen was locked, the device changed networks, or the client was updated. This gives you and support a useful starting point.

A small amount of observation prevents a common mistake: repeatedly switching servers when the actual cause is that the operating system has paused the app. It also helps identify whether a drop affects one device or all devices using the same subscription. If more than one device shows the same issue at the same time, compare their networks and client configurations before assuming that each device has an independent fault.

Check network handoffs and auto-reconnect

Moving between Wi-Fi and cellular data changes the device’s network interface and often its local address. The VPN client then has to establish a connection over the new path. A short interruption during that transition can be normal; a client that stays disconnected afterward may need its reconnect setting enabled, a fresh network connection, or a configuration refresh.

Open the VPN client’s settings and look for options with names such as Auto-reconnect, Reconnect on network change, or Start on launch. Names and availability differ between apps and operating systems. Enable only the options that match your needs, and read any explanation about when the client reconnects. A setting that reconnects after a network handoff does not necessarily mean the VPN will start automatically after every reboot.

Then test the handoff deliberately. Connect on a trusted Wi-Fi network, switch to mobile data if available, and wait for the client to show its final state. Repeat the test in the opposite direction. If the client recovers on one type of handoff but not the other, note the direction and the network involved. Avoid making several changes during the same test, because you will not know which one made a difference.

On a computer, also check what happens after sleep or lid closure. Some systems suspend network activity while sleeping; on wake, the client may need a moment to renegotiate its connection. If it remains offline, disconnect and reconnect once, then check whether a client update or system network change is available. Do not assume that enabling a generic “always-on” option in the operating system is equivalent to enabling reconnect behavior inside the VPN app; they can control different parts of the process.

When traveling, a hotel, airport, or café network may require you to accept a captive-portal notice before normal internet access is available. If the VPN attempts to connect before the network login is complete, it may appear to fail repeatedly. Complete the network’s sign-in using its official page, confirm that ordinary internet access works, and then reconnect the VPN. If your use case involves choosing a service for a trip, the VPNRS VPN for China Travel page provides the service overview; it does not replace checking the client and network settings on the device you are using.

Allow the client to run in the background

Phones and laptops may limit background activity to save power. If the VPN works while the app is open but drops after the screen locks, the operating system may be suspending the client or restricting its network access. Review the device’s battery, background-app, and network-permission settings for the VPN client. The exact names vary by operating-system version and device manufacturer, so use the system settings search if you cannot find the relevant controls.

Android

On Android, check the app’s battery usage settings and remove a restrictive battery mode for the VPN client if the system offers that choice. Also review background data access, data-saver exceptions, and any manufacturer-specific app-management settings. Some Android devices include additional controls that automatically put infrequently used apps to sleep. If the VPN is listed among sleeping or deeply sleeping apps, allow it to remain active while connected.

After changing a restriction, reconnect and lock the screen for a normal period, then check the client status when you return. Avoid turning off every battery safeguard on the device. The goal is to permit the VPN app to maintain its connection, not to remove power management for unrelated apps. If the client still disconnects, restore any setting that did not help and test the next likely cause separately.

iOS

On iPhone or iPad, confirm that the VPN configuration is still approved in system settings and that the client has not been removed, offloaded, or signed out. If a system prompt appears after an update or reinstall, read it and approve the configuration only when you recognize the app and intended action. Low Power Mode and app lifecycle changes can affect when apps refresh; test the VPN with the app open as well as after locking the screen to see whether the failure is tied to background operation.

Windows and macOS

On Windows, check whether the client is allowed through the system firewall and whether a security product is blocking it. If the problem began after a network adapter, firewall, or client change, review that change before reinstalling the app. On macOS, confirm that the VPN or network extension remains enabled in the relevant privacy and network settings. A system update can require renewed approval for a network extension, so look for a pending permission rather than repeatedly importing the subscription.

For every platform, use the provider’s official client instructions or the documentation for the exact compatible client you installed. An app’s background behavior and configuration options are not interchangeable across Windows, macOS, Android, iOS, and Linux. Keep the client updated through its official distribution source, but avoid installing a similarly named app based only on its icon or search ranking.

Test a different protocol or server

If the ordinary internet connection is stable, the client has permission to run, and reconnect settings are enabled, test the connection route. First update the subscription or configuration through the client’s normal import or refresh function. A subscription link can provide updated route information; it is not the same thing as the username and password used to access an account dashboard. Keep the link private because it can contain access credentials.

Next, select a different server or route in the client and test again on the same network. Choose a nearby or otherwise suitable location when the provider offers that choice, but do not treat a different server as a guaranteed fix. A route change is useful as a diagnostic comparison: if one route disconnects and another remains stable under the same conditions, report both route names and the time of the tests to the provider.

If the client offers protocol choices, change only that setting and repeat the same test. Depending on the provider and client, configuration options may include protocols or proxy technologies such as WireGuard, Hysteria2, Trojan, VMess, or Shadowsocks. Not every service offers every option, and the menu labels do not mean the protocols are interchangeable in every network environment. Some networks handle certain connection styles differently, while client support and available settings also vary.

After changing a protocol, verify that the client successfully loaded the intended configuration and reports a connected state. Then test an ordinary website and, if relevant, the specific app that previously failed. If the new protocol makes no difference, switch back before trying another change. Avoid running two VPN or proxy clients at the same time: overlapping routes, DNS settings, or virtual network adapters can create confusing symptoms and make a successful connection appear broken.

People using third-party clients such as Clash Verge, sing-box, or Shadowrocket should confirm that the imported subscription format and selected mode are supported by that particular app. A client may import some route entries but not reproduce every provider-specific policy group or automatic update behavior. Check the client’s own status and configuration diagnostics, and compare with the provider’s recommended client if the service documents one. The aim is to isolate whether the issue lies in the network, the operating system, the client, or the selected route—not to assume that one application is universally more stable.

When to contact support and common questions

Contact the VPN provider when the same issue continues after you have confirmed ordinary internet access, reviewed background permissions, enabled suitable reconnect behavior, and tested another route or protocol where available. Send concise, useful details: device and operating-system version, client name and version, the network type, the approximate time of the drop, the client’s exact status or error, and the steps you already tried. Include whether the issue happens on one route or several.

Do not send a password, private key, or unredacted subscription link in a public post or ordinary screenshot. If support requests a diagnostic log, review it for personal information before sharing and use the provider’s official support channel. If the problem began immediately after a client or operating-system update, mention that timing. A clear report helps support distinguish a local permission issue from a configuration or route problem without asking you to repeat basic checks.

Does a drop always mean the server is down?

No. The device may have switched networks, paused the client in the background, lost ordinary internet access, or applied a restrictive power setting. Check whether the internet works without the VPN and whether the client reports a disconnect before concluding that a server is unavailable.

Why does it disconnect when the screen locks?

A battery or background-app restriction may be suspending the client, particularly on mobile devices. Review the VPN app’s background and battery permissions, then test with the screen locked. If the client stays connected only while open, report that specific pattern to the provider or app developer.

Should I change protocols first?

Usually not. First confirm that the device’s internet works, check reconnect behavior, and allow the client to run in the background. If those checks do not resolve the issue, a single protocol comparison can help identify whether the current connection type is incompatible with the network you are using. Restore the original setting if the test does not help.

What information should I send to support?

Provide the device and operating-system version, client and version, network type, route or server name, error text, and the steps that reproduce the disconnection. Say whether the issue occurs on more than one network or device. Do not include passwords or expose a subscription link in a public message.