VPN Won't Connect? A Complete Troubleshooting Checklist
You tap Connect, the app spins for ten seconds, and then quietly drops back to “Disconnected.” Nothing in the interface explains why, and restarting the app three times hasn’t helped. A VPN client that won’t connect is almost never one single problem — it’s usually one of five or six common culprits stacked together, and most of them take under a minute to rule out.
Run this 60-second checklist first
Before touching any settings, work through the basics. They resolve the majority of connection failures on their own.
- Confirm the base connection works. Turn the VPN off and try loading any website. If regular browsing is also broken, the VPN app isn’t the problem — your Wi-Fi or mobile data is.
- Check the app is up to date. Outdated builds are a frequent cause of failed handshakes, since providers regularly patch protocol and connectivity bugs.
- Switch networks. Move from Wi-Fi to mobile data (or the reverse). If the connection succeeds on one network and fails on another, the problem is local to that network, not your account.
- Restart the app, then the device. A stuck background process is a common, boring, and very fixable cause of a stalled connection.
- Check the time and date on your device. A clock that’s drifted can break the encrypted handshake before it even starts.
Tip: If the app connects instantly on your home Wi-Fi but stalls on hotel or airport Wi-Fi, the network itself is filtering VPN traffic — not a bug in the app. Skip straight to the network section below.
Step-by-step: get reconnected
- Close the app completely (not just minimize it) and reopen it.
- Sign out and sign back in. RunVPN fetches its connection configuration automatically after login — there’s nothing to import or paste by hand, so a fresh sign-in also refreshes your config from the server.
- Toggle airplane mode for five seconds to force your device to re-establish its network path.
- Switch between Wi-Fi and mobile data and try connecting on each.
- Update the app if an update is available in the store.
- Reboot the device if none of the above worked — this clears stuck network sockets that quietly block new connections.
Why connections actually break: MTU, DPI, and the network in between
A lot of “it just won’t connect” reports trace back to packet size, not the app itself. Modern VPN protocols such as WireGuard wrap every packet inside its own encrypted envelope, and that wrapper takes roughly 80 bytes off a standard 1500-byte network path — which is why WireGuard-based tunnels default their interface MTU to around 1420 bytes. On networks with an even smaller usable path (some mobile carriers, hotel routers, satellite links), that default can still be too large, and oversized packets get silently dropped rather than rejected with an error — engineers generally recommend not pushing MTU below 1280 bytes to avoid this kind of silent packet loss.
The other common cause is network-level filtering. Deep packet inspection (DPI) doesn’t need to decrypt your traffic to interfere with it — it can recognize protocol patterns and behavior consistent with VPN tunnels and slow or drop them accordingly. This is one reason RunVPN runs on Xray with VLESS-Reality (XTLS-Vision) and AmneziaWG under the hood: both are built to look like ordinary encrypted traffic on the wire, which keeps the connection stable and private rather than getting flagged as an anomaly.
Public Wi-Fi, corporate networks, and captive portals
Some networks restrict traffic by design, and no amount of app troubleshooting will fix a network that’s actively filtering:
- Hotel and airport Wi-Fi often route all traffic through a captive portal first — open a browser and accept the login page before connecting the VPN.
- Corporate and school networks frequently allow only specific ports and can block anything that looks like an encrypted tunnel.
- Some mobile carriers apply aggressive traffic shaping on certain plans, which can interfere with any encrypted app, VPN included.
Quick reference: symptom, cause, fix
| Symptom | Likely cause | What to try |
|---|---|---|
| Spins forever, never connects | Outdated app or stale login session | Update the app, sign out and back in |
| Connects, then drops after seconds | MTU mismatch on the current network | Switch Wi-Fi/mobile data, retry |
| Works at home, fails on hotel Wi-Fi | Network-level filtering or captive portal | Open a browser, accept the portal page first |
| ”No internet” even with VPN off | Underlying network/ISP issue | Restart router, contact ISP if it persists |
| Connects but pages won’t load | Device clock drift or DNS hiccup | Check date/time, reboot device |
FAQ
Why does my VPN work on Wi-Fi but not on mobile data? Carriers sometimes apply stricter traffic filtering or a smaller usable packet size on cellular networks than on home broadband, which can affect encrypted tunnels differently on each.
Do I need to manually enter server settings? No. After signing in, RunVPN fetches its configuration automatically — there’s no manual setup, no QR code, and nothing to paste.
Is a failed connection a sign my account is compromised? Not on its own. Failed connections are overwhelmingly caused by local network conditions, an outdated app, or a stale session — not account security issues.
Should I try a different protocol if one keeps failing? RunVPN selects between AmneziaWG and VLESS-Reality (XTLS-Vision) automatically to keep the connection stable, so there’s nothing to switch manually — reconnecting after a sign-out often triggers a fresh selection.
Still stuck after the checklist above? Reinstalling the app resets any corrupted local session data and is usually the fastest last resort.