This guide addresses the question “What should I do if v2rayNG won’t connect?” From your phone’s network and node details to subscription updates and common errors, follow this checklist step by step to pinpoint the cause—no log-reading skills required.
1. Check your login and network environment
Many connection failures aren’t caused by v2rayNG itself. The issue may be your current network, system permissions, or an expired node. Start with these basic checks:
- Make sure your phone can open websites normally. If your Wi-Fi has no internet access, switch to 4G/5G and test again.
- Turn off any other VPNs, boosters, or proxy apps to avoid conflicts with ports or virtual network adapters.
- Check that your system clock is accurate. A significant time difference can cause TLS handshake failures.
- Make sure v2rayNG has VPN permission. When connecting for the first time, tap “OK” in the system prompt.
- If you’re using company, campus, or hotel Wi-Fi, access may be restricted. Try switching to mobile data.
If switching networks fixes the problem, the issue is likely with your current network. If it still fails on every network, continue checking your node and configuration.
2. Check whether the node or subscription is working
Open v2rayNG and long-press the current node, then run “Test real connection” or “Test latency.” If the test times out or fails, the node may be unavailable, its port may be blocked, or its configuration may have expired.
- Subscription users: Open the menu in the top-right corner and select “Update subscription.” After it updates, select a node and try connecting again.
- For manually imported nodes, check that the address, port, UUID, encryption, transport protocol, TLS, SNI, and other fields match the provider’s settings.
- If importing from a QR code fails, try copying the complete vmess, vless, or trojan link and importing it from the clipboard.
- Free nodes provided on this site may also stop working due to network fluctuations. Keep several nodes available so you can test them against one another.
Note: Low latency doesn’t guarantee that a node will work. The real connection test is a more useful indicator. If several nodes all fail, first suspect your local environment or client version.
3. How to interpret common errors
You don’t need to understand every line in the v2rayNG log, but a few keywords can help point you in the right direction. Open the menu in the top-right corner, tap Logs, connect once, and check the last few lines.
- If you see timeout or deadline exceeded, the node is usually unreachable, its port is blocked, or the current network is restricting access.
- If you see TLS handshake failed, the system time may be incorrect, the SNI may be wrong, or the TLS settings may not match.
- If you see connection refused, the server port may not be open or the node may no longer be working.
- If it connects but websites won’t load, check the routing mode. First test with “Global,” then switch back to “Bypass LAN and mainland addresses.”
4. Quick fixes
If you don’t want to troubleshoot each setting individually, try these steps in order:
- Restart your phone and close any other proxy apps.
- Update v2rayNG to a recent version.
- Update your subscription or import the node again.
- Test at least three different nodes.
- Switch between Wi-Fi and mobile data and test again.
- Temporarily set the routing mode to Global and check whether you can access external websites.
If it still fails, try using the current node in another client, such as Clash or sing-box. If it works in another client, the issue is probably with the v2rayNG configuration or version. If it fails everywhere, the node or network environment is most likely the problem. Avoid changing all the settings at once. Change only one setting at a time to make it easier to identify the real cause.