A VPN that connects successfully but drops a few minutes later can be frustrating, especially when the cause is not obvious. The most useful first checks are often simple: confirm the app is allowed to run in the background, look for recent Wi-Fi or mobile-network changes, and see whether the problem follows one server or one protocol. Avoid changing several settings at once; a controlled test makes it easier to identify what actually helps.

This guide walks through common causes on Windows, macOS, Android, iOS, and Linux, then gives you a practical order for testing them. A disconnect can come from the device, the local network, the VPN app, or the selected route, so begin with the symptom and narrow the possibilities before reinstalling software or changing advanced settings.

Identify the disconnect pattern

First, determine what “disconnecting” means in your case. Some clients show a clear disconnected state and attempt to reconnect. Others remain open while traffic stops passing through the tunnel. A website timing out by itself does not prove the VPN has disconnected; the destination, browser, or local connection may be responsible.

Note what happens immediately before the interruption. Does it occur when the screen locks, the device sleeps, you move between rooms, or the connection changes from Wi-Fi to mobile data? Does it happen only during a particular app, or on every device using the same network? These details point toward different causes and prevent unnecessary changes.

  • The client reports disconnected. Check background operation, network stability, server availability, and the client’s connection log.
  • The client says connected, but apps stop loading. Check whether traffic is still passing, whether DNS resolution works, and whether a specific app or destination is affected.
  • The drop happens after the device sleeps. Review power-saving and background-app permissions before changing servers.
  • The drop happens while moving or switching networks. Test on one network at a time and check whether the client handles network transitions cleanly.
  • Only one server or protocol fails. Compare another available server or supported protocol while keeping the device and network unchanged.

Keep a short record of the time, network type, selected server, protocol if shown, and the action you were taking. You do not need specialist monitoring software: a few consistent notes can reveal that interruptions happen only after sleep, only on mobile data, or only with one connection choice. If the client provides diagnostic logs, save the relevant section before restarting or reinstalling it.

Start with the pattern: A repeatable trigger is more useful than a guess about which VPN setting must be wrong.

Check power and background settings

Phones and laptops may restrict network activity when an app runs in the background or the device enters a power-saving state. A VPN connection can then be paused, its network interface can be suspended, or the app may be prevented from reconnecting promptly. The exact setting name differs by operating-system version and device manufacturer, so look for battery optimization, background activity, low-power mode, or app sleep controls.

Android background restrictions

On Android, open the system settings for the VPN app and check its battery or app-usage permissions. If the device offers unrestricted or unrestricted-in-background operation, consider allowing it for the VPN client when persistent background connectivity is needed. Also check manufacturer-specific battery managers: some add their own app sleeping, auto-start, or background network restrictions beyond standard Android settings.

Test with battery saver disabled temporarily, then lock the screen and wait through a normal period when the drop usually occurs. If the connection now stays up, re-enable battery saver and adjust only the VPN app’s background allowance. This helps distinguish a power-management issue from a server or protocol problem. Do not disable battery protections for every app as a first step.

iOS background and Low Power Mode

On iPhone or iPad, check whether Low Power Mode is enabled and whether the VPN app has current permissions and an up-to-date version. iOS controls much of the background networking behavior itself, so there may not be a universal “keep this app awake” switch. If drops occur when changing networks or waking the device, test the client after disabling Low Power Mode temporarily and note whether the pattern changes.

Do not assume that leaving the VPN app open on screen is a permanent fix. If a test indicates that the operating system is suspending the connection, use the client’s supported reconnect or on-demand options where available, and check the app’s own guidance for your device. If the behavior continues only after a system update, record the operating-system version and client version for troubleshooting.

Desktop sleep and network adapters

On Windows and macOS, a laptop waking from sleep may restore Wi-Fi before the VPN client has rebuilt its tunnel. If the drop consistently follows sleep, test a fresh connection after waking, and check the client’s reconnect setting. On Windows, power-management options for a wireless adapter may also affect connectivity; change them only if the symptom points to sleep or adapter suspension, and make a note of the original setting so you can restore it.

