A VPN that keeps disconnecting is frustrating, but reinstalling the app is rarely the best first move. A dropped connection can come from a changing Wi-Fi or mobile network, a device power setting, an outdated client, a conflicting VPN profile, or a server that is temporarily unreachable. The useful clue is not just that the connection dropped, but when it happened and whether other apps lost connectivity at the same time.

Work through the checks below in order. Start with the least disruptive changes, keep track of what you alter, and test after each step. That makes it easier to identify the cause instead of changing several settings at once and not knowing which change helped.

Start by separating a VPN problem from an internet problem. If the device loses ordinary internet access when the VPN disconnects, troubleshoot the local network first. If the internet continues working but the VPN drops, focus on the client, its permissions, protocol, and selected server.

Identify when the connection drops

Before changing settings, note what was happening immediately before the disconnect. Did it happen after the screen locked, when the computer woke from sleep, when you left home Wi-Fi, or after switching from Wi-Fi to mobile data? Does it happen only with one app or one server, or across different networks? These patterns narrow the search far more quickly than repeatedly tapping Connect.

7

Troubleshooting checks

4

Issue areas: network, device, app, server

Run a simple comparison. Disconnect the VPN and open a page or app that normally works. Then connect again and repeat the check. If ordinary internet access also fails with the VPN off, restarting or changing the VPN protocol is unlikely to solve the underlying problem. If basic access works without the VPN but fails as soon as it connects, continue with the client and server checks.

  • ✅ Record whether the drop follows sleep, a network change, or a particular app.
  • ✅ Compare basic internet access with the VPN disconnected and connected.
  • ❌ Avoid changing the protocol, server, and device settings all at once.

Check your network and device

1. Stabilize Wi-Fi or mobile data

A VPN depends on a working connection underneath it. Weak Wi-Fi coverage, an overloaded access point, a captive portal, or an unstable mobile signal can interrupt the tunnel even when the VPN app itself is behaving normally. Move closer to the router or try a different trusted network. If you are on public Wi-Fi, make sure the network’s sign-in page has been completed before connecting the VPN.

When the issue appears on only one network, compare it with another connection rather than changing several settings on the device. For example, test on a home Wi-Fi network and then on mobile data, if your plan and local conditions allow. If the VPN stays connected on one but not the other, the difference points toward the access network, its restrictions, or its stability. A VPN cannot repair a broken Wi-Fi connection or guarantee uninterrupted service through a weak signal.

2. Review sleep and background settings

Some devices restrict background activity to save power. A VPN app may be paused when the screen turns off, the device enters a battery-saving mode, or the operating system limits background data. Check the system’s battery and background-app settings for the VPN client. Where available, allow the app to run in the background and avoid aggressive battery optimization while testing.

On a laptop, check whether disconnects happen only after sleep or when the lid is closed. Wake the device, wait for the network connection to return, and then see whether the VPN reconnects. If it does not, disconnect and reconnect the client once the operating system has restored Wi-Fi. This helps distinguish a normal interruption during sleep from a client that cannot recover after the device resumes.

3. Confirm permissions and profiles

On phones and tablets, the operating system may ask for permission to add or manage a VPN configuration. If that permission was denied, removed, or replaced by another app, the client may fail to establish or maintain its connection. Open the device’s VPN settings and check whether the expected profile is present and enabled. If you recently installed another VPN, firewall, DNS filter, or network-monitoring app, temporarily disable it for a controlled test; two apps trying to manage network routing can conflict.

On desktop systems, check whether the client is allowed by the operating system’s firewall and whether another security or endpoint-management tool is blocking it. Do not turn off security protections broadly just to test. If a managed work or school device enforces network policies, ask the administrator whether VPN connections or particular protocols are restricted.

Work through the client checklist

Once the underlying network looks stable, inspect the VPN client itself. Confirm that you are using the official app or a compatible client from a trusted source, and install available updates through that source. An old client may not handle current operating-system behavior or the service’s configuration correctly. Before updating, note the settings you rely on, such as automatic connection, routing mode, and any custom server selection.

Then check whether the client is set to reconnect automatically. The wording varies between apps: it may be called auto-reconnect, connect on demand, or always-on behavior. If automatic reconnection is available, enable it and test after a brief network interruption. On a device that changes networks frequently, such as a phone moving between Wi-Fi and cellular, the client may need permission to continue running and to react to network changes.

If you use a third-party client such as Clash Verge, sing-box, or Shadowrocket, verify compatibility between the client version, the subscription format, and the protocols in the configuration. A subscription URL is a way to import configuration; it does not make every client support every protocol or transport. Refresh the subscription from the service’s official source, check for an import or parsing error, and avoid editing generated configuration values unless you know what they control.

Some clients offer system-proxy mode, while others can route traffic through a virtual interface or TUN mode. These modes do not behave identically. If the app reports a connection but the expected traffic is not working, check that the selected mode matches your use case and that the operating system granted the required permissions. For a disconnect issue specifically, first test with the client’s standard recommended mode before adding custom routing rules.

4. Make one change at a time

