This article addresses the common question, “What should I do if v2rayNG won’t connect?” It focuses on low-risk troubleshooting: check the client and node settings first, then see whether switching between Wi-Fi, mobile data, or another network helps. Avoid changing system settings at random right away.
1. Rule out basic settings issues first
When v2rayNG won’t connect, the node may not be completely down. The issue could be an outdated subscription, an incorrect system time, the wrong routing mode, or a temporary network problem. Follow the steps below in order, testing the connection again after each one.
- Open v2rayNG and make sure the correct node is selected. Don’t leave an empty configuration or an old node selected.
- Tap the menu in the top-right corner and select Update subscription. If you’re using our free nodes, refresh the latest links as well.
- Check your phone’s system time and enable “Set time automatically” and “Set time zone automatically.” An incorrect time can cause TLS connection failures.
- Open v2rayNG’s settings and check that options such as “Enable local DNS” and “Bypass mainland addresses” haven’t been changed repeatedly. If you’re unsure, restore the defaults and try again.
- Run a connectivity test instead of relying only on the latency reading. A latency value doesn’t guarantee that websites will load properly.
If several nodes show a latency reading after you update the subscription but websites still won’t open, try testing in a browser’s incognito window first. This can rule out issues caused by browser cache, proxy extensions, or outdated DNS results.
2. When to switch network environments
As part of low-risk troubleshooting, switching network environments is a useful and straightforward step. It doesn’t change your node settings; it simply helps determine whether your current network is interfering with the proxy connection.
- If the same node consistently fails on Wi-Fi but works on mobile data, the issue is likely with the Wi-Fi network, router, or broadband connection.
- If all nodes fail on a particular public Wi-Fi network but work at home, the public network may be restricting the connection.
- If mobile data also fails but a different node works, the original node is probably unavailable or being interfered with. The problem may not be your phone.
- If other devices on the same network also can’t use similar proxy tools, try restarting the router or testing on another network first.
We recommend testing in this order: disconnect v2rayNG, switch to mobile data, reopen v2rayNG, reconnect to a node, and visit a commonly used website. If mobile data works, switch back to Wi-Fi and test again to identify the difference.
3. Troubleshooting nodes and protocols
If you imported a VLESS, VMess, or Trojan node, make sure the link is complete. When copying it manually, don’t leave out fields such as the UUID, port, transport, TLS, or security type. Importing a subscription is usually more reliable than entering the details manually.
If the connection succeeds but you still can’t access the internet, try another node from the same subscription, preferably one updated recently. You can also delete the old subscription and import it again to prevent the client from retaining outdated settings. Avoid installing untrusted “acceleration modules” or modifying system certificates; these actions can be risky.
4. Quick troubleshooting guide
- Only one node fails: Try another node or update the subscription first.
- All nodes fail: Check the system time, subscription, network environment, and v2rayNG settings.
- Wi-Fi fails but mobile data works: Restart the router or try a different DNS or network environment.
- Some apps don’t work after connecting: Check per-app proxy settings, routing rules, and whether the app itself restricts proxy use.
In short, if v2rayNG won’t connect, don’t rush to uninstall the client or make major changes to your settings. Troubleshoot in this order: update the subscription, test the node, switch networks, and restore the default settings. This will usually help you quickly determine whether the problem is with the node, the client, or your current network environment.