This article helps beginners troubleshoot what to do when v2rayNG won’t connect. Check each item in turn—from nodes and subscriptions to your mobile network, DNS, time settings, and client configuration—to determine whether the problem is caused by an unavailable node, network restrictions, or settings on your device.
1. Check whether the problem is with the node or subscription
Many connection failures aren’t caused by a faulty phone, but by an unavailable node, an expired subscription, or an issue with the imported format. Start with these simple checks.
- Open v2rayNG, switch to another node, and try connecting again. Don’t test just one node.
- Long-press a node and select “Test real connection” or “Test latency.” If all tests fail, the problem is likely with your subscription or network.
- If you use a subscription link, open the subscription settings and tap “Update subscription” to check whether it can be fetched successfully.
- When copying nodes from the free nodes page on this site, make sure you don’t omit link prefixes such as vmess, vless, or trojan.
If only one node fails, switch to another. If all nodes fail, continue checking your phone’s network and client settings.
2. Check your phone’s network environment
v2rayNG can be sensitive to network conditions. Wi-Fi, mobile data, campus networks, and corporate networks may each have different restrictions. Try the following:
- If the connection fails over Wi-Fi, switch to mobile data and try again.
- If it fails over mobile data, turn on Airplane mode for 10 seconds, then turn it off to reconnect to the network.
- Close other VPNs, accelerators, and ad blockers to avoid port conflicts.
- If you’re using public Wi-Fi, first open a web page in your browser to check whether you need to sign in.
If switching networks fixes the problem, the original network may be blocking or interfering with the connection. In that case, v2rayNG itself isn’t faulty.
3. Check v2rayNG’s basic settings
Beginners often overlook app permissions and routing settings. Check the following:
- Make sure your phone allows v2rayNG to create a VPN connection. Tap “OK” when the permission prompt first appears.
- In v2rayNG’s settings, leave “Enable local DNS” at its default setting for now; avoid changing it repeatedly.
- Beginners should choose “Bypass LAN and mainland China addresses” for the routing mode, or leave the default rules enabled.
- Check your phone’s date and time. We recommend enabling “Set time automatically.” An incorrect time can cause TLS-based nodes to fail during the handshake.
If you’ve changed many advanced options, the simplest solution is to back up your nodes, clear the app’s data, and import your subscription again.
4. Use error messages to identify the cause
The v2rayNG log can provide useful clues. Tap the log icon in the top-right corner, or check the messages after connecting. Common errors include:
- timeout: Usually means the node is unreachable, the network is blocking the connection, or the current route is congested. Try another node or network first.
- connection refused: The node’s port is unavailable or its service is experiencing issues. This usually can’t be fixed in the client.
- tls handshake failed: The time may be incorrect, or the SNI/security settings may not match. Check the time and re-import the node.
- failed to resolve: There may be a DNS resolution issue. Switch networks or restart your phone and try again.
5. Recommended troubleshooting steps for beginners
Don’t start by changing settings at random. Follow these steps in order for a more efficient diagnosis:
- Update your subscription or import the nodes again.
- Test at least three different nodes.
- Switch between Wi-Fi and mobile data to test both.
- Restart v2rayNG and your phone.
- Check the system time and VPN permissions, and make sure no other VPN app is causing a conflict.
- Check the log and use the error message to determine whether you need to switch node providers.
In summary, the most common reasons v2rayNG won’t connect are an unavailable node, an outdated subscription, network restrictions, or missing VPN permissions on your device. Beginners should avoid changing advanced settings unnecessarily. Start by testing working nodes on a stable network with the default settings to pinpoint the problem more easily.