This article addresses the question “What should I do if v2rayNG won’t connect?” and is designed to help beginners troubleshoot step by step: check your phone’s network, node configuration, subscription updates, and system VPN permissions to determine whether the issue is caused by your network, an unavailable node, or a client setting.
1. First, rule out local network issues
Sometimes v2rayNG shows that it’s connected, but web pages won’t load. That doesn’t necessarily mean the node is down. Start with these basic checks:
- Close v2rayNG and open a domestic website directly to confirm that your phone can access the internet.
- Switch between Wi-Fi and mobile data to test the connection. Some public Wi-Fi networks restrict proxy connections.
- Turn off power-saving mode, data-management apps, network boosters, and other tools that may block background network access.
- Make sure your phone’s time is set to update automatically. A significant time discrepancy can affect handshakes for some protocols.
If the connection works on mobile data, the Wi-Fi network may be restricted. If it fails on all networks, continue checking the node and client.
2. Check whether the node is working
The most common reason v2rayNG fails to connect is that the node is unavailable or the subscription has expired. In v2rayNG, long-press the current node and try “Test current configuration connection” or “Test all configurations.” If the latency shows -1, timeout, or failed, the node is usually temporarily unavailable.
The fix is simple: update your subscription, then try another node. This site also shares some free nodes for learning and testing, but their reliability depends on the number of users and network conditions, so it’s best not to rely on just one node.
- Subscription users: Tap the menu in the upper-right corner and select “Update subscription.”
- Users who import nodes manually: Copy and import the vmess, vless, trojan, or other links again.
- If you have multiple nodes: Test nodes in different regions and using different protocols first.
3. Check that v2rayNG settings haven’t been changed by mistake
Beginners may accidentally change routing, proxy mode, or DNS settings, making it appear connected even though nothing can be accessed. Check the following:
- Open v2rayNG settings. You can leave “Enable local DNS” at its default setting for now; if you’re unsure, don’t change it.
- For routing mode, start with “Bypass LAN and mainland addresses,” which suits most everyday use.
- When connecting, the system will prompt you for VPN permission. You must tap Allow. If no prompt appears, restart your phone and try again.
- Make sure no other VPN, proxy, or ad-blocking apps are running at the same time, as they may cause port conflicts.
If you’ve changed many settings, back up your nodes, clear v2rayNG’s app data, and reimport your subscription to test again.
4. Use the logs to identify the type of error
Tap Logs at the bottom of v2rayNG to see why the connection failed. Common messages include timeout, connection refused, TLS handshake failed, and EOF. You don’t need to understand every line to narrow down the issue: if multiple nodes time out, your current network is likely restricted; if only one node reports an error, its configuration or status is likely the problem; if errors persist after updating your subscription, your client may be outdated.
Install the latest version of v2rayNG from an app store or the project’s release page, and avoid modified versions from unknown sources. After updating, reimport your nodes and test the connection again.
5. Recommended troubleshooting order for beginners
If you can’t connect, don’t keep changing settings at random. Follow this order to find the problem faster: switch networks, update your subscription, try another node, restart v2rayNG, check VPN permissions, review the logs, and update the client. Most issues can be identified in the first few steps.
If none of the nodes work on any network, consider switching subscription providers or waiting for the connection to come back. Keeping your client, subscription, and phone network settings up to date is key to reducing v2rayNG connection failures.