What should you do if v2rayNG won’t connect? This guide walks you through troubleshooting in the order of “local network → VPN permissions → node subscription → routing and logs” to help you tell whether the problem is your phone’s internet connection, conflicting app settings, or an unavailable node. It applies to v2rayNG for Android and does not require changes to the server configuration.
1. First, make sure your phone can access the internet
Disconnect v2rayNG, then use your browser to open a website you can normally access directly. If that doesn’t work either, address issues such as Wi-Fi sign-in, mobile data settings, or an overdue bill first instead of repeatedly importing nodes.
- Turn off the proxy and try opening a regular webpage. On public Wi-Fi, complete the sign-in process first.
- Switch between Wi-Fi and mobile data, and connect to the same node on each. If it fails on only one network, the network environment is the more likely cause.
- Turn on Airplane mode briefly, then turn it off and try again once the network is back.
- In your system date settings, enable automatic time. A significantly incorrect time can cause TLS verification to fail.
Change only one setting at a time and test immediately afterward; otherwise, it’s hard to tell which step fixed the problem. Keep an eye on data usage when testing with mobile data.
2. Check VPN permissions and app conflicts
When you start v2rayNG, the system will usually prompt you to allow a VPN connection. If you don’t see a VPN indicator in the status bar, first check whether the connection started successfully; the indicator may look different on different phones.
- Exit other VPNs, accelerators, and ad blockers or firewall apps that use local VPN mode to avoid competing for the system VPN connection.
- Check Android’s “Always-on VPN” and “Block connections without VPN” settings, and make sure they aren’t assigned to another app. Menu names vary by device.
- If the connection only drops after the screen locks, allow v2rayNG to run in the background and remove any overly restrictive battery limits.
For a first-time install or update, use an official project distribution channel whenever possible, and avoid modified versions from unknown sources. Disabling system security protections should not be treated as a routine fix.
3. Check that your node and subscription are valid
Make sure the node you intend to use is selected, not just imported. If you use a subscription, update it and check the result. A failed update doesn’t mean all existing nodes are invalid; the subscription URL may simply be temporarily inaccessible.
If you imported a link manually, check for missing characters, spaces, or line breaks. Use the provider’s information to verify the protocol, port, transport, and TLS settings. Don’t disable certificate verification just to get connected. You can also test another node from a trusted source; free nodes on this site may also expire or become unavailable.
A node test timing out is only a clue for troubleshooting. Some test methods can be affected by the target site or network restrictions, so don’t conclude that a node is permanently unavailable based on a single result.
4. Connected but can’t open webpages? Here’s what to check
First, check per-app proxy settings: if your browser is excluded, its traffic may not be going through the proxy. Then check the routing mode. You can temporarily switch to global proxy mode for comparison, and restore your usual rules after testing. If global mode works but rule-based mode doesn’t, check the routing rules and DNS settings first.
Open the logs and look for errors around the time of the connection attempt: “timeout” usually indicates a connection timed out; “connection refused” often means the destination port rejected the connection; certificate errors call for checking the time and node details; and domain resolution errors point to DNS. Log messages aren’t definitive on their own; consider them alongside the results of trying another network or node.
If the problem persists, note your Android and v2rayNG versions, network type, protocol, and the relevant error messages when asking for help. Don’t share your full subscription URL, UUID, password, or QR code publicly, and cover sensitive information in screenshots.