This article addresses the common question, “What should I do if v2rayNG won’t connect?” It focuses on four areas to check: node availability, your phone’s network IP, DNS resolution, and your browser’s proxy settings. It’s intended for Android users who have already imported a VLESS, VMess, or Trojan configuration, or a subscription link, but are seeing timeouts or handshake failures, or can’t open webpages.
1. Check that the node and basic settings are working
Connection failures often aren’t caused by a faulty client. The node may have expired, the subscription may not be up to date, or the imported settings may be incomplete. Start by checking the following:
- Open v2rayNG, tap the menu in the upper-right corner, and select “Update subscription” to make sure you’re using the latest nodes.
- Long-press the current node and select “Test current service connection latency.” If it keeps timing out, try another node from the same subscription.
- Go to “Settings” and check that “Local DNS” hasn’t been changed to an unavailable address. If you’re unsure, restore the default setting.
- Check that your phone’s clock is correct. An incorrect system time can cause TLS handshake failures.
- Turn Airplane mode on and off to get a new network IP, then reconnect with v2rayNG.
If you’re using the free nodes provided on this site, import the latest subscription or a configuration updated that day. The availability of free nodes can change with network conditions.
2. Connection issues caused by your IP or network
If the same node works over Wi-Fi but not mobile data, the cause is usually your carrier’s routing, your current public IP, or network restrictions. Try switching between 4G/5G and Wi-Fi, restarting your router to get a new public IP, or disconnecting from your campus or company network’s secondary authentication before trying again.
If the v2rayNG log shows timeout, connection refused, or no route to host, your current network probably can’t reach the node. Don’t keep changing protocol settings—instead, switch nodes or change networks.
3. Check DNS settings and your browser
Sometimes v2rayNG shows as connected, but your browser still can’t open webpages. The issue may be DNS or the browser’s proxy cache. Try the following:
- In v2rayNG settings, enable “Bypass LAN and mainland addresses,” or test once in global mode.
- Temporarily turn off Private DNS in your phone’s system settings to prevent conflicts with the client’s DNS.
- Clear your browser cache, or test with Chrome, Edge, or Firefox.
- Turn off proxy and ad-blocking extensions in your browser to avoid routing traffic twice.
- Test several websites rather than relying on just one to determine whether the connection works.
If only one browser fails while other apps can access the internet, v2rayNG itself is probably working. Check that browser’s proxy, cache, and Secure DNS settings.
4. Check the logs to identify common errors
Tap the log icon in the upper-left corner of the v2rayNG home screen to see more specific errors. Common messages include: timeout, usually meaning the node is unreachable or the network is blocking the connection; TLS handshake failed, possibly caused by an incorrect system time, an SNI mismatch, or an unavailable node; and DNS lookup failed, which usually means DNS resolution has failed.
Follow the same troubleshooting order each time: update the subscription, switch nodes, change networks, turn off Private DNS, try a different browser, and check the logs. Don’t start by changing core settings such as the UUID, port, or transport protocol. Configurations generated from an imported subscription usually don’t need manual changes.
In short, if v2rayNG won’t connect, first determine whether the problem is an unreachable node or an issue with your device or network. Most problems can be resolved by updating the subscription, switching networks to get a new IP, restoring the default DNS settings, or clearing the browser’s proxy environment. If multiple nodes fail on multiple networks, try a different subscription source or wait for the node provider to fix the issue.