This article addresses the common question, “What should I do if v2rayNG won’t connect?” It focuses on a low-risk troubleshooting order: first check your device and node settings, then see whether switching between Wi-Fi, mobile data, or another network helps. Avoid repeatedly reinstalling the app or changing settings at random.
1. Start with the safest basic checks
A v2rayNG connection failure doesn’t necessarily mean the node is down. It could also be caused by an incorrect system time, an outdated subscription, or the wrong proxy mode. Follow the steps below in order, testing the connection after each one.
- Open your phone’s browser and make sure regular websites load, to rule out a local internet outage.
- In v2rayNG, tap the menu in the upper-right corner and select “Update subscription,” or re-import the free node subscription provided on this site.
- Long-press the current node and select “Test real connection” or “Test latency.” If all tests fail, don’t keep tapping Connect repeatedly.
- Check that your phone’s time is set to update automatically. An incorrect time can cause a TLS handshake to fail.
- Make sure the system VPN permission is enabled. You should see a VPN icon at the top of the screen when connected.
If only one or two nodes fail, try another node first. If all nodes fail, continue by checking your network environment.
2. Check whether your network is the problem
When should you switch networks? Here’s a simple rule of thumb: if the same set of nodes all fail on one network but connect on another, the original network may be restricting connections. For example, company, campus, and public Wi-Fi networks may restrict proxy connections or block certain ports.
- If your home Wi-Fi doesn’t work, switch to mobile data and test again.
- If mobile data doesn’t work, switch to Wi-Fi, or toggle airplane mode off and on before trying again.
- If public Wi-Fi doesn’t work, complete the web-based sign-in first, then connect with v2rayNG.
- If a company or campus network doesn’t work, try a personal network instead. Avoid high-risk attempts to bypass restrictions.
The key is to switch networks without changing complex protocol settings. If the connection works immediately after switching networks, v2rayNG and the node are probably fine.
3. Low-risk ways to troubleshoot nodes and subscriptions
If you still can’t connect on different networks, check the nodes next. Free nodes may stop working due to changes in load, routing, or availability. This is normal. In v2rayNG, you can delete nodes that clearly aren’t working, re-import the subscription, or test nodes that use different protocols or locations.
To import a subscription, copy the subscription link, tap “+” in v2rayNG, then select “Import from clipboard” or “Subscription settings.” Save your changes and update the subscription. Don’t change fields such as address, port, id, security, or network at random. A single incorrect setting can prevent the connection from working.
If you’re using a VLESS, VMess, Trojan, or other node, an outdated client version may also cause compatibility issues. Update v2rayNG from a trusted source, and don’t download modified versions from unknown sources.
4. Check log keywords if the problem persists
v2rayNG logs can help point you in the right direction. Common messages include: timeout, which usually means the network or node is unreachable; TLS handshake failed, which may be related to the system time, certificate, or node settings; connection refused, which may mean the node’s port isn’t available; and no route or DNS-related errors, which you can check again after switching networks.
In short, if you can’t connect, update the subscription and test the nodes first, then switch between Wi-Fi and mobile data to check the network, and finally review the logs. Make changes one step at a time, and change only one variable at a time—this is usually more effective and safer than reinstalling the client.