This article addresses issues Android users may encounter when using v2rayNG, such as “unable to connect,” “connected but no internet,” “test timed out,” and “node latency is -1.” Use the checklist below to troubleshoot your network environment, node details, permissions, and client settings. It’s also useful if you’ve imported free nodes or a subscription but still can’t access the internet as expected.
1. First, check that your network connection is working
Many v2rayNG connection failures aren’t caused by a faulty client, but by problems with your local network or system restrictions. First, open a domestic website in your browser to make sure your phone can access the internet. Then test on both Wi-Fi and mobile data to rule out network blocking or DNS issues.
- Turn Airplane mode off and back on to refresh your network connection.
- If you’re using a campus network, company network, or hotel Wi-Fi, check whether you need to sign in through a web page.
- Temporarily disable restrictions on network access from power-saving mode, data management apps, and third-party security software.
- Check that your phone’s clock is accurate. An incorrect time can affect TLS connections.
If these basic conditions aren’t met, changing nodes usually won’t help. Make sure your local network is working before continuing to troubleshoot v2rayNG.
2. Check that the node or subscription is valid
The most common reasons v2rayNG can’t connect are an inactive node, an expired subscription, or an incompletely copied configuration. This site collects some free nodes for testing, but their stability can vary. We recommend importing several nodes and testing them one by one instead of relying on a single connection.
- Open v2rayNG, go to the menu in the upper-right corner, and select “Test all configurations for real connectivity.”
- If all configurations time out or fail, update your subscription or copy the node link again.
- Long-press a node to check whether fields such as the address, port, user ID, transport protocol, TLS, and SNI are blank or incorrect.
- If you’re using a subscription link, make sure it doesn’t contain extra spaces. Use “Update subscription” rather than pasting it manually into the node field.
A latency test doesn’t guarantee that a node is usable. Some nodes report latency but still can’t open web pages, so rely on the real connectivity test and your actual browsing results.
3. Check v2rayNG permissions and proxy mode
When you connect for the first time, Android will display a VPN connection request. You must tap Allow. If you accidentally tap Cancel, v2rayNG may appear to be running but won’t be able to route your traffic. Search for “VPN” in system settings, remove the old v2rayNG configuration, and reconnect.
On the v2rayNG main screen, make sure the airplane icon at the bottom is active and that the node you want to use is selected. For routing mode, we recommend that most users start with “Bypass LAN and mainland addresses” or the default rules. This helps avoid misconfigured global rules that can disrupt both domestic and international websites. Don’t run multiple VPN apps at the same time, such as other accelerators, VPN-based ad blockers, or packet capture tools. They can compete for the system’s VPN connection.
4. How to handle common errors
- context deadline exceeded: Usually indicates a node timeout, network blocking, or an unreachable server. Try a different network or node.
- connection refused: The port is unavailable or the node configuration is incorrect. Import the subscription again.
- TLS handshake failed: Check your phone’s clock, the TLS setting, and whether the SNI/domain matches the node’s requirements.
- Connected but web pages won’t open: Try a different routing mode, or change the DNS option in settings and reconnect.
If the problem started after you updated v2rayNG, try clearing the app cache and importing your subscription again. If that doesn’t work, uninstall and reinstall the app. Back up any working nodes first to avoid losing your configuration.
5. Recommended troubleshooting order
In practice, work through these steps in order: “local network → system VPN permissions → update subscription → try another node → real connectivity test → check routing and DNS.” This is the quickest way to determine whether the problem lies with your phone, the client settings, or the node itself. If nodes from multiple sources all fail, your current network is probably imposing strict restrictions. If only one node fails, simply switch to another.
In short, if v2rayNG can’t connect, don’t rush to change advanced settings at random. First check your network, permissions, subscription, and node validity using the list above. Most connection issues can be resolved without help by importing a working node correctly and avoiding conflicts with other VPN apps.