This article addresses the common question, “What should I do if v2rayNG won’t connect?” It focuses on a practical, low-risk troubleshooting order for everyday users: check the client and nodes first, then decide whether to switch between Wi-Fi, mobile data, or another network. Avoid changing settings at random as a first step.
1. First rule out basic settings issues
When v2rayNG won’t connect, the node may not actually be down. The cause could be something simple, such as an incorrect import, an inaccurate device clock, or the proxy mode being turned off. Check the following in order:
- Open v2rayNG and make sure the correct node is selected. A check mark should appear beside it.
- Tap the connect button in the lower-right corner and confirm that the VPN icon appears at the top of your phone’s screen.
- Go to “Routing settings.” If you’re an everyday user, start with the default mode or the mode that bypasses LAN and mainland China addresses. Don’t change advanced rules without a good reason.
- Check that your phone’s time is set to sync automatically. A large time discrepancy can cause TLS connection failures.
- If you use a subscription, tap the menu in the upper-right corner and select “Update subscription,” then select a node and try connecting again.
If you copied a free node from this site or another source, make sure the link is complete and starts with a prefix such as vmess://, vless://, or trojan://. Don’t manually remove or edit any parameters.
2. Check whether the node is working
If you still can’t connect after checking the basics, long-press the node in v2rayNG and select “Test current connection” or “Test latency.” If several nodes time out, that doesn’t necessarily mean they’re all down; your current network may be blocking the connections.
- Only one node fails: Try another node from the same subscription first.
- All nodes fail: Check your network, DNS, and the system’s VPN permissions.
- Latency is shown, but webpages won’t load: The issue may be related to routing mode, browser cache, or DNS.
Free nodes can vary in reliability. If one isn’t working, a low-risk first step is to update your subscription and switch nodes rather than repeatedly changing protocol parameters.
3. When to switch networks
If you’ve completed the checks above and still see messages such as “connection timed out,” “connection refused,” or “TLS handshake timeout,” try switching networks. This usually means switching from home Wi-Fi to mobile data, or trying a different Wi-Fi network.
Consider switching networks in these situations:
- The same node works on mobile data but not on Wi-Fi, which may indicate restrictions on your current Wi-Fi network.
- The same set of nodes works on a friend’s phone or another network, but all fail on yours.
- You often can’t connect on public Wi-Fi, campus networks, or company networks, which may have additional restrictions.
- All nodes still time out after restarting v2rayNG, updating your subscription, and trying different nodes.
Switching networks is a low-risk step: it doesn’t change your node settings or affect your phone’s system settings. When testing, change just one thing at a time. For example, switch from Wi-Fi to 4G/5G without also changing DNS, routing, or nodes. This makes it easier to identify the cause.
4. A low-risk order for troubleshooting connection failures
We recommend following this order: restart v2rayNG, update your subscription, try another node, switch networks, and only then consider reinstalling the client. Avoid enabling advanced options you don’t understand, such as custom transport layers, disguise domains, or skipping certificate verification. Incorrect changes can prevent nodes that previously worked from connecting.
If the problem persists, clear the current v2rayNG configuration and reimport your subscription or node. After importing, test one node first instead of changing many settings at once. This site publishes free nodes and client guides, but free resources can change over time, so it’s a good idea to keep a few backup nodes available.
In summary: If v2rayNG won’t connect, first rule out basic issues with the node, subscription, device time, and proxy switch. If multiple nodes all fail on the same network, try switching between Wi-Fi and mobile data. Troubleshooting step by step can help you quickly determine whether the issue is with the node, the client, or the network.