This article addresses the common question, “What should I do if v2rayNG won’t connect?” It focuses on situations where multiple people or a team share nodes—for example, when some users can connect but others can’t, or the connection drops whenever they join the office network. Follow the steps below to check your account, client, network environment, and node stability.
1. First, rule out basic configuration issues
If v2rayNG fails to connect, don’t immediately uninstall and reinstall it. First, check that the imported configuration is correct. In teams, a common problem is that some people copy an expired link while others import an old QR code, leaving them with inconsistent configurations.
- Open v2rayNG and go to the node list. Make sure the selected node isn’t grayed out, unnamed, or an outdated duplicate.
- If you use a subscription, tap the menu in the upper-right corner, select “Update subscription,” and then select a node again.
- Check that your phone’s clock is accurate. We recommend enabling the system’s “Set time automatically” option, as an incorrect time can cause TLS handshakes to fail.
- Test both 4G/5G and Wi-Fi to determine whether the current network is restricting the connection.
- In “Routing settings,” test with the default or global mode to make sure routing rules aren’t blocking the connection.
2. For team use, pay close attention to account stability
If multiple people use the same account and subscription simultaneously over an extended period, connections may become unstable, time out frequently, or fail on some devices. Account stability mainly depends on whether the number of devices, login locations, network egress points, and usage patterns are unusual.
We recommend that teams follow these guidelines: Don’t repeatedly share the same temporary node among multiple users; avoid frequent, rapid switching between cities and carriers; and don’t run high-traffic tasks on multiple devices for long periods at the same time. The free nodes on this site are suitable for testing connectivity and temporary use. For team work, prepare multiple backup nodes to avoid a single point of failure.
3. Quickly identify the cause based on the error
- Connection timed out: First switch networks or nodes. The route may be unreachable, or the current Wi-Fi network may restrict proxy connections.
- TLS handshake failed: Check the system time, make sure the node address hasn’t been changed, and verify that the SNI and transport parameters are complete.
- Web pages won’t open after connecting: Switch to global mode, check your DNS settings, or disable other VPNs or accelerators that may be interfering.
- Only one app isn’t working: Check per-app proxy settings and make sure the app hasn’t been excluded.
4. Recommended steps for stable use
When troubleshooting as a team, designate one person to manage the subscription source and have everyone else update the subscription without manually changing node parameters. If there’s a problem, first test two devices on the same network, then test the same device on different networks. This helps you quickly determine whether the issue is with the node, account usage, or local network.
If no one can connect, the node is probably unavailable or the subscription has expired. If only some users are affected, the cause is usually the client version, phone permissions, network environment, or local configuration. As a last resort, update v2rayNG to the latest version, remove old nodes, and re-import the subscription. Avoid changing multiple settings at once while troubleshooting. Record the results at each step so you can identify the cause more quickly.