A VPN disconnecting after sleep or a Wi-Fi change does not always indicate a faulty server. The device may have paused the VPN app, changed network interfaces, or taken longer to restore its tunnel than the app allows. Start by identifying the pattern: does the drop happen only after waking the device, only when Wi-Fi changes, or even while the connection is otherwise undisturbed? That distinction helps you test the right cause instead of repeatedly switching servers.

Identify when the connection drops

Before changing settings, note what the device was doing immediately before the interruption. A VPN that disconnects when a laptop lid closes points toward sleep and background-app behavior. A phone that drops the tunnel while moving between access points may be reacting to Wi-Fi roaming or a switch to mobile data. If the connection fails while the device stays awake on one network, investigate the local Wi-Fi, client, and route as well.

Check the VPN app’s status when the problem occurs. Some clients show that the tunnel is disconnected; others may still display a connected state while traffic is unable to pass. Open a familiar website or service after reconnecting, and check whether the connection recovers without restarting the whole device. If only one app fails while other traffic works, the issue may be specific to that app or its network permissions rather than a complete VPN drop.

Keep a short record of the time, network type, device power state, selected server, protocol, and any error message. Note whether the VPN reconnects automatically and whether ordinary internet access works while the tunnel is down. These observations are more useful than a series of unrecorded server changes: if several variables change at once, it becomes difficult to tell which one mattered.

Check sleep, Wi-Fi, and power settings

Sleep can suspend network activity or restrict background processes. When the device wakes, Wi-Fi may reconnect before the VPN app has had time to rebuild its tunnel. On phones, battery optimization can also limit an app that is expected to keep working in the background. The precise menu names vary by operating-system version and device manufacturer, so look for the relevant power, background, and network options rather than relying on a single menu path.

Windows and macOS

On Windows, first confirm that the VPN client is allowed to start with the system if you expect it to reconnect after sign-in or wake. Check the client’s reconnect or auto-connect option, then inspect Windows power settings for behavior that suspends the network adapter during sleep. If Wi-Fi itself takes time to return, test the connection after the network icon shows that the device is online; starting the VPN before the adapter is ready can create a misleading failure.

On macOS, check whether the VPN app is permitted to run in the background and whether its own reconnect setting is enabled. After waking the Mac, give Wi-Fi time to associate with the access point before judging the tunnel. If the Mac changes between Wi-Fi and Ethernet, or joins a different wireless network, the old route may no longer be usable. Disconnect and reconnect from the client once the new connection is stable. Avoid repeatedly removing system network profiles unless the client’s documentation instructs you to do so.

Android and iPhone

On Android, review the VPN app’s battery usage and background activity permissions. Some manufacturers add aggressive battery controls that can stop an app even when Android’s general settings appear permissive. If the device has an always-on VPN option, confirm that it is configured for the VPN app you actually use. A lockdown option may block traffic whenever the tunnel is absent; do not disable it casually if preventing unprotected traffic is important to you.

On iPhone, check the VPN app’s reconnect behavior and allow the app to complete any required system prompts. iOS manages background work differently from a desktop system, so an app may need to reconnect after a network transition rather than maintain an uninterrupted tunnel throughout it. If Wi-Fi Assist or a cellular-data transition is involved, observe whether the VPN recovers on the new network. When testing, change one setting at a time and restore any security control you intentionally switched off.

  • ✅ Test after the device has fully rejoined Wi-Fi, not while the network icon is still changing.
  • ✅ Allow the VPN client to run in the background if you expect automatic recovery after sleep.
  • ✅ Check whether a kill switch is blocking traffic while the tunnel is reconnecting.
  • ❌ Don’t assume that a connected Wi-Fi icon means the VPN tunnel has already been restored.
  • ❌ Don’t turn off every battery or security restriction at once; change one relevant setting and retest.

For people comparing a client setup with other ways of keeping a connection available, the VPN for China overview can help clarify the service context; it does not replace checking the operating system’s sleep and network behavior on the device that is disconnecting.

Run a controlled reconnect test

Use the following sequence to narrow the cause. Keep the device in one location and avoid changing the server, protocol, and power settings together. If the VPN becomes stable after one change, repeat the same test once under similar conditions before treating that change as the explanation. A single successful reconnect is useful evidence, but it does not prove that every earlier interruption had the same cause.

  1. Record the starting state. Note the device, operating system, VPN client, network type, selected server, and protocol if the client displays it. Write down whether the device was asleep, moving between Wi-Fi networks, or switching to cellular data.
  2. Check the local connection without the VPN. Disconnect the VPN briefly and confirm that ordinary internet access works. If Wi-Fi itself drops, pages fail to load, or the device cannot reach the router, troubleshoot the local network before judging the VPN route.
  3. Reconnect on the same network. Open the VPN client, connect to the same server, and confirm that a normal site or app works through the tunnel. This establishes whether the current configuration can connect while the device is awake.
  4. Test the triggering event. Let the device sleep or move to the network where the disconnection usually happens. Once it wakes or joins the new network, wait until ordinary internet access is available, then check whether the VPN reconnects automatically.
  5. Change one variable if it fails. First test the client’s reconnect option or the relevant background permission. If the failure remains, compare another suitable server. Only then consider a different protocol offered by the client.
  6. Restore and verify security settings. Re-enable any kill switch or network protection you temporarily changed. Confirm that the expected behavior is now clear: either the VPN reconnects, or traffic remains blocked until you reconnect manually.

