This article addresses the common question “What should I do if v2rayNG won’t connect?” and focuses on low-risk troubleshooting: check the client, nodes, and subscription first, then see whether switching between Wi-Fi, mobile data, or another network helps. This avoids making random configuration changes that could make the problem harder to solve.
1. First, rule out basic client settings
If v2rayNG fails to connect, don’t rush to uninstall the app or keep switching nodes. Start with these basic checks in order. They won’t affect your phone’s system settings and are low-risk.
- Check that your phone’s time is correct. We recommend enabling “Set time automatically.” An incorrect time can cause TLS handshake failures.
- Open v2rayNG and check whether the connection is running. Look for the VPN icon in the notification bar.
- Open the details for your current node and make sure the address, port, UUID, transport protocol, TLS, Reality, and other parameters haven’t been accidentally deleted.
- If you use a subscription, tap “Update subscription,” then select a node and try connecting again.
- Close and reopen v2rayNG. If needed, restart your phone and try again.
If you imported free nodes from this site or another source, we recommend updating them via the subscription link rather than copying them manually, which can result in missing parameters. Free nodes may stop working, so a connection failure doesn’t necessarily mean the client is broken.
2. Check whether the node is down or blocked by your network
If the basic checks don’t help, try switching nodes and networks to narrow down the cause. First, try 2–3 different nodes on the same network. If only one node fails, it’s probably temporarily unavailable. If all nodes fail, your current network may be restricted.
- The same node fails on Wi-Fi but works on mobile data: Your Wi-Fi network may restrict proxy connections. This is common on company, school, hotel, and public networks.
- The same node fails on mobile data but works on Wi-Fi: The issue may be related to your carrier’s network, signal quality, DNS, or temporary routing problems.
- It fails on all networks: The subscription may have expired, the nodes may be down, the client may be outdated, or the configuration parameters may not match.
A low-risk first step is to switch networks and test again. We don’t recommend changing your system DNS or proxy port, or installing “repair tools” from unknown sources.
3. When to try a different network
Consider testing on another network if you haven’t completed the login page for a public Wi-Fi network, regular websites load but v2rayNG keeps timing out, multiple nodes show connection errors, or the same subscription works on another device. Try these steps in order: switch from Wi-Fi to mobile data; toggle airplane mode to refresh your mobile connection; if that doesn’t work, test on another Wi-Fi network.
Keep in mind that switching networks is a way to identify the problem, not necessarily a recommendation to use a particular network long-term. If you’re using a company or campus network, follow applicable laws and network policies, and avoid disrupting others or violating your organization’s requirements.
4. Check the logs to pinpoint the cause
v2rayNG’s built-in logs can provide useful clues. Open the app menu and select “Logs” or “Run logs,” then attempt to connect and check the messages. Common entries include timeout, connection refused, TLS handshake failed, and no route to host. timeout is often related to network connectivity or a node being down; TLS handshake failed may indicate an incorrect time, mismatched TLS parameters, or network interference; connection refused usually means the destination port is unavailable.
Finally, keep v2rayNG up to date and refresh your subscription regularly. Replace nodes promptly when they stop working. Troubleshooting in this order—check settings, update the subscription, switch nodes, switch networks, and check the logs—usually helps you locate the problem quickly without unnecessary changes.