This article addresses the practical question “What should I do if v2rayNG won’t connect?” No complicated settings or self-hosted servers are involved—we’ll use low-risk troubleshooting steps to help you determine whether the issue is caused by a node, the configuration, your phone’s network, or the current network environment.
1. First, rule out basic settings issues
When v2rayNG fails to connect, the software itself often isn’t the problem. The subscription may not have been updated, the node may be unavailable, the system proxy may not be enabled, or your phone’s clock may be incorrect. Check the following in order before repeatedly reinstalling the app.
- Open v2rayNG and make sure a node is selected, rather than an empty or outdated configuration.
- Tap the menu in the upper-right corner, select “Update subscription” or “Update subscription group,” and wait for the update to finish before testing again.
- Try 2–3 different nodes. Don’t assume they’re all unavailable based on a single node.
- Check that your phone’s system time is set to update automatically. An incorrect clock can cause TLS handshakes to fail.
- Make sure v2rayNG has VPN permission. When connected, you should see a key or VPN icon in the status bar.
If you’re using the free nodes provided on this site, try copying the subscription URL again or re-importing the configuration. Free nodes may be temporarily unavailable due to maintenance, expiration, or congestion.
2. Check the logs for clues
Tap Logs at the bottom of the v2rayNG home screen to view connection errors. You don’t need to understand every detail—just look for a few common keywords.
- timeout: The node may not be responding, the connection may be blocked, or your current network may be unreliable.
- connection refused: The node’s port may be unavailable. Try another node.
- TLS, handshake, or certificate: First check your system time, then update the subscription.
- no route or network unreachable: Your phone may not be connected to the internet, or your local network may be restricting access.
Change only one thing at a time while troubleshooting. Start by switching nodes without changing any advanced client settings. If several nodes fail, try a different network. This makes it easier to identify the cause.
3. When to switch networks
Switching networks doesn’t have to involve anything complicated. You can start by switching between Wi-Fi and mobile data. Consider trying a different network if:
- All the same nodes fail on Wi-Fi but connect when you switch to mobile data.
- The logs frequently show timeout errors, and web pages or apps are also slow or unreliable.
- You can’t connect on a company, campus, hotel, or public Wi-Fi network, but it works at home or over mobile data.
- The app shows that it’s connected, but no web pages load, suggesting a DNS issue or network policy restriction.
A low-risk approach is to disconnect v2rayNG, turn off Wi-Fi, switch to 4G/5G, and then reconnect. If that works, your Wi-Fi network is likely imposing restrictions. The reverse applies too: if mobile data doesn’t work, try your home Wi-Fi.
4. Recommended low-risk troubleshooting order
If v2rayNG won’t connect, try these steps in order: update the subscription → switch nodes → restart v2rayNG → switch networks → restart your phone. Avoid clearing all your configurations or changing settings such as the transport protocol, TLS, or SNI right away. Imported nodes usually already include the necessary settings, and changing them at random can make it even harder to connect.
If none of the free nodes work, wait a while and try getting them again, or test a different subscription source. If only one app won’t open, check whether a routing mode such as “Bypass LAN and mainland China addresses” is enabled. In short, start with simple, safe, reversible troubleshooting steps—you can usually identify the cause this way.