This guide addresses the common question, “What should I do if v2rayNG won’t connect?” Follow this checklist to troubleshoot your phone’s network, system time, node subscription, app settings, and log messages, so you can quickly determine whether the issue is with your environment, an unavailable node, or an incorrect configuration import.
1. Check your phone and network
Many connection failures aren’t caused by v2rayNG itself, but by an unstable network environment. Rather than repeatedly reinstalling the app, troubleshoot in this order:
- Make sure your phone is online: Open a domestic website in your browser to rule out a Wi-Fi or mobile data outage.
- Try a different network: If Wi-Fi doesn’t work, switch to 4G/5G; if mobile data doesn’t work, try Wi-Fi. This helps determine whether your current network is restricted.
- Disable battery-saving and background restrictions: Some Android systems restrict VPN apps running in the background, causing them to disconnect shortly after connecting.
- Check the system time: A significant time discrepancy can affect TLS connections. We recommend turning on “Set time automatically.”
- Make sure no other VPN is running: Only use one VPN app at a time.
If everything above checks out, continue troubleshooting within v2rayNG. Don’t assume your phone is faulty right away—first rule out network issues and system permission restrictions.
2. Check your nodes, subscription, and proxy mode
Unavailable nodes, expired subscriptions, and incorrectly copied configurations are common reasons v2rayNG won’t connect. This site provides free nodes that you can import, but free nodes may become unavailable due to network fluctuations. We recommend testing several nodes.
- Open v2rayNG, long-press the current node, and select “Test current configuration” or a similar test option.
- If the test times out, try another node instead of focusing on just one.
- If you use a subscription, open the subscription settings and manually update the subscription link.
- Make sure the imported configuration uses the correct protocol, such as VLESS, VMess, or Trojan. Don’t try to import a node using the wrong format.
- Open the menu in the upper-right corner and check the routing mode. If you’re new to the app, start with the default or global mode to test the connection, then switch to rules once you’ve confirmed it works.
If your list is empty after updating the subscription, the link may have expired, been copied incorrectly, or be inaccessible from your current network. Try copying the link again or switching networks before updating.
3. Use logs to identify the error
v2rayNG logs can be very useful. After a connection failure, open the “Logs” page and check the last few lines. Common messages include:
- timeout: Usually indicates an unreachable node, a blocked connection, or an unresponsive server. Try another node and network first.
- certificate or TLS-related messages: Check your system time, or verify that the node configuration is correct.
- connection refused: The node’s port is unavailable. Try another node.
- no route or DNS-related messages: Try changing the proxy mode or selecting a different DNS option in the settings.
If you’re not sure how to interpret the logs, copy the last 5–10 lines and assess them alongside the node type and your current network. Don’t post anything containing account details or a full subscription link on public platforms.
4. What to do if it still won’t connect
Work from the simplest steps to the most involved: restart v2rayNG, switch nodes, update the subscription, switch networks, and only then consider clearing the app’s data or reinstalling it. Before reinstalling, back up your subscription link and working nodes to avoid losing your configuration.
If none of your nodes work on any network, your app version may be outdated. Update v2rayNG through a trusted app store or the project’s release page. After updating, re-import your subscription and run the connection test again. Following this checklist should help you determine whether v2rayNG’s connection issue is caused by your environment, a node, or the configuration.