This article addresses the common question, “What should I do if v2rayNG won’t connect?” It walks through checks for your phone’s network, system time, node configuration, subscription updates, and proxy mode, helping everyday users quickly pinpoint the cause with a simple checklist. It does not cover setting up a server yourself.
1. Check your phone’s environment first
Many connection failures aren’t caused by a faulty node, but by a problem with the device itself. Before opening v2rayNG, check the following:
- Check your network connection: Open a domestic website in your browser to make sure you can access the internet over Wi-Fi or mobile data.
- Turn off other VPNs: Don’t run an accelerator, corporate VPN, or system proxy tool at the same time.
- Check your system time: Go to your phone’s “Date and time” settings and enable automatic time and time zone. An incorrect time can cause TLS handshake failures.
- Check permissions: The first time you connect, Android will show a VPN connection request. Tap Allow.
- Check battery restrictions: In your system’s battery settings, disable background restrictions for v2rayNG to prevent the system from stopping it after it connects.
If you’re using the free nodes curated on this site, try testing 2–3 different nodes first. Free nodes may become temporarily unavailable due to the number of users or fluctuations in the connection. Don’t assume there’s a problem with the client based on a single node.
2. Check your nodes and subscription
Open v2rayNG and go to the node list. Check that each node has a name, address, port, and protocol. Common issues include incomplete copies, failed QR code scans, and outdated subscriptions.
- Long-press the current node and select “Edit.” Make sure its protocol matches the source you imported it from, such as VMess, VLESS, or Trojan.
- If you use a subscription, tap the menu in the upper-right corner, select “Update subscription,” and wait for the update to finish before selecting a node again.
- If you copied a link manually, copy the entire link again, then select “Import from clipboard.”
- Delete any obvious duplicates or blank nodes to avoid selecting an invalid configuration by mistake.
After importing, tap the test function to the right of a node. A timeout doesn’t necessarily mean all your nodes are unusable, so try another one first. If every node times out, continue with the proxy and DNS settings below.
3. Proxy mode, DNS, and per-app routing
If v2rayNG connects but websites won’t load, the issue is often an unsuitable routing or split-tunneling setting. If you’re a typical user, start with the default settings and troubleshoot from there. Avoid enabling complex rules at the same time.
- Go to “Settings” in the sidebar. Try turning “Enable local DNS” on or off and test both ways.
- Start with the routing mode set to bypass LAN and mainland China addresses. If you still have problems, temporarily switch to global mode for testing.
- If “Per-app proxy” is enabled, make sure you’ve selected the apps that need a proxy, such as your browser, Telegram, and YouTube.
- Don’t configure an additional HTTP proxy in your browser, as it may conflict with the system VPN.
The rule of thumb is simple: If global mode works but split tunneling doesn’t, the issue is probably with the rules. If nothing works in any mode, the node may be unavailable or your network provider may be restricting access.
4. Quick fixes for common errors
If you see a connection failed, timeout, or connection refused message, try switching nodes or updating your subscription first. If the status stays on “Connecting,” check the system VPN permission and battery restrictions. If it says connected but you can’t access external websites, focus on DNS, routing mode, and per-app proxy settings. Public Wi-Fi may also block VPN traffic, so try switching to mobile data.
Here’s a practical troubleshooting order: first make sure your phone can access the internet, then correct the time, turn off other VPNs, update your subscription, try 2–3 nodes, switch to global mode, and finally check DNS and per-app proxy settings. Following these steps will usually help you quickly determine whether the cause is a device settings issue, an unavailable node, or a restriction imposed by your current network environment.