This guide addresses the common question, “What should I do if v2rayNG won’t connect?” It walks you through troubleshooting in order, from your mobile network and node configuration to subscription updates, system permissions, and client settings—ideal for beginners who are new to V2Ray/VLESS.
1. First determine whether the problem is your network or the node
Often, v2rayNG itself isn’t the problem. The cause may be your current network, an expired node, or incomplete configuration. Start with a few basic comparison tests instead of repeatedly reinstalling the client.
- Close v2rayNG and open a domestic website in your browser to confirm that your phone can access the internet normally.
- Switch between Wi-Fi and mobile data, testing the connection on each.
- Restart your router or toggle airplane mode to make your phone reconnect to the network.
- If the connection fails only on a particular Wi-Fi network, it may be blocking proxy connections. Try a different network.
If domestic websites won’t load either, troubleshoot your local network first. If they work but the proxy doesn’t, continue by checking the node and app settings.
2. Check whether the node is working
v2rayNG relies on node information to connect. An expired or blocked node, or an incorrectly entered address, can all cause connection failures. Open v2rayNG, long-press the current node, and select “Test real connection” or a similar option. If the test times out or fails to connect, try another node.
- Make sure the node protocol is supported by the client, such as VMess, VLESS, or Trojan.
- Check that fields such as the address, port, UUID, transport, TLS, and SNI are present and correct.
- If you use a subscription, tap the menu in the upper-right corner and select Update subscription.
- Free nodes provided on this site can be used for temporary testing, but they may stop working, so keep several alternatives available.
A common beginner mistake is missing part of a node when copying it, or failing to refresh the subscription after importing it from a QR code. Try deleting the failing node and importing it again.
3. Check the v2rayNG client settings
Go to the v2rayNG settings page and make sure “Routing settings” hasn’t been accidentally set to bypass the proxy entirely. Beginners can usually start with the default routing option or bypass LAN and mainland China addresses. Before connecting, also make sure you’ve allowed the VPN permission prompt from Android. Otherwise, the client may appear to start, but your traffic won’t actually be routed through the proxy.
If you’ve changed a lot of advanced options, try restoring the defaults. Settings such as DNS, Mux, fragmentation, and camouflage domain can cause connection failures if they don’t match. Most users should use the complete configuration provided by their node provider rather than changing settings at random.
4. Use error messages to identify the problem
Tap Logs at the bottom or open the logs page from the menu, then check the last few lines for error messages. Common messages can be interpreted as follows:
- timeout: The network may be blocking the connection, the node may be unreachable, or the port may not be responding.
- connection refused: The server port may be closed, which usually means the node is no longer working.
- bad request, TLS handshake failed: Often caused by mismatched TLS, SNI, or transport settings.
- no such host: The domain couldn’t be resolved. Try switching networks or changing DNS.
If the logs aren’t clear, take a screenshot of the relevant error messages and search for those keywords to troubleshoot further.
5. A practical troubleshooting sequence
Try these steps in order: switch networks, switch nodes, update the subscription, restart v2rayNG, and finally restart your phone. If it still doesn’t work, update to the latest version of v2rayNG, or temporarily import the same subscription into another client, such as Clash or sing-box, to compare results.
In summary, v2rayNG connection failures usually come down to one of three causes: an unstable local network, a non-working node, or mismatched settings. Beginners should avoid changing advanced parameters at random. Work through these steps one by one, and you should be able to identify the problem.