This article addresses “What should I do if v2rayNG won’t connect?” and focuses on scenarios where multiple people or a team share a subscription, account, or nodes. Often, the phone itself isn’t the problem. Connection failures are more commonly caused by node status, account restrictions, network conditions, or inconsistent client settings.
1. Determine whether the issue affects one person or the whole team
When using v2rayNG as a team, don’t start by repeatedly uninstalling and reinstalling the app. First, find out how widespread the issue is. If only you can’t connect, the cause is usually your local network, system time, or client settings. If multiple people are affected at the same time, the subscription may have expired, a node may be down, or the account policy may have changed.
- Ask one or two teammates to test the same node.
- Switch networks—for example, from Wi-Fi to mobile data.
- In v2rayNG, tap “Test all configurations for real connection.”
- Check whether the subscription was recently updated and whether multiple people are experiencing issues at the same time.
If the free nodes on this site also fail to connect, try a node in a different region or using a different protocol. Don’t focus your troubleshooting on just one node.
2. Check account and subscription stability
When a team shares a subscription, common issues include an expired subscription link, removed nodes, too many devices connected at once, or server-side account restrictions. v2rayNG is just a client; it can’t fix account-side issues.
- Subscription won’t update: Check that the subscription link is complete, try opening it in a browser, and see whether you need to retrieve a new link.
- Latency is -1 for all nodes: The network may be blocking connections, the subscription’s nodes may no longer be active, or the server may be unreachable.
- Some team members can connect while others can’t: First check device time, DNS, proxy mode, and system network permissions.
- Connected, but there’s no internet access: This may be caused by routing rules, DNS, or an issue with the node’s exit server.
For team use, designate one person to manage the subscription. If everyone imports configurations from different sources, it becomes much harder to identify the cause of an issue.
3. Key settings in the v2rayNG client
Open v2rayNG and long-press the current node. Make sure the address, port, UUID, transport protocol, TLS, SNI, and other details haven’t been changed by mistake. If the node was imported through a subscription, it’s usually best not to edit its parameters manually.
Then open Settings and check the following: Start with the routing mode set to “Bypass LAN and mainland addresses.” Try the client’s default DNS settings. If “Proxy only mode” is enabled or the system restricts background activity to save power, the app may not be able to route network traffic properly.
On Android, also make sure v2rayNG is allowed to run in the background and disable aggressive battery-saving features. Some Android manufacturers’ systems disconnect the VPN when the screen locks, which can make the node seem unstable.
4. Troubleshoot connection failures step by step
- Update the subscription: Open the menu in the top-right corner and select “Update subscription.”
- Try other nodes: Don’t test just one—try at least three different nodes.
- Switch networks: Try Wi-Fi, mobile data, and a hotspot.
- Restart the VPN: Disconnect and reconnect, and restart your phone if needed.
- Check the logs: Look for errors such as timeout, TLS, handshake, and DNS in the v2rayNG logs.
If the logs repeatedly show timeout errors, the network or node is usually unreachable. Authentication, UUID, or TLS handshake errors generally indicate a mismatch in the configuration or subscription details. In that case, re-import the subscription instead of continuing to change individual fields.
5. Tips for more reliable team use
In a team setting, stability comes from consistent management and minimizing variables. Use the same client version, standardize the subscription source, regularly remove inactive nodes, and mark currently available nodes in your group chat. When a problem occurs, note the time, network, node name, and error logs before reporting it to the person maintaining the setup.
In short, don’t rush to reinstall v2rayNG if it won’t connect. First determine whether the issue affects one device or the whole team, then check the subscription, account, nodes, network conditions, and client settings. Troubleshooting in order usually helps you identify the cause quickly.