This guide addresses the common question, “What should I do if v2rayNG won’t connect?” Follow this checklist to troubleshoot your phone’s network, system time, node configuration, subscription updates, and app permissions. It can help you quickly determine whether the problem is an unavailable node, an issue with your environment, or a client setting.
1. Check your phone’s network environment first
Many connection failures aren’t caused by v2rayNG itself, but by an unsuitable network. Start with these basic checks rather than repeatedly deleting your configuration.
- Switch networks: Test both Wi-Fi and mobile data. If you’re on a company, campus, or hotel network with strict restrictions, try using mobile data instead.
- Turn off other proxies or VPNs: Don’t run an accelerator, an ad-blocking VPN, or another proxy client at the same time, as they can cause port conflicts.
- Check your system time: An incorrect time or time zone can cause TLS certificate verification to fail. Turn on “Set time automatically.”
- Check your battery and power-saving settings: Some Android systems restrict v2rayNG in the background, causing the connection to drop soon after it’s established.
Once you’ve completed these steps, reopen v2rayNG, tap the switch in the lower-right corner to connect, then test the connection by visiting a familiar website in your browser.
2. Check that your nodes and subscription are working
If your network environment seems fine, check your nodes next. Free nodes may be temporarily unavailable due to congestion, maintenance, or blocking. We recommend regularly updating the free nodes provided on this site before testing them.
- Long-press the current node and select “Test configuration real connection” or a similar test option to check whether it times out.
- If you use a subscription, open the subscription settings and tap Update. After updating, don’t test only the first node—try several.
- Make sure the imported content is complete: if a VLESS, VMess, or Trojan link is missing characters, the connection will usually fail outright.
- Check that the protocol settings match: parameters such as Reality, TLS, WebSocket, and gRPC must match the node information. Changing the port or transport method at random can make the node unusable.
Tip: If all your nodes fail, the issue is more likely to be your network environment or app permissions. If only one node fails, that node is more likely to be unavailable.
3. Check common v2rayNG settings
Open v2rayNG’s settings and check these items first. For routing mode, most users should stick with the default or “Bypass LAN and mainland China addresses” setting rather than switching to complex rules. Leave DNS on its default setting to start. If you can connect but some websites won’t load, try switching to a remote DNS server.
If the app says “Connected” but webpages won’t load, wait for the VPN icon to appear in the system bar, then test in your browser’s incognito window. You can also clear your browser’s DNS cache or try a different browser. If the app doesn’t prompt you to authorize the VPN, delete the old VPN configuration in your system settings, then authorize v2rayNG again.
Some phone management apps may also block background network access. Grant v2rayNG permissions such as run in the background, access the network, and ignore battery optimization. This is especially worth checking on Xiaomi, Huawei, OPPO, and vivo phones.
4. Quick troubleshooting steps, in order
- Close v2rayNG and any other VPNs, then reset your phone’s network connection.
- Correct your system time and switch between Wi-Fi and mobile data.
- Update your subscription or reimport the node link.
- Test nodes one at a time, prioritizing those with normal latency that pass the real connection test.
- Restore v2rayNG’s default routing and DNS settings.
- If it still doesn’t work, uninstall the old version, install the latest version of v2rayNG, and reimport your configuration.
In summary, if v2rayNG won’t connect, don’t assume the node is the only possible cause. Troubleshoot in this order: environment—nodes—subscription—permissions—settings. This will usually help you find the cause quickly. If free nodes are unstable, keep several alternatives available and update your subscription regularly.