NPV Tunnel Not Connecting? 12 Fixes That Actually Work

"Connecting…" forever is the most common complaint about any VPN client. The good news: the cause is almost always one of a dozen things, and you can find which in a few minutes if you go in order.

Start with the logs

Open the Logs tab right after a failed attempt. Words like timeout, authentication failed, TLS, certificate or no route point straight at the fix below.

1. Check your normal internet first

Turn the VPN off and open a web page. If that fails, the problem is your Wi-Fi or mobile data, not NPV Tunnel.

2. Check expiry and data limit

Many configs have an expiry date or data cap. In the Configs tab, look at the details on your config. Expired means you need a fresh one from whoever issued it.

3. Fix the date and time

TLS-based protocols (Trojan, VLESS/VMess over TLS, REALITY) check certificates against the clock. If your phone is a few minutes out, the handshake fails. Enable automatic date and time and automatic time zone.

4. Run a Ping

If Ping times out, the server is down, blocked or the port is wrong. Try again on another network (mobile data instead of Wi-Fi) to see if the network is the culprit.

5. Try another config or protocol

Different networks block different things. If you have several configs, try one that uses another protocol or port, ideally 443. Using a smart group helps: see Smart Route.

6. Re-import the config

A corrupted file, a link with an extra space, or an outdated subscription link can all break a config. Delete it and import again. On iOS, the 57.1 notes specifically mention that re-importing a provider link fixes some affected Trojan configs.

7. Update the app

New releases update the Xray core and fix import bugs. Check the changelog and update from the official store.

8. Remove other VPNs

Android and iOS allow one active VPN. Turn off other VPN apps and remove stale profiles.

9. Check Private DNS

On Android, Settings → Network → Private DNS can interfere with some setups. Try "Automatic" or "Off".

10. Allow background activity

If it connects and then dies a few minutes later, battery management is probably killing it. Follow this guide.

11. Per-app proxy confusion

If only certain apps fail, check the Per-app Proxy setting in the More tab. An app excluded from the tunnel will not use it.

12. Ask the config owner

If everything above checks out, the server may be overloaded or have changed. The app cannot fix a server problem; contact whoever supplies your configuration.

More questions are answered in the FAQ.

A decision tree you can follow in two minutes

1. Does Ping work? If no, go to fixes 4 and 5 (server or network). If yes, continue.
2. Does the log say authentication failed? If yes, your config is wrong or expired (fixes 2 and 6).
3. Does it say TLS or certificate? Fix the date and time (fix 3), then try another SNI or protocol.
4. Does it connect and then die? Battery or network switching (fix 10).
5. Connected but pages will not load? DNS or forwarding problem. See below.

Connected, but nothing loads

This confusing state has a few common causes. The server may not allow forwarding (common with limited SSH accounts). The DNS server in the config may be unreachable, so try a different one in the app's settings. A data limit may have been used up, which some providers enforce by dropping traffic instead of closing the connection. And on some networks IPv6 is broken: check the settings for an IPv6 option and try toggling it.

Works on Wi-Fi but not on mobile data (or the reverse)

Different networks filter differently. A port that works at home can be blocked at a workplace, and mobile carriers sometimes throttle or block UDP-based protocols such as Hysteria2 and WireGuard. Keep a TCP-based config on port 443 in your list as a fallback, and put both in a Smart Route group.

When it is the app and not your setup

Bugs happen. Recent notes mention fixes for saved configs disappearing, restored configs crashing, SSH reconnect after network changes and file opening on 32-bit devices on Android, and improvements to Trojan and WireGuard IPv6 imports on iOS. If your problem started right after an update, see the changelog, then contact support with your version, device and the last log lines.

Frequently asked questions

Keep reading