On Linux, desktop power management, NetworkManager behavior, and the way the chosen client handles interface changes can all matter. Check the client logs and system network state rather than assuming every interruption is caused by the VPN protocol. If the tunnel is managed by a system service, confirm that the service remains active and that its configuration matches the client or provider instructions.

Test your network and recent changes

A VPN relies on the underlying internet connection. If Wi-Fi briefly drops, a router restarts, mobile reception changes, or the device moves between access points, the tunnel may need to reconnect. Begin by checking whether the ordinary connection is stable without the VPN. Use the same device and network, and compare the timing of any interruptions rather than relying on a single successful page load.

Think about what changed shortly before the problem began. Recent changes may include a router or modem restart, a new Wi-Fi network, a password change, an operating-system or client update, a new security application, or a different VPN configuration. If the issue began immediately after one change, test that factor first. Avoid resetting the router or deleting every network profile before you have identified a likely cause.

  • Test one connection type. Stay on Wi-Fi for one test, then try mobile data or another trusted network separately if available. This helps establish whether the issue follows the network.
  • Check the ordinary connection. Disconnect the VPN briefly and see whether the underlying connection itself pauses. Reconnect the VPN after the test.
  • Reduce competing traffic. Pause large uploads, downloads, or other bandwidth-heavy activity while testing. Network congestion can make an otherwise working tunnel appear unreliable.
  • Restart in a useful order. If the local connection is unstable, restart the affected device or network equipment according to its normal instructions, then reconnect the VPN. Avoid repeated rapid restarts that obscure the result.
  • Review recent software changes. Check whether a firewall, endpoint-protection tool, ad blocker, or another proxy app began running around the time the drops started.

Network handoffs deserve particular attention on mobile devices. Moving between Wi-Fi access points, leaving Wi-Fi coverage, or switching between Wi-Fi and cellular data can interrupt existing connections even when ordinary browsing recovers quickly. If the VPN client offers automatic reconnection, confirm that it is enabled. Test a handoff deliberately, then allow the client time to reconnect before concluding that the tunnel is stuck.

If you want a starting point for the service and its supported client options, VPNHey Free VPN for China provides the site’s main entry point; use the instructions for your device and avoid importing a configuration into a client that does not support it.

Change one thing at a time. If you switch networks, server, protocol, and battery settings together, a successful test will not tell you which change solved the problem. Keep the device and test activity consistent whenever possible.

Follow a controlled reconnection test

Use this sequence after checking the obvious battery and network triggers. It moves from low-impact checks to more specific connection changes, while keeping each test easy to compare. If a step fixes the issue, stop there rather than continuing to alter settings that are already working.

  1. Confirm the client state. Open the VPN app and check whether it reports connected, reconnecting, or disconnected. If it shows a connection error, note the wording and save any relevant log details before restarting the app.
  2. Check the underlying network. Temporarily disconnect the VPN and confirm that the device’s normal connection works. If ordinary connectivity also drops, address Wi-Fi, mobile reception, or the router first.
  3. Reconnect on the same network. Close and reopen the client if needed, then connect without changing other settings. Observe whether the connection survives the usual trigger, such as screen lock or a normal app session.
  4. Try another available server. If the problem persists, select a different server that is available to your account and test again on the same network. A drop limited to one server may indicate a route-specific or server-side issue rather than a device-wide fault.
  5. Compare a supported protocol. If the client exposes protocol choices, test another option supported by both the client and the service. Record the original choice and restore it if the test does not help.
  6. Check for app conflicts. Ensure that another VPN, proxy, firewall, or filtering tool is not trying to manage the same traffic. Do not run multiple VPN clients at once; competing routes can produce unstable or confusing results.
  7. Review the result. Note what changed and whether the connection remained stable through the same activity. If the issue continues, collect the client version, operating-system version, network type, server choice, protocol if shown, and relevant logs for support.

