A VPN that connects successfully but drops out every few minutes is difficult to diagnose because the visible symptom is the same while the cause may be completely different. An unstable Wi-Fi link, a sleeping phone, an overloaded route, an incompatible protocol, a damaged subscription entry, or another network tool competing for control can all produce repeated disconnections. Reinstalling the client or switching servers at random may occasionally help, but it rarely explains what went wrong.
The quickest approach is to change only one variable at a time. First determine whether the local network itself is stable. Then check the client’s mode, protocol, subscription status, and background restrictions. Finally, compare another route under the same conditions. This guide applies to official clients on Windows, macOS, Android, iOS, and Linux, as well as compatible tools such as Clash Verge, sing-box, and Shadowrocket.
90+
Countries covered
200+
Available routes
14 days
Refund window
Unlimited
Online devices
Identify the cause before changing everything
Start by recording exactly what “disconnecting” means on your device. Some clients show a clear disconnected status, while others remain marked as connected even though requests are timing out. A browser may stop loading while an existing download continues, or only one application may lose access. These details help distinguish between a local connection failure, a route problem, and an application-specific proxy issue.
Check whether ordinary websites open normally with the VPN disabled. If the Wi-Fi connection also drops without the VPN, focus on the router, signal quality, mobile network, captive portal, or local internet service first. If the local connection is stable but the VPN repeatedly loses its tunnel, continue with client and route diagnostics. Testing on another network, such as mobile data instead of home Wi-Fi, is especially useful because it changes the access network without changing the account or client.
| Observed symptom | Most likely area | First check |
|---|---|---|
| All internet access stops when the VPN drops | Local network, tunnel, or kill switch | Wi-Fi stability and client logs |
| Only one application stops working | Application proxy support or routing rules | System proxy, TUN mode, and split routing |
| The VPN disconnects after the screen turns off | Battery or background restrictions | App battery permissions and background data |
| The problem affects one route but not another | Route congestion or protocol compatibility | Compare routes using the same client settings |
| The client shows no usable routes after an update | Subscription or configuration issue | Subscription validity and format compatibility |
Check Wi-Fi, mobile data, and local network interruptions
A VPN tunnel cannot remain stable if the underlying connection frequently changes address, loses packets, or briefly disconnects. Wi-Fi roaming between access points, weak signal strength, crowded wireless channels, and router power-saving behavior can interrupt a tunnel even when a webpage eventually recovers. The same applies to mobile networks moving between different radio bands or coverage areas. A short interruption may be enough for a long-lived TCP or UDP session to expire.
Test another network without changing the client
Run a controlled comparison. Keep the same client, route, protocol, and connection mode, then test once on the current Wi-Fi and once on a trusted mobile hotspot or mobile data connection. Do not judge the result from a single page load. Open several normal pages, keep a streaming request or long session active, and observe whether the client reports a tunnel change. The purpose is not to produce a universal speed score; it is to see whether the failure follows the access network.
If the VPN works on mobile data but drops on home Wi-Fi, restart the router, move closer to the access point, test the other Wi-Fi band if available, and temporarily disable aggressive roaming or power-saving options. If several devices show the same interruption at the same time, the router or upstream network is more suspicious than the VPN client. If only one device is affected, inspect its network adapter, security software, and saved network profile.
Remove competing network controls
Running two proxy clients at once can create route loops, conflicting virtual adapters, or repeated changes to system proxy settings. Close other VPN applications, proxy managers, traffic filters, DNS interceptors, and network acceleration tools before testing. On Windows and macOS, also check whether endpoint security software, a corporate firewall, or a virtual machine has installed its own network filter. On Linux, inspect active services and virtual interfaces if a desktop client conflicts with a command-line core.
- ✅ Test with one VPN or proxy client active at a time
- ✅ Compare Wi-Fi and mobile data while keeping client settings unchanged
- ✅ Restart the router when several devices show the same interruption
- ❌ Do not conclude that a route is faulty after testing only one unstable Wi-Fi connection
- ❌ Do not enable multiple TUN adapters or virtual network interfaces without checking ownership
Review client mode, permissions, and battery restrictions
Many apparent disconnections are caused by the operating system stopping the client in the background. This is common on phones, but desktop systems can also suspend network adapters, restrict startup services, or block a virtual interface after sleep. If the VPN works while the app is open and fails after the screen locks or the computer wakes, background behavior should be your first suspect.
Keep mobile clients active in the background
On Android, open the system settings for the VPN client and review battery usage, background activity, unrestricted data access, and automatic startup permissions. The exact names vary by device manufacturer. Avoid placing the app in a deep-sleep list if you expect the VPN to remain connected while the screen is off. Also check whether the system is switching between Wi-Fi and mobile data and whether a “data saver” function restricts background traffic.
On iOS, confirm that the VPN profile is still installed and that the client has permission to establish the connection. Review Low Data Mode, Low Power Mode, and any on-demand VPN settings that may trigger a reconnect. If the VPN disconnects whenever the device changes networks, remove and re-add the profile only after recording the current configuration. Repeatedly importing profiles can leave old entries that make it unclear which configuration is active.
Check sleep, startup, and virtual adapter behavior
On Windows, verify that the client has the permissions required for its selected mode. A system proxy may cover browsers and applications that follow Windows settings, while TUN mode uses a virtual adapter to capture more traffic. TUN mode can be useful for command-line tools and applications that ignore the system proxy, but it may conflict with firewalls, virtualization software, or another network adapter. On macOS, review system network extensions and approve the client’s requested permissions when prompted.
Linux users should check whether NetworkManager, systemd services, a desktop client, and a separate sing-box or Clash process are trying to control the same route. A subscription can be valid while the local service fails to start, loses permission, or exits after a configuration reload. Examine the client status and logs rather than assuming that the remote route is unavailable.
Test protocols, route load, and compatibility systematically
Different protocols react differently to packet loss, network filtering, and changes in connectivity. Shadowsocks is commonly used as an encrypted proxy protocol; VMess and Trojan are other protocol families supported by compatible clients; Hysteria2 is designed around QUIC and UDP behavior; WireGuard uses a modern VPN tunnel with its own key and peer configuration. A client must support both the imported configuration format and the protocol used by the selected route. Importing a subscription successfully does not guarantee that every protocol entry can run in every client.
When a route disconnects, first try another route in the same region or route group while keeping the protocol and mode unchanged. If that works, the original route may be congested, temporarily maintained, or less compatible with your access network. If every route using one protocol fails but another protocol remains stable, inspect protocol support, firewall handling, and UDP availability. Do not compare a WireGuard configuration in an official VPN app with a Shadowsocks profile in a proxy client as if they were identical test conditions.
Follow a controlled repair sequence
- Stop other VPN, proxy, DNS, and traffic-filtering applications.
- Confirm that ordinary internet access remains stable with the VPN disabled.
- Restart the current client and update the subscription once.
- Choose a different route while keeping the same protocol and connection mode.
- Test a normal browser, an application that previously failed, and a longer session.
- If the issue continues, switch to a compatible protocol or client core.
- Record the route name, protocol, operating system, network type, and approximate failure event before contacting support.
Official clients are usually the simplest starting point because the download, account association, subscription handling, and protocol support are designed as one workflow. Clash Verge and sing-box are useful when you need detailed rule groups, TUN control, or advanced configuration, but they add more places for a mismatch to occur. Shadowrocket is convenient on supported Apple devices, yet its profile format, permissions, and routing behavior still need to match the imported subscription. Use the client’s documented import method instead of pasting a subscription into an unrelated protocol field.
| Test change | What it can reveal | What must stay unchanged |
|---|---|---|
| Different route, same protocol | Route-specific congestion or maintenance | Client, network, mode, and application |
| Different access network | Wi-Fi, mobile carrier, or local firewall effects | Route, protocol, and client |
| Different protocol | Compatibility, UDP handling, or filtering differences | Client, route region, and access network |
| Different client | Import format, permissions, or core implementation | Account, subscription, and comparable route |
Refresh the subscription and reset only the damaged configuration
A subscription link delivers managed configuration data; it is not the same thing as a single-node link or a web bookmark. If the client shows an empty route list, malformed entries, or routes that fail immediately after an update, confirm that the subscription was copied completely and that the client supports its output format. An expired plan, a revoked link, or an update failure can also leave old entries visible even though they are no longer usable.
Before deleting anything, note the active route, protocol, mode, and any custom rules. Then remove only the affected profile or subscription entry, add the subscription again through “Import from URL,” “Add remote configuration,” or the equivalent option, and perform a manual update. Avoid editing encoded subscription content by hand. A single missing character can invalidate the link, while manually changing server parameters may produce a configuration that no longer matches the provider’s settings.
If the client connects but traffic still stops, reset local DNS or restart the client’s virtual adapter according to the operating system’s normal procedures. Do not reset the entire operating system network stack as a first step, because that can remove unrelated adapters, saved networks, or custom routes. If the issue began immediately after a client update, compare the previous and current client versions only through trusted official distribution channels and keep a copy of the configuration before making changes.
For account-related troubleshooting, MeeVPN supports Windows, macOS, iOS, Android, and Linux. Plans include monthly options of ¥9.9/month with 60GB, ¥18/month with 250GB, and ¥28/month with 500GB; traffic resets monthly from the activation date. Non-expiring traffic packages are available at ¥158/300GB, ¥358/1000GB, and ¥658/3000GB. These allowances affect account usage, not whether a local Wi-Fi adapter or client can maintain a tunnel.
View tutorialsKnow when the problem needs support
Contact support after basic isolation, not only after trying every route. A useful report includes the platform, client name and version, connection type, selected route, protocol, whether the failure occurs after sleep or network changes, and whether another route works. Include a short description of the sequence that reproduces the problem. This is more actionable than saying only that the VPN is slow or disconnected.
Never send your password or expose a complete subscription link in a public ticket, screenshot, forum post, or shared document. If diagnostic logs contain a subscription address, redact the sensitive portion before sharing. You can usually provide the route label, protocol name, error message, and timestamp context without revealing account credentials. Support may ask you to test an official client, update the subscription, or compare a different route so that client-specific and account-wide problems can be separated.
- ✅ Save the exact error message instead of paraphrasing it
- ✅ State whether the issue affects one route, one device, or every device
- ✅ Mention whether Wi-Fi and mobile data produce different results
- ✅ Keep a backup of custom rules before reinstalling or resetting a client
- ❌ Do not publish passwords, subscription links, private keys, or full log files without redaction
VPN disconnection troubleshooting FAQ
Why does the VPN disconnect only when my phone screen is off?
Battery optimization, background data restrictions, or low-power settings may stop the VPN client or its network extension. Allow the client to run in the background, review unrestricted data access, and check whether the system’s on-demand VPN settings are being triggered during screen lock. If the problem remains, compare the same profile on mobile data and Wi-Fi.
Should I switch servers whenever the connection drops?
Try another route, but change only the route first. If the new route works with the same protocol and client, the original route may be temporarily congested or incompatible with the access network. If every route drops, switching servers repeatedly is unlikely to solve the underlying local, permission, or client problem.
Can a subscription link cause repeated disconnections?
A malformed, outdated, or incompatible subscription can create unusable route entries, but it does not normally explain every local network interruption. Update the subscription once, confirm that the client supports the returned format, and test a fresh route. Treat the link as sensitive account information and do not share it publicly.
What information should I send to support?
Provide the device platform, client, route label, protocol, connection type, failure pattern, and exact error text. Say whether another route or network works. Redact passwords, subscription URLs, private keys, and unrelated personal data from screenshots and logs before sending them.