VPN Keeps Disconnecting? 7 Fixes for a Stable Connection

A VPN that connects successfully but drops a few minutes later can be frustrating, especially when the cause is not obvious. The problem may be a changing network, an operating-system power setting, an expired or outdated configuration, or a route or protocol that does not work well on the current connection. Reinstalling the app is rarely the best first step. Work through the checks below in order, changing one thing at a time so you can tell whether the connection becomes more reliable.

Identify when the VPN drops

Before changing settings, note what happens immediately before the disconnection. Does it happen when the screen locks, when you move between rooms, when Wi-Fi changes to mobile data, or only while using one particular app? Does the client show “disconnected,” “reconnecting,” or still “connected” while websites stop loading? These details help separate a tunnel interruption from a DNS, routing, or app-specific problem.

Test the same basic activity both with the VPN off and with it on. If your ordinary connection also cuts out, start with the network. If only the VPN fails, focus on the client, its configuration, and the route. If the client remains connected but one website or app fails, the tunnel may still be active; the destination service, DNS, or routing rules could be the issue. Avoid concluding that the whole VPN has failed based on one page that was already open. Make a fresh request and check the client’s current status.

Use a short record rather than relying on memory: device and operating-system version, client name and version, selected route, connection type, and what you were doing when the failure occurred. Do not include your password, full subscription link, or private configuration details if you share that record with support.

Seven fixes to try

1. Check the underlying network

A VPN cannot maintain a tunnel through a connection that is itself dropping packets or losing internet access. First disconnect the VPN and see whether ordinary browsing remains stable. If it does not, reconnect to Wi-Fi, move closer to the access point, or test a different trusted network. On mobile data, check whether the signal is fluctuating or the device is switching between network types. Captive portals at hotels, airports, and other public locations may also require you to complete a sign-in page before the VPN can connect reliably.

If the issue appears during a Wi-Fi-to-mobile-data handover, test each network separately. A client may need a moment to establish a new tunnel after the device changes interfaces. Confirm whether the client has an option for reconnecting when the network changes, and enable it if it fits your needs. Do not assume that a brief interruption during a handover means the route itself is defective.

2. Restart the client and device

Disconnect from the VPN using the client’s own control, close and reopen the app, and connect again. If the client still reports an inconsistent state, restart the device before changing advanced network settings. This can clear a stalled VPN service or a stale network interface without removing your subscription or saved configurations.

On a computer, also check whether another VPN client or proxy tool is running. Two apps that both try to control system routing or create a VPN interface can conflict. Quit the other tool completely, then test one client at a time. Avoid deleting configuration files or resetting all network preferences as an early troubleshooting step; those actions may remove settings unrelated to the VPN.

3. Review battery and background settings

If the VPN disconnects after the screen locks or after the app has been in the background, inspect the operating system’s power-management settings for that client. Android manufacturers may provide controls for battery optimization, background activity, autostart, or app sleep. On iPhone, iPad, and desktop systems, check whether low-power modes, app restrictions, or system policies are affecting background network activity. Menu names and available controls differ by operating-system version and device maker.

Change only the settings relevant to keeping the client active, and do so only if a persistent connection is part of your use case. Removing every battery restriction can increase power use and is not necessary for occasional VPN sessions. After adjusting a setting, lock the screen, wait long enough for the usual symptom to occur, then reopen an app and make a fresh request. A connection icon alone does not prove that data is passing through the tunnel.

4. Refresh the subscription or configuration

An outdated configuration can leave the client attempting to use a route that is no longer available or whose details have changed. If you use a subscription, open the client’s subscription or profile area and use its update function. If the service provides a new subscription link or updated setup instructions in its panel, use those rather than copying a link from an old message or an unofficial source.

Do not paste a subscription URL into a general browser or share it publicly. Treat it as private access information. After updating, check that the route list has refreshed and select a route again. If you imported an individual configuration rather than a subscription, compare its fields with the current information from the provider. Do not edit protocol, authentication, or server fields by guesswork: a small mismatch can prevent the tunnel from reconnecting.

5. Test another route

