This article explains what to do when v2rayNG won’t connect, and is intended for users trying V2Ray/VLESS nodes for the first time. Follow these steps in order: first make sure your phone’s network is working, then check your nodes and subscription, and finally review the client settings and system restrictions. This can save you from repeatedly reinstalling the app as a first resort.
1. Check whether the problem is with your local network
Many connection failures aren’t caused by a faulty node, but by an unstable Wi-Fi or mobile network, or DNS issues. Start with a simple check: close v2rayNG and see whether domestic websites open normally. Then switch networks—for example, from Wi-Fi to mobile data, or vice versa—and try again.
- Open a browser and confirm that regular webpages are accessible.
- After switching networks, tap Connect in v2rayNG again.
- If it only fails on a particular Wi-Fi network, the router, campus network, or company network may be restricting proxy connections.
- If it fails on every network, continue by checking the node configuration.
New users should also check their phone’s clock. An incorrect system time can cause TLS handshake failures. Go to your system settings, enable “Set time automatically” and “Set time zone automatically,” then restart v2rayNG and try again.
2. Check whether the node is working and was imported correctly
If you’re using a subscription link, update the subscription from the menu in the top-right corner of v2rayNG. Don’t assume all nodes will work just because the update succeeded. Free nodes may expire, become congested, or be temporarily restricted, so try 2–3 different nodes. This site also curates free node resources, but availability may vary depending on your network environment.
- Long-press a node and make sure its address, port, UUID, and transport protocol are all present.
- For VLESS/Reality, TLS, WebSocket, and similar configurations, the security type and path must match the node information.
- Don’t import a Clash subscription directly as a v2rayNG node. It will fail if the format is incompatible.
- When copying a node link, make sure you don’t leave out the prefix: vmess://, vless://, or trojan://.
After importing, use v2rayNG’s test function to check the latency. Note that a successful latency test doesn’t guarantee the node will work. A node may respond to the test but still be unable to load webpages, so verify it by visiting a website.
3. Check the v2rayNG client settings
Open the v2rayNG settings. Most users should leave the defaults as they are. Pay particular attention to the “Routing mode” setting in case it was changed accidentally. For everyday use, you can choose the common mode that bypasses the proxy for LAN and mainland China addresses. If the rules seem to be causing problems, temporarily switch to global mode to see whether routing rules are preventing websites from opening.
You should see a VPN icon at the top of your phone’s screen when connected. If it doesn’t appear, the local VPN permission may not have been set up correctly. Disconnect and try again, then allow v2rayNG to create a VPN connection when prompted by the system. Some security apps and battery-saving modes can block background network access, so add v2rayNG to the battery optimization whitelist.
4. Diagnose the problem from the error message
If the connection still fails, open the v2rayNG logs and look for keywords. A timeout usually means your network can’t reach the node or the node is unavailable. “TLS handshake failed” is often caused by an incorrect system time or mismatched SNI/security settings. “Connection refused” may mean the port is closed or the node is no longer working.
Try these steps in order: switch networks, switch nodes, update the subscription, check the system time, and reinstall the client. Reinstallation should be a last resort, since many issues are caused by the node or network and won’t be fixed by reinstalling. If multiple nodes fail on multiple networks, consider updating to the latest version of v2rayNG or testing with another client, such as Clash or sing-box.
In summary, if v2rayNG won’t connect, don’t keep trying the same node over and over. Check your network, node details, client permissions, and log errors one by one to quickly identify the cause. Keeping your subscription up to date, using correctly formatted nodes, and avoiding mixing configurations from different clients are the safest practices for new users.