This article addresses the common question, “What should I do if v2rayNG won’t connect?” Follow the checklist below to check your phone’s network, node status, subscription import, system permissions, and error logs. This can help you quickly determine whether the issue is with the client settings, an inactive node, or restrictions on your current network.
1. Check your phone’s network environment first
Many connection failures aren’t caused by v2rayNG itself, but by an unstable network on your phone. Start with these basic checks:
- Switch networks: Switch between Wi-Fi and mobile data to rule out network blocking or DNS issues.
- Turn off other proxies/VPNs: Use only one VPN connection at a time—v2rayNG—to avoid conflicts.
- Check your system time: An incorrect time or time zone can cause TLS handshakes to fail.
- Make sure VPN access is authorized: When connecting for the first time, allow the system to create a VPN connection, or it won’t work.
- Disable battery restrictions: Some Android systems restrict background network access. Add v2rayNG to the battery optimization whitelist.
2. Check whether the node or subscription is working
If your network environment is fine, check the node next. Free nodes often stop working because they expire, become congested, get blocked, or have their configurations changed. This site also provides free node information that you can import, but you’ll need to test it in the client to confirm whether it works.
- Open v2rayNG, long-press the current node, and select “Test current server real connectivity” or a similar option.
- If the latency test times out, try another node in the same subscription.
- If all nodes fail, open the subscription settings and tap Update subscription.
- If it still fails after updating, delete the old nodes and re-import them using the subscription link or node link.
Note: Don’t manually change parameters during import, especially the address, port, UUID, encryption method, transport protocol, or SNI. Even a single incorrect character can prevent the connection from working.
3. Check the v2rayNG client settings
A green connection button in v2rayNG doesn’t necessarily mean you can access websites. You also need to check the routing and proxy mode. For most users, the default configuration is best. When troubleshooting, focus on these settings:
- Routing mode: Prefer “Bypass LAN and mainland China addresses” or the default rules. If you’re unsure, don’t change the global rules.
- Local DNS: If websites won’t load, try changing your system DNS or restoring the default DNS settings in v2rayNG.
- Allow connections from LAN: This usually isn’t needed for personal use on a phone. Leaving it off helps avoid extra issues.
- Core version: Update the Xray/V2Ray core in the app settings. Older versions may not support newer protocol parameters.
4. Use the logs to identify common errors
Check the logs from the menu in the upper-right corner of v2rayNG to identify the cause more quickly. Common errors include:
- timeout, i/o timeout: Usually means the node is unreachable, the network is blocking the connection, or the current route is congested.
- connection refused: The server port is unavailable. You’ll usually need to switch to another node.
- handshake failed, TLS error: Often caused by an incorrect SNI, certificate, system time, or node parameter.
- no such host: DNS lookup failed. Try switching networks or checking your DNS settings.
If the same error keeps appearing in the logs, don’t keep reconnecting indefinitely. A more effective approach is to switch nodes, update the subscription, and change networks to test each possibility.
5. Recommended troubleshooting order
The quickest order is: toggle airplane mode, then switch between Wi-Fi and mobile data; test the current node; if it fails, update the subscription; if it still fails, try a different group of nodes; and only then reinstall the client. Back up your subscription link before reinstalling to avoid losing your configuration.
In summary, v2rayNG connection problems usually have one of three causes: a network issue, an inactive node, or incompatible client settings. Following this checklist should help you identify most problems. If only one app won’t open, also check whether it’s set to use the proxy and whether the system is restricting its network access.