A single route may be temporarily unreachable from your network, or it may not be the best match for the service you are trying to use. Select a different available route in the same general region and repeat the same test. Keep the client, device, and test activity unchanged so the result is meaningful. If one route repeatedly drops while another remains connected under the same conditions, that is useful evidence to give the service provider.

Choose a location based on the destination service and your actual results, rather than assuming that the nearest location is always the most reliable. Route availability and performance can vary with the access network, destination, and current conditions. A route list may include different route types, but labels alone do not guarantee that a particular route will work best on every device or network.

6. Try a different supported protocol

If the client and subscription offer more than one protocol, try another supported option when the current one repeatedly fails. Network operators and firewalls do not handle every transport in the same way, so a protocol that connects on home Wi-Fi may behave differently on a restricted public network. Options may include Shadowsocks, VMess, Trojan, Hysteria2, or WireGuard, depending on the service, client, and configuration. These are not interchangeable labels: a client must support the selected protocol, and the subscription must provide a compatible configuration.

Change the protocol only through the client’s supported settings or by selecting a configuration supplied for that protocol. Do not manually convert one protocol’s link into another, and do not assume that every client supports every format. If the change makes no difference, switch back before testing another variable. That keeps the original working configuration available and makes it easier to identify which change affected the result.

7. Check system VPN and proxy settings

Look for an always-on VPN setting, a “block connections without VPN” option, a second VPN profile, or a system proxy that may be controlling traffic. These features can be useful when configured intentionally, but a stale profile or conflicting proxy can prevent the client from reconnecting normally. Check for settings that you or an administrator deliberately enabled before changing them; work or school devices may be managed by policies you should not override.

On Windows and macOS, also check whether another networking utility, security product, or proxy setting is intercepting traffic. On mobile devices, review the system’s VPN list and remove only profiles that you recognize as obsolete and no longer need. If you are unsure which profile belongs to an app or organization, ask its administrator or the app’s support team before deleting it.

A controlled troubleshooting sequence

Use this sequence after the initial checks. It is designed to narrow down the cause without changing several unrelated settings at once.

1. Record the symptom. Note whether the client says it disconnected, is reconnecting, or remains connected while traffic fails. Record the network type and what you were doing just before the issue.
2. Check ordinary internet access. Disconnect the VPN and test a fresh page or app request. If that also fails, address the underlying Wi-Fi or mobile-data connection first.
3. Test the client in the foreground. Reopen it, connect using the current configuration, and try the same activity that normally triggers the problem.
4. Test one route change. Select a different available route while keeping the device, network, and activity the same. Note whether the symptom changes.
5. Test one protocol change, if supported. Use a configuration that the client and subscription explicitly support. Restore the previous selection if the result is unchanged.
6. Test the background case. If the failure usually happens while idle or screen-locked, review only the relevant background or battery setting, then repeat the test.
7. Update the configuration last. Refresh the subscription using the client’s update function or follow the current instructions in your service panel. Reconnect and check the result again.

Allow enough time for the usual failure pattern to appear, but avoid repeatedly changing settings during a single test. If the issue happens only on one network, report that distinction. If every route and supported protocol fails on one device but works on another device using the same network, the first device’s client or system settings deserve closer attention. Conversely, if the same route fails across devices only on one access network, the network path may be involved.

• ✅ Test ordinary internet access before blaming the VPN.
• ✅ Change one setting at a time and keep a note of the result.
• ✅ Use only routes and protocol configurations supported by the client.
• ❌ Do not publish a subscription link, password, or private configuration.
• ❌ Do not run multiple VPN clients simultaneously during diagnosis.

When to contact support

Contact the provider or client support team if the disconnect continues after you have checked the network, restarted the client, refreshed the configuration, and tested another supported route or protocol. Include the device and operating-system version, client name and version, approximate time of the failure, network type, selected route, and the exact status or error message. Say which checks you have already completed and whether the problem occurs in the foreground, in the background, or during a network change.

Share only diagnostic information that is needed to investigate the issue. Redact account identifiers and private details from screenshots, and never send your password or a complete subscription link in a public post. If the client has a built-in diagnostic export, review what it contains and follow the provider’s instructions for sending it through an appropriate private channel. For client installation or configuration guidance, see the setup guides; for available locations, see the server page.

Frequently asked questions