In short: A VPN fails to connect in 9 out of 10 cases because of network settings, an outdated protocol, or app restrictions — not because of the service itself. Check your internet without VPN, switch protocols, and disable Private DNS. If that doesn't help, find a device-specific guide in the section below. To verify your tunnel is correctly established, see how to check that your VPN is working correctly.
A VPN that won't connect is a typical technical problem with a systematic solution: narrow down the area (internet? service? device?) and fix the specific cause. This article covers all universal diagnostic steps regardless of operating system or connection type.
Step 1. Check Whether Your Internet Works Without VPN
The first step is to confirm that the VPN service has a working connection to start with; if the internet doesn't work without VPN, the problem is not with the app.
How to Check Basic Connectivity
- Fully disconnect the VPN app (don't just switch servers).
- Open any website in a browser — for example, google.com. It should load without VPN.
- If the page doesn't load — the problem is your internet connection. Restart your router, check your mobile data balance, or switch to a different network.
- If the page loads fine but VPN still won't connect — proceed to the next steps.
Extra check: on Android or a PC, open a terminal and run ping 8.8.8.8. If packets go through, IP connectivity is fine and the problem is at the VPN layer, not the underlying network.
When the Cause Is a LiMP VPN Server
If the internet works without VPN but no LiMP VPN server connects, check the app for status notifications. Temporary unavailability of a specific server is normal — the fix is to switch servers (Step 2).
Step 2. Restart VPN and Switch Protocol
Different protocols have different compatibility with network infrastructure; WireGuard is faster on mobile internet, IKEv2 is more stable on unstable connections, and OpenVPN TCP is the most permissive through restricted networks.
WireGuard, IKEv2, OpenVPN — Reliability Differences
- WireGuard — the fastest modern protocol; uses UDP. May not work on networks where the carrier restricts UDP traffic or uses Deep Packet Inspection.
- IKEv2 — handles seamless handovers between Wi-Fi and mobile data (MOBIKE support); survives network changes without dropping the tunnel.
- OpenVPN TCP — the most permissive through corporate and public network restrictions: port 443 traffic is indistinguishable from regular HTTPS and is rarely blocked by routers.
For a detailed protocol comparison and step-by-step switching instructions, see how to change VPN protocol on phone and PC in 2026.
Switch Servers
If the protocol works in principle but the connection is unstable, switch servers. Selection criteria: geographic proximity (lower latency) and server load (the app usually shows a load indicator). Try two or three servers in different regions — the issue may be overload on one specific node, not the protocol or device.
Step 3. Check Your Network Settings
Device network settings and conflicting apps are the second most common cause of a broken VPN connection after basic internet issues.
Private DNS and VPN Conflict
Private DNS (DoH/DoT) operates in parallel with the VPN tunnel and can create a routing conflict: the connection shows as 'Connected' but sites don't load, because DNS queries are bypassing the tunnel.
- Android: Settings → Network & Internet → Private DNS → select Off. Restart VPN and retest.
- iOS: Settings → Wi-Fi → (i) next to your network → DNS → switch to Automatic. Remove any third-party DoH/DoT profiles if installed.
MTU and Packet Fragmentation
MTU (Maximum Transmission Unit) is the maximum size of a data packet. If the MTU on the interface is larger than the network allows — especially relevant for 5G and some carriers — packets get fragmented or dropped, causing VPN to connect slowly then time out.
Characteristic symptom: VPN hangs on the connecting screen, then throws an error or silently reverts. Fix: switch from WireGuard to IKEv2 (lower overhead), or try a different server — MTU issues often depend on the specific network route, not the device itself.
Conflicting Applications
VPN connections can be blocked or disrupted by:
- Another active VPN profile — even a disconnected but not removed profile can hold the TUN interface and block a new connection.
- Antivirus or firewall software — some block TUN adapters as suspicious virtual network interfaces.
- Corporate MDM profiles with a VPN prohibition policy (see Step 4).
Check: Settings → (Network & Internet →) VPN — there should be exactly one active profile. Delete unused profiles.
Step 4. Remove App Restrictions
Both iOS and Android aggressively manage background app activity to save battery — and VPN often becomes a victim of this optimization, especially on devices with aggressive power-saving profiles.
Battery Optimization Kills Background VPN
Android can forcibly stop the VPN process when the screen turns off, especially on MIUI (Xiaomi), One UI (Samsung), and ColorOS (OPPO/Realme) devices.
- Android (stock): Settings → Apps → LiMP VPN → Battery → select Unrestricted.
- MIUI (Xiaomi): Security → Background App Management → LiMP VPN → No restrictions.
- Samsung One UI: Settings → Device Care → Battery → Restrictions → exclude LiMP VPN from sleeping apps.
- iOS: There is no direct battery restriction for VPN, but keep iOS updated — Apple periodically fixes bugs affecting background VPN extensions.
Corporate MDM Profiles and Restricted Networks
A corporate MDM profile (Mobile Device Management) may intentionally block VPN installation or use on a company device — this is a security policy, not a bug.
- Check on iOS: Settings → General → VPN & Device Management.
- Check on Android: Settings → Security → Device Administrators.
- If an MDM profile is present, contact your IT administrator. Removing a corporate profile yourself will break access to work resources.
Update the App and Operating System
iOS and Android updates sometimes change TUN interface APIs or reset VPN app permissions. If VPN stopped working immediately after a system update, first update the LiMP VPN app to the latest version from the App Store or Google Play, then reinstall the VPN profile if needed.
Diagnose by Symptom — Quick Reference Table
If you know the symptom, find your row in the table — faster than running through all four steps in sequence.
| Symptom | Likely Cause | Quick Fix |
|---|---|---|
| "Connected" but sites won't load | DNS conflict or split-tunnel misconfiguration | Disable Private DNS; check selective tunnel settings |
| VPN drops when switching from Wi-Fi to mobile data | Always-On VPN not enabled | Enable Always-On VPN in Android system settings |
| VPN connects slowly, then errors out | MTU / packet fragmentation | Switch to IKEv2 or select a different server |
| VPN won't start after OS update | Compatibility bug / TUN permission reset | Update app; reinstall VPN profile |
| Works on Wi-Fi, fails on 4G/5G | Carrier blocks UDP traffic | Switch to OpenVPN TCP (port 443) |
| No protocol works at all | Antivirus or corporate MDM profile | Check MDM profile; disable third-party firewall |
| VPN keeps reconnecting | Battery optimization kills background process | Remove battery restriction for LiMP VPN |
| TLS handshake error / "Authentication failed" | System clock out of sync | Enable automatic date & time in device settings |
| High ping, packet loss | Selected server overloaded | Switch to the nearest lightly-loaded server |
VPN Not Working on Your Device — Detailed Guides
If the general steps above didn't help, find the guide for your specific device — each covers OS-specific causes and fixes not included in this general walkthrough.
- VPN not working on Android — Private DNS, Always-On VPN, MIUI/One UI Battery, TUN conflicts
- VPN not working on iPhone — iOS profiles, CarPlay, MDM restrictions, iCloud Private Relay
- VPN not working on phone — general mobile guide, cross-platform
- VPN not working on PC — Windows Defender Firewall, TAP/TUN adapter, desktop split tunneling
- VPN not working over Wi-Fi — router settings, UDP blocking at router level, hairpin NAT
- VPN not working on mobile data — carrier restrictions, optimal protocol for 4G/5G
After resolving the issue, verify with the how to check that your VPN is working correctly guide — it takes under a minute.
What to Do If Nothing Worked
If all five steps are done but VPN still won't connect, make sure none of these were skipped:
- Internet without VPN works stably (Step 1).
- All three protocols tried: WireGuard, IKEv2, OpenVPN TCP (Step 2).
- Private DNS disabled, unused profiles removed, conflicting antivirus checked (Step 3).
- Battery restriction removed for the app, MDM profile checked (Step 4).
- LiMP VPN app and operating system updated to the latest versions.
If all conditions are met, contact support: the LiMP VPN features page has current contacts and FAQ. To review plan options, see LiMP VPN pricing plans.
Frequently Asked Questions About VPN Not Working
Why is VPN not working when it says "Connected"?
'Connected' means the tunnel is established, but traffic may be bypassing it due to a DNS conflict or split-tunnel settings. Disable Private DNS on Android and verify that the app's selective tunnel mode isn't excluding the sites you need.
Why does VPN work on Wi-Fi but not on mobile data?
Mobile networks sometimes restrict UDP, which WireGuard relies on. Switch to IKEv2 or OpenVPN/TCP in the protocol settings — these work more reliably on 4G/5G networks with carrier restrictions.
Why did VPN stop working after a phone update?
iOS and Android updates sometimes reset permissions or remove VPN profiles. Update the LiMP VPN app to the latest version, reinstall the VPN profile, and verify the 'Always On' permission is enabled.
What if no VPN protocol works on my phone at all?
If WireGuard, IKEv2, and OpenVPN all fail, check your corporate MDM profile (iOS: Settings → General → VPN & Device Management; Android: Settings → Security → Device Administrators) or third-party antivirus software. On a corporate network, contact your IT administrator.
VPN only fails on one specific Wi-Fi network — why?
Public and corporate Wi-Fi networks often restrict VPN protocols at the router level. Try switching to OpenVPN on port 443 (TCP) — that traffic is indistinguishable from regular HTTPS and is rarely blocked on restrictive networks.