This article answers the question “What should I do if v2rayNG won’t connect?” Without getting into complex theory, it walks you through four areas—your phone and network environment, node configuration, client settings, and network restrictions—to help you quickly determine whether the problem is an inactive node, an incorrectly imported subscription, or your local network.
1. Check your phone and network environment first
Many connection failures aren’t caused by v2rayNG itself, but by issues with the environment. Start by checking these commonly overlooked areas:
- Make sure your system time is correct: Turn on automatic time and time zone settings on your phone. A large time discrepancy can cause TLS certificate verification to fail.
- Try a different network: Switch between Wi-Fi and mobile data to rule out network blocking, DNS issues, or router restrictions.
- Turn off other proxies/VPNs: Run only one VPN app at a time to avoid port conflicts or routing issues.
- Check v2rayNG permissions: Make sure it’s allowed to create a VPN connection. Some system management apps may block background network access.
- Restart your phone and try again: This can clear leftover VPN tunnels and network cache, especially after frequently switching nodes.
2. Check whether the node or subscription is working
If your environment is fine, check the node next. This site provides some free nodes for testing, but they may become unavailable due to load, location, or expiration. Try several nodes to compare results.
- Long-press the current node and select “Test current configuration’s real connection” or “Test all configurations’ real connections.” If the latency is blank or the test fails, try another node first.
- Make sure the subscription link is complete, with no missing characters, and don’t mistake a webpage address for a subscription link.
- After importing, check that the protocol type—such as VLESS, VMess, or Trojan—has been identified correctly.
- If the node uses TLS, Reality, WebSocket, or other settings, missing SNI, Host, or Path values can also prevent it from connecting.
A common symptom is that the import succeeds, but the connection drops as soon as you connect. This usually means the format was recognized, but the remote service is unavailable or a key parameter doesn’t match.
3. Practical settings in the v2rayNG client
After opening v2rayNG, try these steps in order:
- Update the client to a recent version. Older versions may not support some VLESS, Reality, or sing-box-converted configurations.
- Select “Update subscription” from the top-right menu. Don’t import it once and then leave it unrefreshed.
- In the routing settings, select “Global proxy” to test the connection first. Once it works, switch to bypassing the LAN or using per-app proxying.
- Check the logs for error keywords. For example, “timeout” usually indicates a network issue or an unreachable node; “TLS handshake failed” often points to a certificate, SNI, or time issue; and “connection refused” usually means the port or service is unavailable.
If you’re unsure whether routing rules are the problem, the simplest approach is to use Global mode to visit a commonly used test website. Once that works, you can fine-tune the rules.
4. Quick guide to diagnosing connection failures
- All nodes fail: First check your phone’s time, network, permissions, carrier restrictions, and client version.
- Only one node fails: That node is likely inactive, congested, or using changed parameters.
- Connected, but webpages won’t open: Check whether your browser is using the proxy, or try changing DNS or switching to Global mode.
- Shows as connected, but your IP hasn’t changed: The routing rules may not be applying, or the target app may not be selected for per-app proxying.
Finally, keep a working configuration for comparison. When something goes wrong, avoid changing too many settings at once. Check each item in order: network environment → node availability → client settings → log errors. This usually helps you quickly pinpoint why v2rayNG won’t connect and avoids repeated reinstalls that don’t address the underlying problem.