This article addresses the common question, “What should I do if v2rayNG won’t connect?” Whether you’ve just imported a free node, a subscription stopped working after an update, or the app says it’s connected but webpages won’t load, work through the checklist below to quickly identify whether the problem is with the node, your network, the configuration, or your phone.
1. Check your phone and network
Many connection failures aren’t caused by v2rayNG itself; your current network may simply be unsuitable. When troubleshooting, try turning v2rayNG off and back on first to rule out any lingering connection issues.
- Make sure your phone’s date, time, and time zone are correct. A significant time difference can cause TLS connection failures.
- Try switching networks: switch from Wi-Fi to mobile data, or from mobile data to Wi-Fi.
- Turn off battery saver and data saver modes to prevent the system from restricting the VPN in the background.
- Check whether other VPNs, network accelerators, or ad blockers are running. For testing, leave only v2rayNG enabled.
- Make sure your browser isn’t using an incorrectly configured proxy extension. Mobile browsers generally don’t need any additional settings.
2. Check whether the node is working
If only one node fails to connect, the node itself is the most likely cause. Free nodes provided by this site can also be affected by route fluctuations, regional network conditions, and node expiration, so it’s a good idea to keep several nodes available.
- In v2rayNG, long-press the current node and select a latency test or a real connection test.
- If the latency is -1, the test times out, or the real connection test fails, try another node.
- If all nodes fail, tap the subscription update button in the top-right corner and check that the subscription has refreshed.
- If the connection still fails after updating, delete the old nodes and re-import the subscription link or individual node.
Note: A successful latency test doesn’t guarantee that webpages will load properly. The real connection test is a more useful indicator.
3. Check that the imported configuration is complete
v2rayNG supports protocols such as VMess, VLESS, Trojan, and Shadowsocks. If you can’t connect, avoid changing parameters at random, especially fields such as transport, TLS, SNI, and path. If you imported a node by copying its link, make sure the link wasn’t broken across lines, altered with spaces, or truncated by a messaging app.
Common errors include a missing address, incorrect port, incomplete UUID, mismatched TLS setting, incorrect WebSocket path, or a missing Reality public key or shortId. If you encounter one of these issues, the simplest solution is to copy the complete node link again, delete the old configuration in v2rayNG, and import it again.
4. What if it connects but webpages won’t load?
If v2rayNG shows that it’s connected but Google, YouTube, or Telegram still won’t open, try the following:
- In v2rayNG’s settings, check that “Bypass LAN and mainland addresses” or the routing rules are configured correctly. Make sure you haven’t accidentally selected direct connection for all traffic.
- Try switching the routing mode, for example, from per-app proxying to global proxying.
- Check whether proxying is enabled for only some apps. If necessary, turn off per-app proxying.
- Clear your browser’s DNS cache, or restart your phone before reconnecting.
- Try nodes using different protocols or from different regions to rule out a problem with a particular route.
5. Quickly identify the source of the problem
A simple rule of thumb: if one node fails, the node is probably the problem; if all nodes fail on the same Wi-Fi but work on mobile data, the Wi-Fi network is probably restricting the connection; if they fail on every network, the issue may be with the client version, subscription format, or system VPN permissions.
Keep v2rayNG up to date and install it from a trusted source. If your system asks for VPN permission, you must allow it or the VPN tunnel cannot be established. While troubleshooting, avoid changing multiple settings at once; change one setting at a time so you can easily revert it.
In short, if v2rayNG won’t connect, check these four areas: network environment, node availability, configuration completeness, and routing and proxy settings. This will usually help you find the cause. If you still can’t connect, try a different subscription source or test with another client.