This article addresses the common question, “What should I do if v2rayNG won’t connect?” It walks through a checklist covering your phone’s network, node details, subscription updates, system permissions, and log errors to help you quickly determine whether the issue lies with the client settings, an unavailable node, or restrictions on your current network.
1. Check your network and basic settings first
Connection failures are often caused not by v2rayNG itself, but by network conditions, incorrect time settings, or missing permissions. Before reinstalling the app, work through these checks in order.
- Switch networks: Switch between Wi-Fi and mobile data. Some public Wi-Fi networks restrict proxy connections.
- Check your phone’s time: An incorrect system time or time zone can cause TLS handshake failures. We recommend enabling “Set time automatically.”
- Close other VPN apps: Only one VPN app can run reliably at a time. First exit any speed boosters, VPN-based ad blockers, or corporate VPN apps.
- Check system permissions: When you connect for the first time, allow v2rayNG to create a VPN connection. Otherwise, it may not start.
- Test a regular website: If you can’t open domestic websites without a proxy either, troubleshoot your phone’s network first.
Once you’ve completed these steps, tap the connect button in the bottom-right corner of v2rayNG to test the connection. If it still fails, check your nodes and subscription.
2. Check whether your node is working
The most common reasons v2rayNG won’t connect are an expired node, a blocked address, or incorrect port or protocol settings. Long-press the current node and choose Edit or View configuration. Pay particular attention to the following:
- Protocol type: VLESS, VMess, Trojan, and other protocols are not interchangeable. If the wrong type was detected during import, the connection will fail.
- Address and port: An incorrect domain, IP address, or port will cause a timeout.
- UUID/password: Even an extra space or a single missing character will prevent authentication.
- TLS and transport settings: TLS, the WebSocket path, Host, and SNI must match the settings provided for the node.
If you’re using free nodes provided on this site, import them by copying the complete share link or subscription URL rather than entering the details manually. This helps avoid typos. Free nodes may become unavailable or congested, so if one fails, try another node in the same subscription.
3. How to refresh a subscription reliably
If you imported nodes using a subscription URL, the list may still be visible even though the nodes have been updated. Follow these steps:
- Open v2rayNG, tap “+” in the top-right corner, and make sure there are no extra spaces in the subscription URL.
- Open the subscription group and select “Update subscription.”
- After the update, don’t test just one node. Try switching between two or three nodes.
- Long-press a node and select “Test real connection” or check the latency. Latency alone doesn’t guarantee that a node will work, but if every test fails, there may be an issue with the subscription or your network.
If you get an error while updating the subscription, first check whether the subscription URL opens in a browser. If it doesn’t, the URL may have expired or your current network may be blocking it.
4. Use the logs to identify the cause of the failure
The v2rayNG logs are more useful than the pop-up message. Open the menu in the top-left corner and select Logs or Connection logs. Common messages can be interpreted as follows: timeout usually means the node is unreachable, the port is blocked, or the network is restricted; failed to resolve usually indicates a DNS lookup failure, so try another network or enable Private DNS in your system settings; certificate-related errors are often caused by an incorrect device time or mismatched SNI/TLS settings; authentication failed usually means the UUID, password, or protocol parameters are incorrect.
When troubleshooting, change just one thing at a time: switch networks first, then try another node, update the subscription, and only consider reinstalling the client as a last resort. This makes it easier to pinpoint the cause and prevents unnecessary changes from making things more confusing.
5. What to do if you still can’t connect
If all nodes fail, update v2rayNG to the latest version, then delete the old configurations and import them again. Before importing, make sure the links come from a reliable source, and avoid using QR codes that may have been cropped or links that messaging apps have wrapped onto multiple lines. If only one node fails, it’s probably unavailable or temporarily down, so simply switch to another one.
In summary, if v2rayNG won’t connect, troubleshoot in this order: “network → permissions and time → node settings → subscription update → log errors.” This usually helps you find the cause. Instead of reinstalling the app over and over, a methodical checklist is more effective.