A VPN that keeps disconnecting is frustrating, but reinstalling the app is rarely the best first move. The cause may be an unstable Wi-Fi or mobile connection, an operating-system setting that suspends the app, a stale tunnel after switching networks, or a problem with one particular server or protocol. Work through these possibilities in order: first establish whether the internet connection itself is stable, then check the device and app, and only then change the route or protocol.
Make one change at a time and test the same task after each change. If you switch servers, change protocol, and adjust battery settings all at once, you may restore the connection without learning what caused the drop. A careful sequence makes it easier to keep a useful setting and undo changes that do not help.
Identify where the connection is failing
A VPN connection depends on more than the VPN app. Your device must have working internet access, the app must be allowed to run and maintain its tunnel, and the selected server must be reachable from the current network. A failure at any one of these layers can look like the same symptom: the VPN disconnects, reconnects, or reports that it cannot reach the server.
3 layers
Network, device, and route
5 platforms
Windows, macOS, iOS, Android, Linux
1 change
Test at a time
When the VPN drops, check whether ordinary internet access still works. Disconnect the VPN temporarily and load a site or open an app you normally use. If that also fails, the immediate problem is likely the Wi-Fi, mobile data, router, or internet provider rather than the VPN tunnel. If the internet works without the VPN but not with it, focus on the VPN app, server, protocol, or network rules that affect VPN traffic.
Notice the timing as well. Drops that happen only when the screen turns off point toward background or battery restrictions. Drops after moving between Wi-Fi and mobile data suggest a handoff or tunnel-recovery issue. A connection that fails only on one Wi-Fi network may be blocked or disrupted by that network. A drop that occurs on several networks but only with one server is a reason to test another route.
A VPN status indicator can be useful, but it does not always tell you whether all apps have recovered. After a reconnect, open the affected app or page again. Some applications keep a failed request or old connection alive until you refresh, restart the app, or sign in again.
Rule out network and router problems
Start with the least disruptive network checks. Confirm that Wi-Fi or mobile data is enabled and that the device has not joined a network with a sign-in page. Public Wi-Fi at hotels, airports, campuses, and workplaces may require you to accept terms or authenticate in a browser before general internet access is available. Complete that step with the VPN disconnected, then reconnect.
Compare the connection on another network if one is available. For example, try mobile data instead of home Wi-Fi, or another trusted Wi-Fi network instead of the one that is dropping. If the VPN stays connected elsewhere, the original network may be interrupting the tunnel, losing connectivity, or applying rules that restrict VPN traffic. If it disconnects on different networks, investigate device settings, app configuration, and server choice next.
Restarting the router can help when the underlying Wi-Fi or internet connection is unreliable, but it is not a universal VPN fix. First check whether other devices also lose internet access. If they do, address the router or provider connection. If only one device and one VPN app are affected, restarting the router may add downtime without addressing the cause.
When moving between networks, give the device a moment to establish ordinary internet access before asking the VPN to reconnect. A tunnel created over a disappearing Wi-Fi connection may not automatically transfer to mobile data. If the app remains stuck, disconnect it from within the app, wait until the new network is usable, and connect again. Avoid repeatedly toggling airplane mode or changing several network settings in quick succession; those actions can make it harder to see which connection state is actually failing.
- ✅ Test ordinary internet access with the VPN disconnected.
- ✅ Complete any Wi-Fi sign-in or captive portal step before reconnecting.
- ✅ Compare a trusted second network to see whether the issue follows the device or the network.
- ❌ Do not assume a VPN fault when other apps also cannot reach the internet.
Check device settings and reconnect options
Operating systems may restrict background activity to save power, or change network state while a device sleeps. The exact menu names vary by operating-system version and device manufacturer, so look for settings related to battery use, background activity, VPN, and network access rather than relying on a single menu path.
Windows and macOS
On Windows, check that the VPN app is allowed through the active firewall profile and that no second VPN or proxy utility is competing for the same system network settings. A security suite, endpoint-management tool, or manually configured proxy can affect connection attempts. If the problem began after sleep, wake the computer, confirm that Wi-Fi or Ethernet has recovered, and reconnect from the VPN app. If the app offers an automatic reconnect or connection-protection option, review its behavior and test it with the current network.
On macOS, check whether the VPN profile or app still appears enabled and whether a system prompt is waiting for approval. After waking from sleep or changing networks, disconnect and reconnect if the tunnel does not recover on its own. If you use more than one VPN client, turn off the other client before testing. Avoid deleting system profiles or changing advanced network services unless you know how to restore them; start with the app’s own disconnect and reconnect controls.
Android and iPhone
On Android, inspect battery optimization or background-use restrictions for the VPN app. Some devices offer manufacturer-specific power controls in addition to Android’s standard settings. Allowing appropriate background activity can help the app maintain a connection while the screen is off, but it may increase battery use. Also check Android’s VPN settings for an always-on VPN or a setting that blocks connections without the VPN. Those options can be useful when intentionally configured, but a mismatch between system settings and the app can make recovery appear to fail.
On iPhone, check whether the VPN app is permitted to refresh or reconnect as expected, and whether a configuration or permission prompt needs attention. iOS manages background activity and network transitions differently from desktop operating systems; do not expect every app to behave exactly as it does on a computer. If the tunnel drops after switching between Wi-Fi and cellular, open the VPN app after the new connection is established and reconnect. If the app provides an on-demand or automatic connection option, test it separately from manual connection.
On any device, the app’s own reconnect setting and the operating system’s VPN behavior are not always the same thing. A reconnect option may retry the selected server after a failure, while an always-on or connection-protection setting may prevent traffic from leaving the device without an active tunnel. Read the option’s description before enabling it, especially if you rely on local network devices or need internet access during troubleshooting.
Also update the VPN app and operating system through their normal update channels if an update is available. Updates can fix compatibility problems, but changing versions during diagnosis makes comparisons less clear. If the problem started immediately after an update, note that fact and check the provider’s support information before removing the configuration.
Run a controlled reconnect test
Use this sequence after confirming that the device has ordinary internet access. It avoids jumping straight to a reinstall and makes each test easier to interpret. If the VPN is managed by an organization, follow its support instructions before changing profiles, security settings, or connection policies.
- Record the current setup. Note the network, server or region, protocol if shown, and whether the drop happens during sleep, network switching, or ordinary use. If the app shows an error message, copy its wording rather than relying on memory.
- Reconnect on the same network. Disconnect from inside the VPN app, wait for the status to change, and connect again without changing server or protocol. Check whether the same activity works. This tests whether a clean session resolves a temporary tunnel state.
- Test ordinary internet access. If the VPN drops again, disconnect it and check whether the device can load ordinary services. If those fail too, restore the network first. If they work, continue with the VPN-specific checks.
- Change only the server or route. Select another available server in the same general region, if one is offered, and repeat the same activity. If the new server remains stable, the original route may have a temporary issue or may not suit the current network. Do not infer a permanent quality difference from a single test.
- Change protocol only if needed. If the app exposes protocol choices, try another supported option and repeat the test while keeping the network and server unchanged. Some networks handle VPN transports differently, so a protocol change can help; it can also affect compatibility or performance. Return to the original option if the alternative makes the connection less reliable.
- Test a second network. If possible, repeat the test on a trusted alternative network. Compare the result with the first network. This helps determine whether the failure follows a particular access network or remains with the device and app.
- Restore settings that did not help. Keep a brief note of each change. Turn off test-only settings you do not want, and avoid leaving multiple experimental configurations active.
Do not treat a momentary reconnect as proof that the issue is fixed. Use the device in the way that usually triggers the problem: lock the phone if drops happen while idle, move between Wi-Fi and cellular if the issue follows a handoff, or repeat the same work task if it fails during a particular activity. The purpose is to see whether the original symptom returns under comparable conditions.
If you use a subscription link in a compatible third-party client rather than a provider’s own app, the same diagnostic order applies, but the controls may have different names. Check the client’s connection log, selected outbound, and automatic-reconnect behavior. Confirm that the subscription has been imported or updated successfully, and avoid importing duplicate profiles that may have conflicting names or settings. Do not share a subscription URL publicly: treat it like an account credential.
When to change a server or protocol
Try another server when the connection fails only with the current selection, the app repeatedly cannot establish a session to that endpoint, or the service lists more than one route suitable for your needs. A different server may use a different path, but changing location is not guaranteed to solve a network problem. Select a permitted region that fits your use, and keep it consistent while you test rather than switching repeatedly after every brief interruption.
Protocol names describe how the VPN tunnel is established; they do not by themselves guarantee stability. A network may allow one transport more readily than another, while a restrictive firewall may interfere with several. If your client offers choices such as WireGuard, OpenVPN, or a provider-specific protocol, use only options the service supports and follow its documentation. Do not copy protocol settings from an unrelated client or assume that two apps use the same configuration simply because their menus contain similar labels.
Likewise, route labels such as direct, relay, or IEPL describe aspects of the network path, not a promise that a session cannot drop. Your local connection to an entry point, the route between network segments, the exit, and the destination can each affect continuity. Compare routes using the same device, network, and task so the result is meaningful. If a different route is stable, you can use it while reporting the original route and conditions to support.
| Symptom | First check | Next useful test |
|---|---|---|
| Other apps also lose internet | Wi-Fi, cellular data, router, or sign-in page | Restore ordinary internet access before testing the VPN again |
| Drops after the screen locks | Battery or background restrictions | Allow appropriate background activity, then repeat the same idle test |
| Drops while changing networks | Network handoff and tunnel recovery | Wait for the new network, then reconnect from the app |
| Only one server repeatedly fails | Selected endpoint or route | Try another supported server while keeping other settings unchanged |
| Several networks and servers fail | App state, permissions, protocol, or service status | Check logs and contact support before deleting configurations |
Before concluding that a server is overloaded, check whether the provider reports maintenance or a service interruption. A slow or unstable connection can have several causes, and a user-side symptom alone does not establish server load. If a service status page or support channel is available, include the approximate time and selected route when asking for help.
Frequently asked questions
Should I reinstall the VPN app?
Not as the first step. Check internet access, network changes, background restrictions, reconnect settings, and another supported server first. Reinstalling may remove useful logs or configuration and does not fix a problem caused by the router or network. Consider it only after simpler checks fail, and confirm that you can sign in again and restore the required settings before removing the app.
Why does the VPN disconnect when my phone locks?
Battery management or background restrictions may suspend the VPN app, but network changes or system power behavior can also be involved. Review the app’s background and battery permissions, then repeat the same test with the screen locked. Make one setting change at a time and consider the battery trade-off before allowing unrestricted background activity.
Should I use auto-reconnect or always-on VPN?
Use these options only after understanding what each one controls. Auto-reconnect generally attempts to restore a failed VPN session; an operating-system always-on setting may apply more broadly and can affect whether apps have internet when the tunnel is unavailable. Check the app and operating-system descriptions, and test the behavior on your own device. If you need access to local devices or must troubleshoot a network, make sure you know how to disconnect the VPN safely.
What information should I send to support?
Share your operating system and version, VPN app or compatible client, network type, selected server, protocol if visible, the time and pattern of the drop, and the steps you already tested. Include the exact error text or a redacted log if support requests one. Remove account credentials, passwords, private keys, and subscription links before sharing screenshots or diagnostic files.
In most cases, the quickest path is to separate a general internet failure from a VPN-only failure, check the device’s ability to keep the app active, and then compare one server or protocol at a time. That process is more informative than repeatedly reinstalling the client and leaves you with a clear record if the issue needs provider support.