This guide addresses problems such as being unable to access the internet after importing a node into v2rayNG and tapping “Connect,” failed latency tests, timeouts, or websites not loading after connecting. The steps below follow the easiest order for beginners: check your phone’s network, node details, client settings, and system restrictions.
1. First check whether the problem is with your phone’s network
Many cases of “v2rayNG won’t connect” are not caused by a faulty client, but by an unstable or restricted network. Before changing your configuration repeatedly, check the following in order:
- Close v2rayNG and use your browser to open a domestic website to confirm that your phone can connect to the internet normally.
- Switch between Wi-Fi and mobile data and test again. Some campus, workplace, and public Wi-Fi networks restrict proxy connections.
- Turn off battery saver and data saver to prevent the system from restricting v2rayNG in the background.
- Make sure your phone’s time is set to sync automatically. An incorrect time can cause TLS certificate validation errors.
If you can’t open domestic websites either, fix your basic network connection first. If access only fails when v2rayNG is enabled, continue troubleshooting the node and configuration.
2. Check whether the node is available
v2rayNG relies on node parameters to connect. An expired node, a changed port, or an expired subscription can all cause connection failures. On the v2rayNG home screen, long-press a node and select “Test current service connection” or “Test all configurations.” If the result is consistently timeout, EOF, or connection refused, the node is usually unavailable or your network cannot reach it.
- Try a different node: Don’t rely on just one node. Try other routes in the same subscription.
- Update your subscription: Tap the menu in the upper-right corner and select “Update subscription” to avoid using outdated node information.
- Import the node again: If you imported a vmess or vless link from the clipboard, make sure it was copied in full, with no extra spaces or missing line breaks.
- Check that the protocol matches: VLESS, VMess, Trojan, and other protocols use different parameters. Don’t change the port, UUID, or transport settings at random.
This site also shares free nodes for testing, but free nodes can be affected by the number of users and network conditions. If one becomes temporarily unavailable, update your subscription or switch routes first.
3. Check your v2rayNG settings
If the node is working but you still can’t connect, check the client itself. First, update v2rayNG to a recent version, as older versions may not support some Reality, gRPC, or XTLS configurations. Then open “Settings” and check the following:
- Routing mode: Beginners should select “Bypass LAN and mainland China addresses” or use the default rules to avoid blocking local access with global rules.
- VPN permission: The first time you connect, Android will prompt you to authorize the VPN. You must tap Allow.
- Per-app proxy: If “Per-app proxy” is enabled, make sure apps such as your browser, Telegram, and YouTube haven’t been excluded.
- Local DNS: If you can connect but websites won’t load, try switching the built-in DNS or restoring the default settings.
If you’ve changed a lot of settings, the simplest option is to back up your subscription link, clear v2rayNG’s app data, and then import the subscription again to test.
4. Understand common errors and what to check
v2rayNG logs can help identify the problem. Tap the menu in the upper-right corner and open the logs, then check the last few lines. Common errors include: timeout, which usually means the node is unreachable or the current network is blocking the connection; connection refused, which may mean the port is closed; TLS handshake failed, which often points to an incorrect time or mismatched SNI or security settings; and no such host, which may indicate a DNS resolution failure.
Follow one rule while troubleshooting: change only one thing at a time. For example, switch networks first, then switch nodes, then update your subscription, and finally reset the client. Don’t change the protocol, port, TLS, and routing rules all at once, or it will be difficult to tell which change fixed the problem.
5. What to do if you still can’t connect
If you’ve tried all the steps above, run this minimal test: switch to mobile data, update v2rayNG, import a new subscription with a verified format, select one node, authorize the VPN, and test the connection. If it still fails, note the relevant log messages and compare the results with a similar client such as NekoBox or Clash Meta for Android. If another client works, the issue may be with your v2rayNG settings. If none of them work, the node or your current network is probably the problem.