This guide addresses the question “What should I do if v2rayNG won’t connect?” Whether you can’t get online after importing a free node or subscription link, or after manually adding a VLESS/VMess node, work through the checklist below to quickly determine whether the problem is your network, an inactive node, a configuration error, or a system permission issue.
1. First, check your basic connection environment
Many connection failures aren’t caused by v2rayNG itself, but by the current network or system environment. Start with these checks:
- Switch networks: Toggle between Wi-Fi and mobile data. Some campus and corporate networks restrict proxy connections.
- Check your device’s clock: Go to “Date & time” and enable automatic settings. A large time discrepancy can cause TLS handshakes to fail.
- Disable battery restrictions: Allow v2rayNG to run in the background in your system settings so it isn’t killed as soon as you connect.
- Check VPN permissions: The first time you connect, you’ll be prompted to authorize the VPN. Tap “OK” to establish the local proxy.
- Don’t run multiple proxies at once: Close other VPNs, accelerators, and packet capture tools to prevent port conflicts.
2. Check whether the node and subscription are working
If your environment is fine, check the node next. Free nodes can change frequently, so it’s common for them to become unavailable. Here’s how to troubleshoot:
- Open v2rayNG, long-press the current node, and select “Test current service connection” or a similar test option.
- If the test times out or fails, try another node from the same subscription.
- If all nodes fail, tap the menu in the upper-right corner and update the subscription. If that still doesn’t work, the subscription link may have expired.
- For manually added nodes, verify that the address, port, UUID, encryption method, transport protocol, TLS, SNI, and other settings are all correct.
We compile free nodes that you can import, but the stability of free nodes depends on the connection and the number of users. Keep several backup nodes instead of relying on a single connection.
3. Common v2rayNG configuration errors
If the node passes the connection test but your browser can’t open websites, check the local settings. Open the left-side menu or settings page in v2rayNG and review the following:
- For routing mode, start with “Bypass LAN and mainland China addresses” or “Global.” If you’re unsure, use Global for testing.
- If per-app proxying is enabled, make sure your browser, Telegram, YouTube, and other apps are selected.
- For local DNS, try enabling “Remote DNS” or switching to the system’s default DNS to avoid domain resolution failures.
- If only one website is inaccessible, try another browser or clear the DNS cache before deleting all your settings.
Also, Clash and sing-box subscriptions can’t be imported directly as v2rayNG subscriptions. v2rayNG generally requires a subscription link in a compatible V2Ray format. An incompatible format may result in an empty import or connection problems.
4. Quickly identify the cause based on the symptoms
The error message can help pinpoint the problem: “timeout” usually means the node is blocked, the network is restricted, or the server is unreachable; “TLS handshake failed” commonly points to an incorrect device clock, mismatched SNI, or incorrect TLS settings; if you can connect but can’t open websites, the issue is usually DNS, routing, or per-app proxy settings; if the connection drops as soon as you tap the connect button, check VPN permissions and background restrictions first.
In practice, try switching networks first, then switching nodes, then updating the subscription, and reinstalling the client only as a last resort. Before reinstalling, export a backup of your current settings to avoid losing your nodes. If “v2rayNG won’t connect,” don’t keep tapping the connect button. Work through the checklist to find the cause more quickly.