What should you do if v2rayNG won’t connect? This guide walks you through troubleshooting in this order: check your device’s network, verify the client settings, update your nodes, and compare network environments. This can help you determine whether the problem is with your phone, a node, or the current network. Start with small, reversible changes; there’s no need to immediately reinstall the app, reset your phone’s network settings, or disable security protections.
1. First, determine whether the app won’t start or starts but can’t access the internet
After you tap Connect, if you don’t see the Android VPN permission prompt or key icon, first check the app’s permissions. If the app shows as running but webpages won’t load, continue by checking the node and network. Being shown as connected doesn’t guarantee that the proxy node is working; it may only mean that the VPN service on your phone has started.
- Disconnect v2rayNG and use your browser to open a domestic website that normally works. If that won’t load either, first check whether you need to sign in to the Wi-Fi network, your mobile data account has an outstanding balance, or the signal is poor.
- Check your system date, time, and time zone. We recommend enabling automatic settings to prevent an incorrect time from affecting encrypted connection verification.
- Quit any other VPNs, accelerators, or filtering tools that use a local VPN, then restart v2rayNG to avoid conflicts over the system VPN connection.
- When connecting for the first time, allow the system VPN request. If another app is reported as occupying the connection, check your system’s VPN settings to see whether another app has “Always-on VPN” enabled.
2. Check your nodes and subscription without changing too many settings at once
Make sure the node you want to use is selected, then use the test feature in the menu to check the connection. Test names may differ between versions, and a latency test doesn’t necessarily reflect whether webpages will load. A single timeout doesn’t prove that the network is restricted; an expired node, an invalid address, or a temporary server issue could also cause the failure.
- If you use a subscription, update it and check for messages such as download or parsing failures. An update failure doesn’t necessarily mean that your existing nodes are no longer working.
- Test another node from a trusted source that has been updated recently. If all your nodes come from the same subscription, they could still all be unavailable at the same time.
- If you import a node manually, check that the link is complete, especially that no parameters at the end have been omitted. If in doubt, copy and import the original link again rather than changing the port or transport settings at random.
- Check that the routing mode matches what you expect. Split-routing rules may send some apps directly to the internet. If per-app proxying is enabled, make sure your browser isn’t excluded.
When possible, use a stable version released through the project’s official channels. Back up any necessary settings before updating, but don’t post your subscription link, node password, or full configuration in a public group when asking for help.
3. When should you try a different network environment?
If basic internet access is working, VPN permission has been granted, and multiple nodes still won’t work, compare network environments. Change only one condition at a time: use the same phone, node, and settings to test over Wi-Fi first, then turn off Wi-Fi and repeat the test using your own mobile data. Keep an eye on data usage.
If mobile data works but Wi-Fi doesn’t, the issue is more likely related to the current Wi-Fi network, router, or upstream network, though that alone won’t identify the exact cause. On public Wi-Fi, complete any required sign-in first. On campus or workplace networks, follow the usage rules and don’t try to bypass administrative restrictions. If both networks fail, check the node and client first.
4. If it still fails, note the error and ask for help
Check the logs for timeouts, domain name resolution failures, or certificate errors, and note the client version, network type, and steps needed to reproduce the problem. Assess timeouts in light of the results from testing different nodes and networks. If name resolution fails, first confirm that your basic internet connection is working. For certificate errors, first check the time and node settings. Don’t disable certificate verification just to get connected. Before sharing logs, redact server addresses, identifiers, and subscription links. This makes troubleshooting easier while protecting your configuration.