This article addresses the common question, “What should I do if v2rayNG won’t connect?” Troubleshoot in order, checking your nodes, subscription, network environment, client settings, and whether frequent switching has triggered security measures. Start with low-cost fixes to restore your connection and improve stability.
1. First, determine whether the problem is with the node or your device
When v2rayNG fails to connect, don’t immediately delete and reinstall the app. Start with a few basic checks: if the same node fails on different networks, it’s probably offline. If none of your nodes work, the issue may be your device’s network, DNS, clock, or client configuration. The free nodes provided on this site can be useful for temporary testing, but they can be unreliable, so treat them as a troubleshooting aid rather than your only long-term option.
- Open v2rayNG and make sure the proxy switch in the upper-right corner is turned on.
- Tap the current node and choose “Test all configurations” or run a latency test.
- Test once on mobile data and once on Wi-Fi to rule out carrier or router issues.
- Check that your phone’s clock is set to update automatically. An incorrect time can cause TLS handshake failures.
- Update v2rayNG to a recent version. Older cores may not be compatible with some VLESS, Reality, or TLS configurations.
2. Avoid common subscription and node import errors
Many connection failures aren’t caused by a faulty node, but by an outdated subscription, incomplete copied content, or a protocol mismatch. Open your subscription settings and update the subscription manually. If parsing fails, check whether the subscription link contains spaces, has expired, or requires a proxy to access. When importing vmess, vless, or trojan links manually, use “Import from clipboard” rather than changing fields such as the port, UUID, or transport protocol yourself.
If the node name appears after import but it still won’t connect, check three things: whether the address was accidentally deleted, whether the port is a number, and whether the transport layer matches the node’s instructions. With configurations such as VLESS + Reality, WebSocket, and gRPC in particular, changing the SNI, Host, or Path without a good reason can easily cause connection failures.
3. Avoid usage habits that may repeatedly trigger security checks
Frequent node switching, running lots of speed tests in a short time, or using the same account to connect frequently from multiple devices at once can all look suspicious to the node server or websites you visit. Most users don’t need to chase the lowest latency all the time; a stable connection to the websites you use regularly is more important.
- Don’t run dozens of speed tests in a row. Testing 3–5 nodes is enough.
- When possible, use the same node on only one device at a time.
- If a connection fails, wait a few seconds before reconnecting instead of repeatedly connecting and disconnecting in quick succession.
- Prioritize nodes with stable latency and low packet loss; there’s no need to constantly switch to new ones.
- When visiting sites that require you to sign in, avoid frequently switching between regions to reduce repeated account security checks.
4. What to try if you still can’t connect
If all your nodes fail, try changing the routing mode in v2rayNG’s settings to “Bypass LAN and mainland addresses.” You can also leave DNS at its default setting or enable remote DNS, then test again. If that still doesn’t work, clear the app cache, reimport the subscription, and restart your phone’s network connection. If only one app won’t open, it may be connecting directly or using cached network settings. Close it completely and try again.
Finally, keep 2–3 backup nodes or subscriptions from different sources so you’re not dependent on a single one. If v2rayNG won’t connect, troubleshoot in this order: network environment, subscription update, node configuration, client version, and usage frequency. This will usually improve reliability without adding much cost.