Use this short procedure to keep the test readable:

  1. Note the device, operating system, client version, network type, selected server, and the approximate time of the drop.
  2. Connect to a trusted network and confirm that ordinary internet access works before starting the VPN.
  3. Connect using the client’s standard settings and keep the same server while checking whether the problem returns.
  4. Change one item only, such as the server or protocol, and repeat the same check under comparable conditions.
  5. Write down the outcome, then restore the original setting if the change makes the connection less stable.

If you need a place to review the service’s available options and general setup information, VPNSon VPN That Works in China is the site homepage. Use the relevant client’s own instructions for importing a subscription or configuration, because the exact steps depend on the platform and app.

When the client offers connection logs, look for the time of the disconnect and the surrounding error message. Logs can indicate whether the client lost its network, could not reach the server, or rejected a configuration. Do not post a full configuration or subscription link publicly: these may contain account-specific information. If you contact support, share the device platform, client name and version, network type, server selection, and a brief description of the error instead.

Test a different server or protocol

If the connection drops on one server but remains stable on another, the issue may be specific to the selected server or route. Try another server that is appropriate for your location and task, then repeat the same test. Avoid rapidly cycling through many servers: a controlled comparison gives you more useful information, while repeated switching can make it difficult to tell whether a change in network conditions caused the result.

If the client and service offer more than one supported protocol, a protocol change can be a useful diagnostic step. Protocols differ in how they establish and maintain connections, and networks may treat them differently. Compatibility also depends on the client implementation and server configuration. Choose only an option supported by both your client and service; selecting a protocol that the imported configuration does not provide will not improve reliability.

Keep the network, device, and general test conditions as similar as possible while comparing. If one protocol or server works better, record that combination and use it as a temporary workaround. If every available option disconnects on the same network, return to the network checks rather than assuming that changing protocols will overcome the local connection problem.

Change servers and protocols as tests, not guesses. A stable result on an alternative can help isolate a route or compatibility issue. If the pattern does not change, look again at the device, underlying network, or client configuration.

Handle network changes and sleep

Moving between access points or switching from Wi-Fi to mobile data can briefly interrupt an active connection. Some clients reconnect automatically; others may need a moment after the operating system finishes changing networks. If drops happen during transitions, enable the client’s reconnect option where available and check that background activity is permitted. For a controlled test, stay on one network first, then deliberately change networks once and observe whether the client recovers.

After sleep, first verify that the device itself is back online. A computer may take time to restore Wi-Fi, and a phone may have paused background work while its screen was off. If the VPN remains disconnected after the base connection returns, try reconnecting from the client. If this resolves the issue consistently, review the sleep, battery, and auto-connect options rather than repeatedly reinstalling the application.

When a device changes networks often and the client cannot reconnect reliably, a manual disconnect before a planned network change can make troubleshooting clearer. This is not a universal requirement; client behavior differs by operating system and configuration. Test the behavior on your own device and use the least complicated setting that maintains the connection you need.

Know when to reset or contact support

Consider resetting the client’s network configuration only after recording the settings and confirming that the profile or imported subscription is correct. A reset may remove custom rules, saved servers, or other preferences. If the issue began immediately after an update or configuration change, restoring the last known working settings can be more informative than removing the entire app.

Reinstalling is a later step, not the default fix. Before doing it, check that you can obtain the official installer again and know how to sign in or import your configuration. On mobile devices, removing the app may also remove its VPN profile. After reinstalling, test with the default configuration before restoring optional rules, so you can tell whether the clean setup has resolved the issue.

Contact the service or client support team if the problem persists across trusted networks, the standard configuration, and more than one compatible server or protocol. Include the exact time and frequency pattern, the operating system, client version, network type, and any error text. Explain whether the device had internet access with the VPN disconnected. This information helps support distinguish a local connectivity issue from a client or server-side problem without requiring you to share sensitive account details.

  • ✅ Keep a short record of changes and results so support can reproduce the pattern.
  • ✅ Remove or refresh only the affected profile when the configuration is clearly invalid.
  • ❌ Do not send passwords, private keys, or unredacted subscription links in a public post.

Frequently asked questions

Why does my VPN disconnect when my phone screen turns off?

Battery optimization or background-app restrictions may pause the client, but the underlying network can also change while the phone is idle. Allow the VPN app to run in the background, review battery settings, and test whether the disconnect still occurs on a stable network. Menu names and available controls differ by operating-system version.

Should I reinstall the VPN app?

Not as the first step. Check the network, permissions, automatic reconnection, client update, and imported configuration first. Reinstall only when simpler checks fail or support recommends it, and make sure you can restore your settings afterward.

Will changing the protocol stop disconnections?

It may help if the selected protocol is incompatible with the client or behaves poorly on a particular network, but it cannot fix weak Wi-Fi, device restrictions, or every server-side problem. Test a supported alternative while keeping other conditions unchanged.

Why does the VPN drop only on one network?

That network may have unstable connectivity, a sign-in requirement, or restrictions that affect the VPN connection. Compare with another trusted network and confirm that the first network has ordinary internet access. If the problem is isolated to a managed network, its administrator may need to clarify the applicable policy.