This article addresses the common question, “What should I do if v2rayNG won’t connect?” It’s for beginners who can’t get online after importing a V2Ray/VLESS node, whose connection tests keep failing, or who see timeouts. The checks below go from simple to more involved. You don’t need to understand how the protocols work—just follow the steps.
1. First, check whether the problem is your local network
Many connection failures aren’t caused by a faulty node. Your phone’s network may be unstable, DNS may be having issues, or your local network may be restricting connections. Start with these basic checks:
- Close v2rayNG and open a browser to visit a domestic website. Make sure your regular internet connection works.
- Switch between Wi-Fi and mobile data and test again. Some campus and workplace networks restrict proxy connections.
- Turn off Battery Saver and Data Saver to prevent your system from restricting v2rayNG in the background.
- If you’re using public Wi-Fi, check whether you need to sign in through a web page.
If the connection works over mobile data, the current Wi-Fi network is probably restricted; the client configuration may be fine.
2. Check that the node was imported correctly
Open v2rayNG, long-press the current node, and select “Edit configuration.” Check that fields such as the address, port, user ID, transport, TLS, and security type aren’t blank or garbled. If you imported the node using a subscription link, tap the menu in the top-right corner and select Update subscription to avoid using an outdated cached configuration.
A common beginner mistake is copying only part of a link or accidentally including the accompanying instructions. It’s best to use “Import from clipboard” or “Scan QR code.” For free nodes provided on this site, we also recommend importing them via subscription to avoid errors from entering details manually.
3. Use the built-in tests to pinpoint the issue
In the v2rayNG node list, tap “Test all configurations for connectivity” or test the latency. Note that a failed latency test doesn’t necessarily mean a node won’t work. However, if the connectivity test keeps timing out, the node is usually unreachable, the network is blocking the connection, or the configuration doesn’t match.
- One node fails: Try other nodes in the same subscription.
- All nodes fail: First check your local network, whether the subscription has expired, and whether your system clock is correct.
- Some apps work, but your browser doesn’t: Check whether per-app proxying or routing rules are enabled.
An incorrect system time can also cause TLS connection issues, so we recommend enabling “Set time automatically.”
4. Check common v2rayNG settings
After tapping the connect button in the lower-right corner, a VPN icon should appear in the status bar. If it doesn’t, the system may not have granted VPN permission. Try connecting again and approve the permission request. Also check “Routing settings.” If you’re new to the app, start with Global or a common mode that bypasses LAN/domestic addresses, and avoid changing complex rules without a reason.
If you’ve imported a lot of nodes, delete any that are clearly inactive and keep only the node you’re testing. If needed, clear the app cache or update to a newer version of v2rayNG. Older versions may not support some newer transport settings, so the configuration may look correct but still fail to connect.
5. What to do if you still can’t connect
Run through these final checks in order: restart your phone; switch networks; update the subscription; try another node; update the client; check the system clock; and close any other VPN, accelerator, or firewall apps. Android phones can usually run only one VPN at a time, so another proxy app running in the background may cause a conflict.
In short, if v2rayNG fails to connect, don’t rush to reinstall it. Check the network, node availability, client permissions, routing rules, and version compatibility one by one. Most beginner issues can be identified in the first few steps. If all nodes fail on different networks, consider switching subscription providers or waiting for the nodes to come back online.