What should you do if v2rayNG won’t connect? This guide walks through troubleshooting in the order of “local network, VPN permissions, node subscription, and log messages” to help you tell whether the issue is a disconnected phone, an unavailable node, or a proxy setting. It applies to Android users and doesn’t require changes to server settings.
1. First, make sure your phone can access the internet
Disconnect v2rayNG, then use your browser to open a domestic website that you can normally access. If it still won’t load, troubleshoot your Wi-Fi or mobile network first rather than repeatedly switching nodes.
- Switch between Wi-Fi and mobile data. After each switch, reconnect v2rayNG and check whether the problem occurs only on one type of network.
- Public Wi-Fi may require web-based authentication. Disconnect the proxy, complete the login or accept the terms of use, and then connect again.
- Temporarily exit other VPNs, accelerators, or filtering apps that use local VPN mode. Android usually can’t run multiple VPN services at the same time.
- Turn on automatic date, time, and time zone settings. A significantly incorrect time can cause TLS certificate verification to fail.
Change only one setting at a time, and test right away. If it doesn’t help, restore the original setting. This makes it easier to pinpoint the problem.
2. Check VPN permissions and background restrictions
Select a node in v2rayNG and tap the start button. When the system displays a VPN connection request, tap Allow. If the VPN icon doesn’t appear or the service stops shortly after starting, open the system app settings and make sure background activity and network access aren’t restricted.
Some phones require you to allow autostart and set the battery policy to unrestricted. If “Always-on VPN” or “Block connections without VPN” is enabled for another app in the system VPN settings, that may also affect your test. Note the original settings before changing them as needed. The VPN icon only indicates that the service has started; it doesn’t mean the node is reachable.
3. Check that the node and subscription are available
- Update the relevant subscription in subscription management and check for errors. If the update fails, check whether the subscription URL is complete or expired. Don’t repeatedly add the same subscription.
- After updating, select a node again, then stop and restart the connection to make sure you aren’t still using an old configuration.
- Use the connection test provided by the client, then verify by opening a webpage. Menu names may vary between versions; treat latency results as a rough guide only.
- If only one node fails while others work, that node is the most likely cause. If all nodes fail, continue checking the network and client.
When importing a VLESS or other share link, keep the link intact. Don’t guess at changes to the port, transport method, or TLS settings. Free nodes may become unavailable at any time. Even if you get one from a source such as this site, test it first; continued availability isn’t guaranteed.
4. Use logs to pinpoint the issue instead of reinstalling blindly
Open the logs page, reconnect once, and check the errors that appear. A timeout may indicate that the node can’t be reached or that there’s a problem with the network path. Messages mentioning lookup or DNS suggest checking domain name resolution. Messages mentioning certificate or TLS suggest checking the system time and node details. These messages are troubleshooting clues, not definitive diagnoses.
If you’ve manually configured Android “Private DNS,” temporarily switch it back to Automatic and test again. If only certain apps can’t connect, check whether they’re excluded from per-app proxying. If only some websites are affected, temporarily switch routing modes to compare, then restore the original setting after testing.
Don’t disable certificate verification just to get rid of an error. If the problem persists, update the client using a trusted source. Back up your configuration before reinstalling. When asking for help, include your system version, client version, network type, and redacted logs. Don’t share your subscription URL, UUID, or full share link publicly.