This article addresses the common issue of “What to do when v2rayNG won’t connect.” It focuses on troubleshooting node status, your phone’s network, IP address, DNS, and browser environment. It’s intended for users who have already imported a VLESS, VMess, or Trojan configuration, or a subscription link, but see timeouts or failures, or can connect but can’t access the internet.
1. First, check that the node and import method are working properly
Connection failures often aren’t caused by a problem with your phone. The node may have expired, the subscription may be out of date, or the configuration may not have been copied in full. Check the following in order:
- Open v2rayNG, tap the menu in the upper-right corner, and select “Update subscription” or reimport your subscription link.
- Long-press the current node and select “Test current configuration” or “Test all configurations.”
- If all nodes fail, check your network and subscription first. If only one node fails, that node is probably unavailable.
- Make sure your phone’s system time is set to sync automatically. An incorrect time can cause TLS handshake failures.
We compile free nodes for testing, but free nodes may stop working due to high usage or fluctuating connections. It’s a good idea to prepare several nodes and test them against one another.
2. Can your IP environment affect v2rayNG connections?
Yes. Some networks restrict proxy connections, including company Wi-Fi, campus networks, public hotspots, and mobile networks experiencing temporary disruptions. To troubleshoot, try switching networks:
- Switch from Wi-Fi to mobile data, or from mobile data to Wi-Fi.
- Turn off other VPNs, network accelerators, and packet capture tools to avoid port or routing conflicts.
- If you’ve had repeated connection failures, turn on Airplane mode for 10 seconds, then turn it off to get a new IP address.
If the connection works after switching networks, the original network may be restricting it. Don’t keep changing node settings; first check whether the network itself is working.
3. Incorrect DNS settings can let you connect but prevent websites from loading
If v2rayNG shows that you’re connected but your browser can’t open Google or YouTube, the problem may be with DNS resolution. Check the “Routing” and “DNS” options in v2rayNG settings. If you’re a typical user, start with the default settings and avoid entering unfamiliar DNS addresses.
If you’ve changed your DNS settings before, try restoring the defaults and restarting v2rayNG. Some Android systems also have “Private DNS” enabled, usually under the network options in system settings. An unavailable Private DNS server can prevent all websites from resolving. Try setting it to “Automatic” or turning it off temporarily, then test again.
4. Check your browser and proxy mode too
Sometimes v2rayNG connects successfully, but your browser environment affects whether websites load. Try testing with Chrome, Edge, or your system browser, and clear the cache for the affected website. If a site won’t open in just one browser, the node may not be the problem.
Also make sure the icon in the lower-right corner of the v2rayNG home screen indicates that the app is running, and check the routing mode. If you’re a typical user, try global proxy mode first. If websites load in global mode but not in split-tunneling mode, your rules or routing configuration may need updating. Once testing is complete, switch back to a mode such as bypassing addresses in mainland China if needed.
5. Quick troubleshooting checklist if you still can’t connect
- Update your subscription and test all nodes again.
- Switch networks to rule out restrictions on Wi-Fi, campus networks, or mobile networks.
- Restore the default DNS settings and turn off any problematic Private DNS.
- Try another browser, clear its cache, and try again.
- Update v2rayNG to a newer version to avoid incompatibility between older cores and newer protocol settings.
In short, if v2rayNG won’t connect, don’t focus only on the node. Check in this order: whether the node is working, your network and IP environment, DNS, your browser, and the client version. This will usually help you pinpoint the problem quickly. If you’re using free nodes, it’s normal for them to stop working occasionally. Update your subscription or switch nodes, then test again.