This article addresses the common question, “What should I do if v2rayNG won’t connect?”: when you import nodes but can’t access the internet, it keeps showing “connecting,” speed tests fail, or web pages time out, you can go through the checklist below item by item. First rule out problems with your phone environment, permissions, time settings, subscriptions, and the nodes themselves, then decide whether you need to switch nodes.
1. Check your phone’s login environment before connecting
Many connection failures are not caused by the client itself, but because the basic environment does not meet the requirements. It is recommended to confirm the following first:
- System time is correct: Go to your phone settings and enable “Set time/time zone automatically.” Excessive time deviation can cause TLS verification to fail.
- Network is available: First turn off v2rayNG, then use your browser to open domestic websites and confirm that the Wi-Fi or mobile data itself can access the internet.
- Permissions are allowed: When launching v2rayNG for the first time, it will request VPN connection permission, and you must tap “OK”; on some phones you must also allow background activity.
- Do not run multiple proxies/VPNs at the same time: If other accelerators, ad-filtering VPNs, or system proxy tools are running simultaneously, they may conflict with each other.
- Disable battery restrictions: In app management, set v2rayNG to “Unrestricted” or allow background activity to prevent disconnection after the screen is locked.
2. Check your v2rayNG configuration step by step
- Open v2rayNG and confirm that a node is selected; there should be a highlight or check mark on the left side of the node.
- Tap the menu in the upper right corner and choose “Test all configurations with real connection” or a similar test option; if all tests fail, first suspect an expired subscription, invalid nodes, or local network restrictions.
- Go to the node edit page and check whether the address, port, user ID, encryption method, transport protocol, TLS, SNI, and other fields are empty or were modified by mistake. Ordinary users are not advised to manually change parameters.
- If you are using a subscription, tap “Update subscription” and test again. When copying the subscription link, do not include spaces, line breaks, or extra characters.
- Try switching between 2–3 different nodes instead of repeatedly reconnecting to just one node.
If you are using the free nodes provided by this site, it is recommended to regularly copy the latest subscription or node information again. Free nodes may become unavailable due to load, routing, or validity period changes, which is normal.
3. Common errors and corresponding fixes
If the status bar shows connected but web pages will not open, first check the routing mode. You can try using “Global Proxy” in settings for testing; if global mode works but bypass mode does not, the routing rules may not match. If you see messages such as TLS, handshake, or timeout, they are generally related to node parameters, time settings, SNI, or line blocking.
When you encounter “speed test failed,” it does not necessarily mean the node is completely unusable, because some test addresses may be blocked. A more reliable method is to connect first, then open the target website in your browser while also checking the v2rayNG logs. If timeout appears continuously in the logs, you can switch networks, for example from Wi-Fi to mobile data.
4. Final checklist if it still won’t connect
- Restart your phone and try connecting again to clear the system’s temporary network state.
- Update v2rayNG to a newer version to avoid incompatibility between older versions and newer configurations.
- Delete old nodes and re-import the subscription or QR code.
- Switch nodes or subscription sources to determine whether a single node has failed.
- Test under different networks to confirm that the issue is not caused by restrictions from your current carrier, campus network, or company network.
Summary: When v2rayNG won’t connect, do not start by repeatedly uninstalling it. Troubleshoot in the order of “phone environment → permissions and time → subscription update → node testing → routing mode → switch network,” and you can usually locate the problem quickly. If multiple nodes fail under multiple networks, then consider whether the client version or the subscription itself is abnormal.