If OpenVPN on your device connects and then drops after a few seconds, or doesn't respond to the Connect button at all, here are the six most common causes with concrete fixes for Windows, Android, and iPhone in 2026.
If you haven't set up your OpenVPN profile yet, start with the guide on how to configure OpenVPN — some of the errors below trace back to a wrong initial setup rather than a connection failure.
What \u201cOpenVPN is not working\u201d actually means: three different symptoms
Before chasing a cause, pin down which failure you actually have — the fix is different for each one.
- Won't connect at all — the Connect button spins and returns an error or timeout, the tunnel never comes up.
- Connects and immediately drops — status shows \u201cConnected\u201d, then the connection resets itself after a few seconds.
- Connects but there's no internet — status stays \u201cConnected\u201d, but sites won't load or load with errors.
The first two cases almost always trace back to causes 1-4 and 6 below; the third is usually cause 5 or a DNS setting (see the FAQ).
Cause 1. A corrupted or outdated .ovpn file
An outdated or broken configuration file is the single most common reason OpenVPN fails to connect. The .ovpn profile stores the server address, port, protocol, and certificates — if the server's IP changed or the certificate was reissued, the old file simply can't reach the node anymore.
A telltale sign is a TLS key negotiation timeout error, or the app hanging on \u201cResolving host\u201d right after you try to connect.
How to get a fresh .ovpn profile
- Open your VPN service account and download the current configuration file for the server you need.
- Remove the old profile from the client entirely (not just disconnect — delete it), so the app doesn't fall back on cached parameters.
- Import the new file and reconnect without changing any other settings.
Cause 2. The server is unreachable or overloaded
If the configuration is correct but the connection still drops during the handshake, the specific server is likely temporarily unresponsive: it could be under maintenance, overloaded with connections, or pulled out of rotation by the VPN provider.
How to check: switch to a different city or country in the same app. If the alternate server connects fine, the issue was never your profile or your network — it was that one node.
Cause 3. Why switching to TCP:443 helps
OpenVPN defaults to UDP port 1194 — exactly the port most often blocked by corporate firewalls, hotel guest Wi-Fi, and some home routers with aggressive security settings. TCP:443 is the same port used by regular encrypted web traffic (HTTPS), so a connection on it is harder to tell apart from an ordinary website visit, and network equipment is less likely to block it \u201cby port.\u201d
| Parameter | UDP 1194 | TCP 443 |
|---|---|---|
| Latency | Lower, better for video and gaming | Slightly higher due to delivery acknowledgements |
| Stability on restrictive networks | Lower — the port is often closed by firewalls | Higher — blends in with regular HTTPS traffic |
| Compatibility | May not pass through hotel or office guest Wi-Fi | Passes through almost anywhere websites are reachable |
If the app lets you pick the transport manually, switch to TCP:443 and reconnect — for most handshake-stage failures, that's the fastest fix. LiMP VPN lets you switch protocol and port right in the app, no reinstall needed — see pricing and features for details.
Cause 4. An expired certificate or device clock drift
OpenVPN checks the TLS certificate's validity on every connection, and that check relies on the device's system date and time. If the clock is off by even a few minutes — common after a phone reboots without network access, or after a time zone change — the client can treat a valid certificate as expired and reject the connection with a Certificate verify failed error.
Check that date, time, and time zone are set to automatic in your device settings, then reconnect.
Cause 5. Network interference along the route: why the protocol sometimes gets shaky on its own
Even with a correct profile, a reachable server, and the right time on your device, a connection can drop now and then for no obvious reason — and it isn't always a settings problem. In 2026, some networks in Russia apply more active traffic filtering at the backbone level, and classic protocols, including OpenVPN and WireGuard, sometimes lose stability as a result. This is a general reliability factor of a given network, not a sign of a problem with your specific device or account.
If drops keep repeating on the same network (say, at home but not at work), try switching protocol and transport to TCP:443 — for many users that noticeably improves stability. For more on how traffic filtering works, see what is DPI.
Cause 6. Wrong login credentials or a two-factor account lock
An AUTH_FAILED error means the server rejected not the network connection but the credentials themselves. The most common causes are an expired password, an accidentally wrong keyboard layout while typing, or a temporary account lock after several failed login attempts.
Reset your password through the account dashboard, make sure your keyboard layout and Caps Lock are off, and try again — if the account is temporarily locked, waiting a few minutes is usually enough.
Step-by-step checklist: 5 steps if nothing else worked
If the cause is still unclear, work through these in order — most OpenVPN failures get resolved by step two or three.
- Check the internet without the VPNTurn OpenVPN off and open any website to confirm the network itself works.
- Refresh the .ovpn profileDownload a current configuration file from your account and import it again.
- Switch the protocol to TCP:443If the app lets you pick the transport, switch from UDP to TCP and reconnect.
- Check the device's date and timeTurn on automatic sync for date, time, and time zone.
- Reinstall the clientRemove and reinstall the OpenVPN app from an official source — this clears any cached settings.
OpenVPN across devices: how the diagnosis differs
The causes of failure are the same across platforms, but the way you check them differs. If the steps above didn't solve it, see the device-specific breakdown: VPN not working on Android, VPN not working on PC.
Error code \u2192 likely cause \u2192 what to do
| Error code | Likely cause | What to do |
|---|---|---|
| AUTH_FAILED | Wrong login credentials or account lock | Reset password, check keyboard layout, wait out any lock |
| TLS Error | Expired certificate or clock drift | Turn on automatic date and time sync on the device |
| Connection refused | Server unreachable or temporarily out of rotation | Switch to a different city or country |
| TLS key negotiation timeout | Outdated or corrupted .ovpn profile | Download and import a fresh configuration file |
| Certificate verify failed | Expired certificate on the client side | Refresh the profile, check the device's date and time |
| No route to host | Port blocked by the network or a firewall | Switch protocol and transport to TCP:443 |
If none of these steps help, contact support and include the error code, your carrier, and your device type — that speeds up diagnosis on the server side.
