This guide addresses the common question, “What should I do if v2rayNG won’t connect?” It walks through checks in order of increasing risk, from your phone’s network, browser proxy, and DNS to server routes and client settings. It does not involve flashing your device, rooting it, or changing low-level system settings, so it’s suitable for everyday users to follow.
1. First, rule out basic network problems
Many connection failures aren’t caused by v2rayNG itself, but by issues with your local network, time settings, or permissions. Start with these checks, which won’t affect your phone:
- Close v2rayNG and open a domestic website directly in your browser to confirm your phone can access the internet.
- Switch between Wi-Fi and mobile data once in case your current network is restricting proxy connections.
- Check that your phone’s date, time, and time zone are set to sync automatically. An incorrect time can cause TLS handshake failures.
- Open your system settings and make sure v2rayNG isn’t blocked by battery-saving settings, background restrictions, or network permissions.
If domestic websites won’t load either, troubleshoot your local network first. If they load normally but overseas websites don’t, continue checking your server and proxy settings.
2. Check your browser and proxy mode
If v2rayNG shows “Connected” but your browser still won’t load webpages, the proxy may not actually be handling your traffic. Open v2rayNG and check that the key or VPN icon appears in the status bar. If it doesn’t, the system VPN tunnel hasn’t been established successfully.
For testing, use Chrome, Edge, or your system browser to avoid conflicts with built-in proxies or ad-blocking extensions in some browsers. If you’re using a mode such as “Proxy only” or “Per-app proxy,” make sure your browser is selected. For initial testing, we recommend Global mode or Bypass LAN and Mainland China addresses. Once it works, you can adjust the rules.
3. Troubleshoot DNS and server routes
If you see a timeout, a blank page, or a DNS resolution error, try changing your DNS. In v2rayNG settings, find the DNS options and try automatic DNS first. If the problem persists, try a commonly used public DNS. Don’t run multiple tools that change DNS at the same time—for example, Private DNS, an accelerator, or an ad-blocking VPN—as they may conflict.
- “timeout”: Usually indicates an unreachable route, network blocking, or an unavailable server.
- “connection refused”: The server port may be unavailable, or the configuration may have expired.
- “TLS handshake failed”: Often caused by an incorrect time, domain name, or transport settings.
- Connected but very slow: Try another route from the same subscription, or test over Wi-Fi and mobile data.
This site collects some free nodes for testing, but their stability depends on the number of users and network conditions. Treat them as troubleshooting or temporary resources rather than relying on a single node.
4. Reimport your subscription and nodes
Incorrect node parameters are another common cause of v2rayNG connection failures. If you imported a link by copying and pasting, make sure it’s complete and contains no extra spaces or line breaks. If you use a subscription, open the menu in the top-right corner of v2rayNG, select Subscription settings, and update the subscription before testing again.
- Long-press the current node and select Test latency or Test real connection.
- Delete nodes that are clearly unavailable, duplicated, or expired.
- Copy the subscription URL again from a trusted source and paste it into v2rayNG.
- After updating the subscription, choose a node with relatively low latency and complete protocol details.
If a node won’t connect on multiple networks while other nodes work normally, it’s safe to conclude that the node is down or its route is unavailable. There’s no need to keep reinstalling the client.
5. Reset the client only as a last resort
If none of the above works, back up your subscription URL, then clear the v2rayNG cache or reinstall the latest version. After installation, import just one node you know works and test it. This prevents old rules, DNS settings, or routing configurations from affecting your diagnosis. Troubleshoot in this order: network, browser, DNS, node, and finally the client. This helps avoid unnecessary changes and makes it easier to identify the real cause.