This guide addresses the question “What should I do if v2rayNG won’t connect?” Without changing complex settings or tinkering with the server, it walks you through checks for the app, nodes, subscription, and current network environment in order of risk, helping you quickly determine whether the issue is a software setting, an inactive node, or a network restriction.
1. First, check that v2rayNG is set up correctly
Many connection failures don’t necessarily mean the node is down. The import may be incomplete, your device’s clock may be inaccurate, or the local VPN may not be enabled. Start with these checks:
- Open v2rayNG and make sure a node is selected. A check mark should appear beside it.
- Tap the connect button in the lower-right corner and check whether a VPN icon appears in the status bar.
- Open “Settings” and leave “Routing” on the default setting or set it to bypass LAN/mainland China addresses. Avoid changing advanced settings without a reason.
- Check your phone’s time and time zone. We recommend enabling the system’s “Set time automatically” option. An inaccurate clock can cause a TLS handshake to fail.
- If you imported the configuration from a link, import it again to rule out a missing link or a QR code scanning error.
Once you’ve completed these checks, try visiting a commonly used overseas website in your browser. Don’t rely only on the app’s “Connected” status: successfully establishing a local VPN connection doesn’t mean the node is working.
2. Check whether the node or subscription is inactive
If v2rayNG shows that it’s connected but you still can’t open webpages, first suspect that the node has expired, is blocked, or that the subscription hasn’t been updated. You can run “Test real connection” or “Test latency” on a node from the main screen, but keep in mind that a latency result doesn’t guarantee that you’ll be able to access websites.
- Switch to another node in the same subscription and try loading a webpage again.
- Update the subscription manually: tap the menu in the upper-right corner and select “Update subscription.”
- Delete any old nodes that clearly aren’t working to avoid connecting to them by mistake.
- Try importing a free node provided on this site as a cross-check to determine whether the problem is with the node or your local network.
If nodes from several different sources all fail, check your network environment next. If only one node fails, simply switching to another node will usually solve the problem.
3. When to switch network environments
Switching network environments means moving from your current Wi-Fi to mobile data, or from one Wi-Fi network to another, without changing any sensitive settings. Try this in the following situations:
- All nodes show a timeout, connection reset, or TLS handshake timeout error.
- The same node works on a friend’s phone or on another network, but not on your current network.
- You can’t connect over your workplace, campus, or hotel Wi-Fi, but it works at home or on mobile data.
- Webpages sometimes load after connecting but the connection drops soon afterward, and switching nodes doesn’t help.
Switching networks is a low-risk action and won’t damage your v2rayNG configuration. First, try turning off Wi-Fi and using mobile data. Then try restarting your router or switching to another trusted Wi-Fi network. Don’t install acceleration apps from unknown sources or modify system certificates.
4. Safe steps if you still can’t connect
If the problem persists after these checks, try the following in order: restart v2rayNG, restart your phone, update v2rayNG to a newer version, then delete and reimport your subscription. If you see an error, note the key terms, such as timeout, connection refused, or failed to detect internet connection, so you can use them to guide further troubleshooting.
Finally, don’t share subscription links or screenshots of your nodes in public groups, and don’t enable advanced options unless you understand them. Troubleshooting in the order of “client settings—nodes and subscription—network environment” will usually help you pinpoint why v2rayNG won’t connect.