Protocol names alone do not guarantee that two configurations behave the same way. WireGuard, Shadowsocks, VMess, Trojan, and Hysteria2 are different technologies, and a particular client may support only some of them or require a provider-specific configuration. Do not paste credentials or subscription details into an unrelated client, and do not edit advanced transport parameters unless the service’s instructions explicitly call for it.

A protocol comparison is most meaningful when the network, device, server region, and test activity remain unchanged. If one option works and another repeatedly fails under otherwise similar conditions, record that result rather than treating it as proof that the same protocol will behave identically on every network. Some networks handle connection methods differently, and client implementation also matters.

  • ✅ Keep a note of the original server and protocol before testing alternatives.
  • ✅ Test on the same device and network when comparing connection choices.
  • ✅ Check the client’s logs if it reports a specific error or repeated reconnect attempts.
  • ❌ Do not run two VPN clients simultaneously while troubleshooting.
  • ❌ Do not share passwords, subscription links, or private configuration details in public reports.

When to change the server, protocol, or client

Try a different server when the disconnect appears tied to one selection: for example, other server choices remain connected on the same device and network, while one repeatedly drops. Keep the comparison fair by changing only the server. If every server disconnects at the same moment, focus first on local network changes, background restrictions, or a client-wide issue.

Consider a different protocol only when the client offers the option and the service supports it. A protocol switch can be a useful diagnostic test, but it is not a universal repair. Some networks may block or disrupt certain connection methods, while another option may be more compatible with that environment. If the switch makes no clear difference, return to the previous setting and investigate the common factors.

Update the VPN client through its trusted official distribution channel if the installed version is outdated or the problem began after a known app change. Before reinstalling, check whether you can sign in again and retrieve your configuration; preserve any information you need without exposing credentials. Reinstalling should be a later step, not the first response to every short interruption.

DNS problems can look like a disconnect even when the tunnel remains active. If the client says connected but names fail to load, test whether the issue affects all apps or only one browser, and whether a direct IP connection behaves differently where appropriate. Do not change DNS settings randomly: VPN clients may set DNS as part of the tunnel, and manual overrides can create leaks or conflict with the intended configuration.

Use the smallest effective change: If only one server, network, or background condition reproduces the issue, fix or avoid that specific trigger before replacing the client or editing advanced settings.

Contact support when the problem continues across networks and server choices, or when the client logs show a persistent error you cannot interpret. Include the device and operating-system version, client version, approximate times of the drops, network type, server selection, and the tests already completed. Remove passwords, account tokens, and full subscription URLs from screenshots or logs before sharing them.

VPN disconnection FAQ

Why does my VPN disconnect when my phone screen locks?

Battery optimization, Low Power Mode, or a manufacturer-specific background manager may restrict the VPN app when it is not in the foreground. Check the app’s background and battery permissions, then test whether allowing background operation changes the behavior. Also confirm whether the interruption happens only after the device sleeps or whether it occurs during active use too.

Should I change the VPN protocol?

Only as a controlled test when your client and service support another option. Record the current setting, change one variable, and compare on the same device and network. Protocol availability and behavior depend on the configuration and client; choosing a different name is not guaranteed to fix every disconnect.

Why does the client say connected while websites fail?

The tunnel may be active while DNS resolution, a particular app, or the destination site is failing. Check whether multiple apps are affected and whether the client’s connection status or logs show an error. Avoid treating one unavailable website as proof that the whole VPN has dropped.

What information should I send to support?

Provide your device and operating-system version, VPN client version, network type, selected server, protocol if visible, the approximate time of a drop, and the troubleshooting steps you tried. Include relevant error text or a carefully reviewed log excerpt, but remove passwords, access tokens, and subscription links first.

Bottom line: Check background power settings and network changes first, then compare one server or supported protocol at a time. A clear test record makes both self-troubleshooting and support follow-up more effective.