Frequent VPN disconnects are frustrating, but they do not always mean the server is down. A connection can drop when your Wi-Fi signal changes, a phone suspends the client in the background, a router interrupts an idle session, or the selected protocol does not work well on the current network. A client may also reconnect automatically, making the problem look like a brief slowdown rather than a full interruption.
Start by identifying what actually stops: the VPN session, internet access on the device, or only one app. Then change one condition at a time. Switching servers, protocols, devices, and network settings all at once can temporarily hide the cause without showing you what fixed it. The checks below help narrow down the likely source and choose a practical next step.
Identify what is disconnecting
First note what you see when the interruption happens. Does the client change from Connected to Disconnected? Does the client stay connected while every app loses access? Does a browser page fail while other apps keep working? Does the connection recover by itself, or do you need to tap Connect again? These differences point to different parts of the network path.
A brief interruption during a move between Wi-Fi and mobile data is not the same as a session that repeatedly fails on one stable network. Likewise, a website timing out does not necessarily mean the VPN disconnected: the website, its DNS lookup, or a particular route may have failed while the tunnel remained active. Check the client status and try an unrelated site or app before changing settings.
- ✅ Record whether the client reports a disconnect or only the target app stops responding.
- ✅ Notice whether the issue follows one Wi-Fi network, mobile data, or every network you use.
- ✅ Check whether the drop happens after the device sleeps, changes networks, or sits idle.
- ❌ Do not assume that a failed website request proves the VPN session ended.
- ❌ Avoid changing several connection settings before you have a useful comparison.
If the client offers connection logs, look for events around the interruption, such as a network change, handshake timeout, route reset, or client restart. The wording varies between apps, and a single log entry may not establish the cause. Logs are most useful when you can compare the same type of failure across different networks or settings.
Check the local network and selected server
Begin with the simplest comparison: use the same device and client on another network. If the VPN is stable on mobile data but drops on one home Wi-Fi network, the home router or internet connection becomes a stronger suspect. If the drop follows you across networks, focus next on the client, device settings, account configuration, or the selected server.
Check whether ordinary internet access is stable without the VPN. If the Wi-Fi itself disconnects or pages fail even when the VPN is off, troubleshoot the router, signal quality, or internet provider first. On a crowded or weak wireless connection, packets may be delayed or lost. A tunnel can be more sensitive to interruptions than ordinary browsing because it depends on maintaining a usable path between the device and the remote endpoint.
Test a different server in the same general region, then compare with another available region if the service permits it. This helps separate a problem associated with one endpoint from an issue affecting the whole connection path. A different server may improve stability, but changing regions can also affect latency, available services, or the location presented to websites. Choose a server for the task at hand rather than assuming the geographically nearest option will always be best.
Routers and managed networks may handle long-lived or unfamiliar connections differently. Guest Wi-Fi, office networks, hotel access portals, and public hotspots can impose restrictions or interrupt traffic. Complete any network sign-in page before connecting. If only one network repeatedly causes drops, try its supported settings or ask the network administrator whether it limits VPN traffic. Do not attempt to bypass an organization’s security rules.
Run a controlled troubleshooting test
Use a short, repeatable test instead of making several changes in a hurry. Keep the device in the same place, use one network, and try a single server and protocol at a time. If you switch a setting, note what changed and whether the interruption pattern changed too. The goal is not to prove that one option is universally better; it is to find out which condition is associated with the failure on your setup.
- Confirm the baseline. Check ordinary internet access with the VPN disconnected. If the base connection is unreliable, resolve that first.
- Reconnect cleanly. Close any duplicate proxy or VPN clients, reconnect with one client, and confirm its status. Two apps trying to manage system proxy or tunnel settings can create confusing behavior.
- Hold the network constant. Avoid switching between Wi-Fi and mobile data during this comparison. If the problem normally occurs after sleep or a network handoff, test that event separately.
- Change the server only. Keep the protocol and client mode the same, then compare another suitable server. This isolates whether the issue may be endpoint-specific.
- Change the protocol only if available. Keep the same server or region where possible and test a protocol supported by both the provider and client. Do not copy protocol settings from an unrelated configuration.
- Review the result. Note whether the client disconnected, whether the device still had internet access, and what the log reported. Restore the previous setting if the change makes access worse.
Protocols can behave differently on different networks. Shadowsocks, VMess, and Trojan configurations may use different transports and parameters; Hysteria2 is designed around a different transport approach from conventional TCP-based connections. A network that handles one transport poorly may handle another more reliably, but the result depends on the client, server configuration, and network conditions. A protocol name alone does not guarantee that two configurations are interchangeable.
Do not edit authentication, TLS, transport, or server parameters unless the provider’s instructions explain the change. A mismatch can prevent a connection or make diagnosis harder. In compatible clients such as Clash Verge, sing-box, or Shadowrocket, confirm that the imported profile is current and that the selected node is actually the one being used. If you use the provider’s official client, first check for an available client update through its official source.
Check device power and client settings
Phones and laptops may limit background activity to save power. If drops happen after the screen turns off or the client moves to the background, review the operating system’s battery, background refresh, and network permission settings for that client. The exact controls differ by system version and device manufacturer. Use the least restrictive setting needed for a fair test, then restore your preferred battery settings if they do not affect stability.
Windows and macOS
On Windows or macOS, check whether sleep, a network adapter power setting, or a change from Ethernet to Wi-Fi lines up with the drop. Confirm that the client has permission to create or manage its virtual adapter if it uses a system-wide tunnel mode. If the client relies on a system proxy instead, verify that another application has not replaced or cleared the system proxy settings. Administrative prompts and permission names differ between clients, so follow the client’s documentation rather than changing unrelated system services.
Android and iOS
On Android, review battery optimization and background restrictions for the VPN app, along with any device-specific power-saving controls. Some manufacturers add their own app-sleep rules. On iOS, check the VPN status and the app’s available background or on-demand options; the system controls much of the background networking behavior, so not every setting is exposed to the user. If a drop occurs only when switching between Wi-Fi and cellular, compare the behavior on each network before changing background permissions.
Linux and third-party clients
On Linux, inspect whether the network manager, firewall, sleep behavior, or another VPN service is replacing routes when connectivity changes. If you use a third-party client, confirm that it supports the imported protocol and configuration fields. A profile can import successfully while some options are unsupported or interpreted differently. Keep one client responsible for the system route during testing, and review its logs for interface or route changes around the failure.
For any platform, check whether the client has an automatic reconnect option. Reconnection can reduce the time without a tunnel, but it does not explain why the drop happened. If the client repeatedly reconnects, note the frequency and the surrounding network events rather than treating automatic recovery as a complete fix.
Know when to change settings or contact support
Switch servers when the issue appears isolated to one endpoint or one route. Try another protocol when the current one repeatedly struggles on a particular network and the client and provider both support alternatives. Review power or background settings when drops closely follow sleep or app suspension. If the whole device loses internet at the same time, resolve the local connectivity problem before changing VPN configuration.
Ask the provider for help when the client disconnects across multiple networks and servers, when logs show repeated handshake or authentication failures, or when a recently imported configuration no longer works as expected. Include the operating system, client name and version, protocol, whether the failure occurs on Wi-Fi or mobile data, and the approximate time and pattern of the drop. Share only the relevant log excerpt through the provider’s support channel.
Before sending logs or screenshots, remove subscription links, usernames, authentication tokens, private server details, and other identifiers. A subscription URL can contain credentials; treat it like a password. Never post it publicly or send it to an unofficial account that claims to offer troubleshooting.
If you need to confirm how to install or import a supported client, use the setup guide. Follow the instructions for your platform and client rather than importing the same configuration into several apps at once.
Frequently asked questions
Why does my VPN disconnect when my phone screen turns off?
Battery optimization, background restrictions, or the operating system’s network management may suspend or limit the client. Review the app’s background and battery settings, then test whether the drop still occurs. If the client remains connected but apps lose access, also check the device’s network transition behavior.
Why does the VPN drop only on Wi-Fi?
The Wi-Fi signal, router, internet connection, or network policy may be interrupting the session. Compare another Wi-Fi network with mobile data, and check whether ordinary internet access also fails. If the issue is limited to one router, restarting or updating that router may help, but first make sure the underlying connection is stable.
Should I switch protocols whenever a connection drops?
No. First establish whether the drop is tied to one network, server, device state, or client. A protocol change is a useful controlled test when the current transport may not work well on that network and an alternative is supported. Changing protocols without recording the result can make the cause harder to identify.
What information should I send to support?
Describe the platform, client, protocol, network type, server selection, and what happens at the time of the drop. Include a relevant redacted log excerpt if requested. Do not share a subscription URL, password, authentication token, or complete configuration file unless the provider gives you a secure and appropriate way to do so.