This article addresses the common question, “What should I do if v2rayNG won’t connect?” Follow these low-risk checks in order: first confirm your browser and phone’s network are working, then check DNS, system proxy settings, node connectivity, and subscription status. None of these steps require reinstalling the system or changing low-level settings, so you can work through them one by one.
1. First check whether the issue is with your browser or network
Sometimes v2rayNG shows that it’s connected, but webpages still won’t load. That doesn’t necessarily mean the node is down. Start with these basic checks:
- Open your browser and visit a domestic website, such as a search or news page, to confirm your phone can access the internet.
- Try a different browser—for example, switch from Chrome to your phone’s built-in browser—to rule out issues with the browser cache, extensions, or security settings.
- Turn off Wi-Fi and use mobile data, or vice versa, to see if the current network is blocking traffic or the router’s DNS is malfunctioning.
- Check that your phone’s clock is correct. An incorrect time can cause TLS certificate verification to fail.
If domestic websites won’t load either, troubleshoot your phone’s network first. If they work but overseas websites don’t, continue by checking v2rayNG settings.
2. Check v2rayNG’s basic status
Open v2rayNG and check that the status in the upper-right corner or at the bottom shows that it’s connected. Then long-press the current node to check that its configuration is complete. Common protocols such as VLESS, VMess, and Trojan require correct details for the address, port, user ID, transport, and other settings.
- Make sure the selected node is the one you want to use, not an empty configuration or an old node.
- Tap “Test connection” or “Real connection test” and check whether it reports a timeout, TLS error, or connection refusal.
- If you just imported a subscription, pull down to refresh or tap the subscription update button to avoid using expired nodes.
- If prompted to grant system VPN permission, tap Allow. Otherwise, v2rayNG can’t route your traffic.
This site also provides some free nodes for testing, but free connections may be affected by peak-hour congestion, regional network conditions, or node maintenance. We recommend trying several nodes in turn.
3. Low-risk changes to DNS and routing settings
If v2rayNG is connected but some websites won’t load, check DNS. If you’re a regular user, avoid changing complex rules without a good reason. Start with the common options in the app.
- Open v2rayNG settings and check whether “Local DNS” or a similar option is enabled.
- If domain names aren’t resolving, try switching to the app’s default DNS, then reconnect.
- For routing, start with “Bypass LAN and mainland China addresses” or the app’s default rules.
- Don’t run multiple proxy tools at the same time, as their DNS and VPN settings may conflict.
Typical signs of a DNS issue include being able to reach an IP address but not open a website by its domain name, or being able to use some apps but not your browser. In this case, restarting v2rayNG, changing the DNS option, and reconnecting are usually more effective than repeatedly importing nodes.
4. How to check for a failed connection or subscription issue
If no websites load and connection tests keep timing out, the route may be unavailable. Try these steps in order:
- Try two or three nodes in different regions from the same subscription.
- Update the subscription and select a node again instead of continuing to use an old link.
- Import the node into another client, such as Clash or sing-box, to check whether the issue is with the client.
- If it only fails on one network, the cause may be your carrier’s or Wi-Fi network’s policies.
Avoid changing advanced settings at random, such as TLS, Reality, or transport-layer fields, unless you know the service provider requires it. A single incorrect node parameter can prevent the connection from working entirely.
5. Recommended troubleshooting order
If v2rayNG fails to connect, work through these steps in order: “check the network → test the browser → update the subscription → switch nodes → check DNS → restart the client.” This is the lowest-risk approach and makes it easier to pinpoint the issue. If all nodes fail, first consider an expired subscription, route maintenance, or restrictions on your current network. If only the browser fails, focus on its cache, DNS, and proxy settings. Work through the checklist one item at a time—it’s usually faster to restore your connection this way than by reinstalling the app.