This article addresses the issue of “What to do when v2rayNG won’t connect”: If you’ve imported a V2Ray/VLESS/VMess node but your phone keeps showing a connection failure—or connects but can’t open web pages—check the items below one by one. This will usually help you quickly determine whether the cause is the node, subscription, network environment, or client settings.
1. Check your network and sign-in status
Connection failures often aren’t caused by a faulty app; your current network environment may simply be unsuitable. Start with these basic checks:
- Make sure your phone’s date, time, and time zone are set to update automatically. A significant time discrepancy can cause a TLS handshake to fail.
- Try switching networks: switch from Wi-Fi to mobile data, or vice versa.
- Turn off other VPNs, proxies, and accelerators to prevent multiple proxy apps from competing for the system VPN connection.
- Make sure your system allows v2rayNG to access the network and run in the background. Some Android systems restrict background activity to save battery.
- If you’re using public Wi-Fi, open a regular webpage first to check whether you need to sign in to the network.
If switching networks fixes the issue immediately, your original network may be heavily restricted or experiencing DNS issues. If the problem persists on every network, continue by checking the node and configuration.
2. Check that the node, subscription, and configuration are valid
v2rayNG relies on complete and accurate node parameters, including the address, port, user ID, transport protocol, TLS, and SNI. You don’t need to understand every parameter, but make sure the source is trustworthy and the configuration hasn’t been corrupted.
- Open v2rayNG, long-press the current node, and select “Test current configuration” or a similar test option.
- If the test times out or shows “failed” or “connection refused,” try another node in the same subscription first.
- Tap the menu in the top-right corner and update the subscription to avoid using outdated nodes.
- If you imported a link manually, copy the complete vmess://, vless://, or trojan:// link again, making sure no characters are missing.
- Check that you haven’t selected an empty or outdated configuration, and make sure you’re connecting to the node you just updated.
This site provides a selection of free nodes for testing, but their availability may vary. We recommend keeping several backup nodes rather than relying on a single configuration.
3. Troubleshoot common client settings
Incorrect settings in v2rayNG can also result in being “connected but unable to access the internet.” Try these adjustments:
- Start with the “Bypass LAN and mainland China addresses” routing mode instead of using complex custom rules.
- Try enabling remote DNS, or restore the default DNS settings and reconnect.
- If “Per-app proxy” is enabled, make sure apps such as your browser, Telegram, and YouTube are selected.
- Update v2rayNG to a newer version. Older cores may not support parameters used by some newer protocols.
After making changes, don’t rely solely on the VPN icon at the top of your screen. Open a website that requires a proxy to test the connection directly. The VPN icon only indicates that the system proxy connection is established; it doesn’t guarantee that the node is working.
4. How to identify the cause if you still can’t connect
You can often narrow down the cause based on what you’re seeing: If none of the nodes pass the connection test, the issue is likely with your local network, DNS, system permissions, or client version. If only a few nodes fail, they’re probably unavailable or their parameters have changed. If some websites open but load slowly, the connection may be congested or the routing rules may not be suitable.
We recommend troubleshooting in this order: “Update subscription → Switch networks → Try another node → Restart the client → Update v2rayNG.” Change only one setting at a time so you can tell which step resolves the issue. If you see an error message, look for keywords such as timeout, TLS handshake failed, and connection refused, then check your network, TLS/SNI settings, or node status accordingly.