This article addresses the common question, “What should I do if v2rayNG won’t connect?” If you import a node and see a timeout or TLS handshake failure, or connect successfully but can’t open webpages, the app itself may not be the problem. The issue could lie with the node, your network, DNS, your IP environment, or your browser’s proxy settings. Follow these troubleshooting steps in order.
1. Check the node and basic v2rayNG settings
Many connection failures are caused by outdated node details, incomplete copying, or an old client version. Start with these basic checks before changing any advanced settings.
- Open v2rayNG, tap “+” in the upper-right corner, and confirm that the node was imported correctly from the clipboard, a QR code, or a subscription.
- Long-press the node and select “Test all configurations” or a similar test option to see whether all nodes time out.
- If only one node fails, try another. If they all fail, continue troubleshooting your device and network.
- Update v2rayNG to a recent version. Older versions may not support some VLESS, Reality, or TLS fingerprint configurations.
- Make sure your phone’s time is set to sync automatically. A significant time difference can cause certificate verification to fail.
If you use a subscription link, try updating the subscription first, then run the test again. This site also lists free nodes that you can use to check whether the client is working. However, free nodes can be unstable, so don’t assume the app is broken based on a single node.
2. Check your IP environment: carrier, Wi-Fi, and mobile data
If v2rayNG keeps showing a timeout, your current network’s outgoing connection may be the cause. The easiest test is to switch networks: try mobile data instead of Wi-Fi, or vice versa. If it works on one network but not the other, the problem is likely with the network you’re using.
- Public Wi-Fi: School, office, and hotel networks may restrict UDP, proxy ports, or unusual TLS connections.
- Home broadband: Router-based DNS hijacking, IPv6 issues, or security settings on your modem may affect the connection.
- Mobile data: Some regions or carriers may have unreliable connections on certain ports. Try a different node protocol or port.
You can also try toggling “Bypass LAN addresses” and “Enable IPv6” in v2rayNG’s settings. If enabling IPv6 causes problems, turn it off and try again.
3. DNS issues: what to do if you connect but can’t open websites
If v2rayNG shows that you’re connected but your browser can’t open webpages, or only some websites are inaccessible, check your DNS settings. DNS translates domain names into IP addresses. If DNS queries are being tampered with or routed incorrectly, the connection may appear successful even though you can’t access websites.
In v2rayNG’s settings, find the routing or DNS options and try the default configuration first. Avoid enabling multiple third-party DNS tools at the same time. If your phone has ad blockers, Private DNS, other VPNs, or firewall apps installed, temporarily disable them. You can also try setting “Private DNS” in Android’s system settings to Off or Automatic.
Another common cause is incorrect routing rules. If you’ve selected “Proxy only blocked sites” but the rule file is outdated, your target website may not be routed through the proxy. Try switching to “Global proxy” as a test. If the site opens with global proxy enabled, the node is working and the problem is with the routing rules.
4. Your browser and apps can also affect access
Sometimes v2rayNG is proxying traffic correctly, but browser cache, proxy extensions, or an app’s built-in DNS can make it seem otherwise. Try testing with different browsers, such as Chrome, Firefox, and your system browser.
- Clear your browser cache and cookies, then try again.
- Disable any proxy settings, private DNS, or acceleration extensions in your browser.
- Check that the key icon is visible at the top of v2rayNG and that security software hasn’t blocked the system VPN permission.
- If only one app isn’t working, check whether it has been excluded from “Per-app proxy” in v2rayNG.
Recommended troubleshooting order: Try a different node, switch networks, check DNS, and then check your browser and per-app proxy settings. This is the quickest way to pinpoint the issue. If none of the nodes work on any network, try reinstalling v2rayNG and importing a subscription or node configuration that you’ve confirmed is valid.