This article addresses a common question: “What should I do if v2rayNG won’t connect?” It’s intended for users who are just getting started with V2Ray/VLESS nodes. Follow the checks below in order: first check your network, then your nodes and subscription, and finally your client settings. This can save you from repeatedly reinstalling the app right away.
1. First, check whether the problem is with your network
Many connection failures aren’t caused by v2rayNG itself, but by network restrictions, DNS issues, or conflicts with your system proxy. Start with these basic checks:
- Close v2rayNG and open a domestic website in your browser to confirm that your phone can access the internet normally.
- Switch networks—for example, switch from Wi-Fi to mobile data, or try a different Wi-Fi network.
- Turn off any other VPNs, accelerators, or packet-capture tools to prevent multiple proxies from handling your network traffic at the same time.
- Check that your phone’s clock is accurate. A significant time discrepancy can cause TLS connection failures.
- If you’re using a company, campus, or hotel network, ports or protocols may be restricted. Try a different network to check.
If you can connect over mobile data, the original Wi-Fi network may be restricted. If you can’t connect on any network, continue by checking your nodes and configuration.
2. Check whether the node is working
An unavailable node is one of the most common reasons v2rayNG won’t connect. Free nodes in particular may stop working because of high usage, maintenance, or expiration. Here’s how to check:
- Long-press the current node and select the real connection test or latency test to see whether it returns a result.
- Try other nodes in the same subscription rather than repeatedly attempting to connect to just one.
- If you’re using a free node provided on this site, copy the latest subscription or node link and import it again.
- Make sure the imported configuration uses a format supported by v2rayNG, such as vmess, vless, or trojan.
Note that a successful latency test doesn’t guarantee that you’ll be able to access external sites. However, if all nodes time out, the subscription may have expired, the network may be restricted, or the client may be misconfigured.
3. Reimport the subscription and update the configuration
If you’re using a subscription link, update the subscription first rather than manually changing a number of settings. The steps are usually: open v2rayNG, tap “+” in the upper-right corner, select “Subscription settings,” add or edit the subscription URL, then return to the main screen and update the subscription.
After updating, select a node and tap the Connect button in the lower-right corner. The first time you connect, the system will prompt you to create a VPN connection; you must tap Allow. If no prompt appears, check the VPN permissions in your phone’s system settings or restart your phone and try again.
4. Check common v2rayNG settings
It’s easy for new users to change an option by mistake, preventing an otherwise working node from connecting. Check these settings in particular:
- Routing mode: If you’re unsure, use the default rules to avoid accidentally blocking all traffic.
- Local DNS: If DNS resolution is failing, try restoring the default DNS settings.
- Allow LAN connections: This usually doesn’t need to be enabled for ordinary phone use.
- Per-app proxy: If enabled, only the selected apps will use the proxy, which can make it seem like the connection isn’t working.
If you’re not sure which settings you’ve changed, back up your nodes, clear the app data, and reimport the subscription to test it. This simple but effective approach is useful for troubleshooting a misconfigured setup.
5. Check the logs to identify the error
The v2rayNG logs can offer useful clues. After a connection fails, open the logs. If you see “timeout,” the network or node is probably unreachable. If you see terms related to “certificate,” “TLS,” or “handshake,” the issue may be your device’s clock, TLS, or the node configuration. If you see “no route” or “dns error,” check your routing and DNS settings first.
In short, if v2rayNG won’t connect, try these steps in order: switch networks, switch nodes, update the subscription, check permissions, and review the logs. Avoid repeatedly installing different clients or changing advanced settings at random. Most issues can be resolved by updating to a working node and restoring the default settings.