When you compare results, use the same app and the same trigger each time. For example, compare waking from sleep on one Wi-Fi network with waking from sleep on another, rather than comparing one sleep test with a cellular handoff. If you are using a compatible third-party client, verify that its imported subscription is current and that the selected configuration is intended for that client. A client may display a profile as connected even when the underlying route has stopped responding, so confirm with ordinary traffic rather than relying on the status label alone.

Compare servers and protocol options carefully

If the local network remains usable and the same server repeatedly fails after a network transition, try another appropriate server from the client’s available list. This can help distinguish a route-specific interruption from a device-wide problem. Change only the server first and repeat the same sleep or Wi-Fi test. If every server fails in the same way, switching locations over and over is unlikely to address a power-management or Wi-Fi roaming issue.

A protocol change is another diagnostic step, not a guaranteed fix. VPN protocols and proxy protocols are not interchangeable labels: WireGuard is a VPN protocol, while Shadowsocks, VMess, and Trojan are commonly used by proxy clients. Hysteria2 is designed around UDP transport. Client and service support determines which options are available, and a protocol that works in one client may not be available in another. Use only options provided by your service or client, and avoid copying settings from unrelated guides.

Change to test What it may reveal How to interpret the result
Reconnect on the same server Whether the tunnel can recover after the local network returns If manual reconnection works, focus on automatic recovery, background permissions, or timing after wake.
Try another available server Whether the interruption appears limited to one route If only one route fails, provide that route’s details to support; if all fail alike, check the device and network.
Try another supported protocol Whether the behavior changes with the client’s transport option A difference may point to network compatibility, but it does not by itself identify the exact cause.
Test another Wi-Fi network Whether the issue follows one router or access point If the VPN is stable elsewhere, review the original network’s roaming, firewall, or router settings.

Some networks restrict or disrupt particular traffic types, so an alternative supported protocol may behave differently. That result is only a clue: it does not prove that the original protocol is broken or that the alternate choice is universally better. Keep a record of the exact client and option used, then return to a known working configuration if the test makes the connection less reliable.

Practical conclusion: Fix sleep and Wi-Fi recovery first; use server or protocol changes to isolate a route or network compatibility problem, not as a substitute for checking the device.

Know when to contact support

Ask for help if the VPN continues to disconnect after the device is awake, the local internet connection is stable, and you have tested the client’s reconnect behavior. Include the operating system and version, client name and version, whether you use an official app or a compatible third-party client, and the server and protocol involved. Describe the trigger precisely: waking from sleep, joining a different Wi-Fi network, switching to cellular, or disconnecting without an obvious change.

Also provide the exact error text and the approximate time of a recent failure. Explain what you tested and what happened, including whether another server or network changed the result. If the client provides diagnostic logs, follow its instructions for exporting them and remove account credentials, subscription URLs, tokens, and other private information before sharing. Do not post a subscription link publicly; it can function like a credential and may allow others to use your configuration.

A useful support report states the sequence rather than only saying “the VPN is unstable.” For example: the device was connected to Wi-Fi, entered sleep, woke with ordinary internet access, and the client did or did not reconnect. If the problem follows a particular router, say so. If it follows one device across different networks, mention that too. Clear observations help support distinguish a client recovery issue from a local access-point problem or a route-specific failure.

Frequently asked questions

Why does my VPN disconnect when my device sleeps?

Sleep can pause the network adapter or restrict background activity, so the VPN tunnel may not survive the transition. After waking, the device may restore Wi-Fi before the client reconnects. Check the client’s reconnect behavior and the operating system’s background or power settings, then test whether ordinary internet access returns before the tunnel.

Should I leave the kill switch enabled?

If you use a kill switch to prevent traffic from leaving outside the VPN, keep it enabled unless you have a specific reason to change it. It may block internet access during a drop by design. If you temporarily turn it off for diagnosis, use the test only to understand the symptom, then restore the protection and verify its behavior.

Will changing VPN servers stop the drops?

It may help if the issue is limited to a particular route, but it will not usually fix a client that is being paused during sleep or a Wi-Fi adapter that disconnects. Test another available server while keeping the device, network, and trigger the same. If all routes fail in the same way, focus on the client and local network.

What information should I send to support?

Provide the device and operating-system version, client and version, connection type, selected server, protocol if known, the exact error, and the event that preceded the drop. Include the steps you already tried and whether they changed the result. Share logs only through the approved support channel, and never include a public copy of your subscription URL or account credentials.