This article addresses the common question, “What should I do if v2rayNG won’t connect?” It walks you through troubleshooting your nodes, IP, DNS, system time, and browser environment. It’s intended for users who have already imported a VLESS, VMess, or Trojan configuration, or a subscription link, but can’t connect on their phone, have no internet after connecting, or can’t open web pages.
1. First, check that your nodes and basic settings are working
Many connection failures aren’t caused by a faulty client, but by an inactive node, an outdated subscription, or mismatched settings. Start by checking the following:
- Open v2rayNG, tap the menu in the upper-right corner, then select “Update subscription” or re-import your nodes.
- Long-press the current node and select “Test current configuration (real connection)” or “Test all configurations (real connection).”
- If you see a timeout, EOF, or TLS handshake failed error, try another node first.
- Make sure your phone’s time is set to sync automatically. A significant time difference can cause TLS verification to fail.
- Check that you’re running only one proxy app. Avoid using it alongside another VPN or accelerator.
If you’re using our free nodes, we recommend copying the latest subscription link and importing it again. Free nodes can become unavailable, so older configurations may no longer work.
2. Can your IP network affect v2rayNG connections?
Yes. Restrictions vary between mobile carriers, campus networks, company Wi-Fi, and public hotspots. The same node may work on one network but fail to connect on another. To troubleshoot, switch networks: try mobile data instead of Wi-Fi, or home broadband instead of mobile data. If the connection only fails on one network, the cause may be the local network’s internet gateway or firewall policies.
Also, switching nodes frequently or running lots of tests in a short time may cause the destination service to temporarily refuse connections. If this happens, wait a few minutes, then try a node in another region or using a different protocol. Avoid repeatedly tapping the connect button, as this can make it harder to tell whether the client is actually at fault.
3. DNS settings can cause “connected, but web pages won’t open”
If v2rayNG shows that you’re connected but your browser can’t open websites, a common cause is a DNS resolution problem. Try the following:
- In v2rayNG settings, enable “Bypass LAN addresses” to prevent problems accessing your local network.
- Go to “Settings – DNS” and try the app’s default DNS. Don’t enter an address unless you’re sure it’s correct.
- Clear your browser cache or try another browser, such as Chrome, Firefox, or Edge.
- Turn off “Private DNS” in your phone’s system settings, or set it to automatic. Some Private DNS settings can conflict with the proxy.
If only certain websites fail to load while others work, the issue is usually not a general v2rayNG failure. It may be caused by routing rules, DNS, or the destination website’s policies.
4. Check your browser and system environment, too
Browser proxy settings, extensions, and cache can all affect your diagnosis. First, try opening a test page in incognito mode, and turn off ad blockers, proxy extensions, packet-capture tools, and similar software. On Android, also make sure v2rayNG has permission to create a VPN connection and that battery-saving settings aren’t restricting its background activity.
If the logs show connection refused, the node’s port is probably unreachable. A timeout usually indicates network blocking or an unstable node. If you see a message related to certificate, check the time, TLS, SNI, or whether the node has expired. Most users don’t need to change complex low-level settings. Try switching nodes, updating your subscription, or changing networks first.
5. Recommended troubleshooting order
The quickest order is: update your subscription → test multiple nodes → switch between Wi-Fi and mobile data → turn off Private DNS → try another browser in incognito mode → check the log keywords. Following these steps should help you identify whether the problem is with the node, the network, or your device’s environment. If no nodes work on any network, consider uninstalling and reinstalling v2rayNG, then importing the latest subscription again.