What should you do if v2rayNG won’t connect? This article helps you distinguish between phone network issues, VPN conflicts, inactive nodes, and DNS problems. Troubleshoot in this order: check the network first, then the client, and finally the node. These steps apply when a configuration has been imported on an Android phone, but you can’t connect or can’t open webpages after connecting.
1. First, make sure your phone’s network is working
Stop v2rayNG and open a domestic website that you can normally access. If it still won’t load, focus first on Wi-Fi, mobile data, or network sign-in issues. Don’t rush to change the node settings.
- Turn Wi-Fi or mobile data off and back on, then try opening a webpage again.
- When connecting to hotel, campus, or mall Wi-Fi, complete the network authentication first. A network that requires sign-in may show as connected but still not provide internet access.
- Switch between Wi-Fi and mobile data, and test the same node on each. Keep an eye on your mobile data usage.
- Temporarily turn off other VPNs, proxies, or ad blockers that use a local VPN. Android generally can’t run multiple services of this type at the same time.
If the same node works after you switch networks, the issue may be related to the original network. However, don’t conclude that the network is blocking access based on a single test. Try again later or contact the network administrator to confirm any usage restrictions.
2. Check that v2rayNG is actually routing your traffic
Select the configuration you want to use, tap the start button, and allow the VPN connection request from Android. If the connection doesn’t start successfully, check the message shown in the app. Interface labels may vary between versions; follow what you see on your device.
- Open the system VPN settings and check whether another app has enabled “Always-on VPN” or the option to block connections without a VPN.
- If only some apps won’t open, check v2rayNG’s per-app proxy settings and make sure the affected apps aren’t excluded.
- If the connection drops when the screen locks, allow v2rayNG to run in the background in system settings and disable any strict battery restrictions for it.
The VPN icon doesn’t mean the node is working: it only indicates that the local VPN service is running. You still need to open a webpage to verify the connection.
3. Update your subscription to distinguish node issues from configuration issues
If you use a subscription, update it first and make sure no errors appear, then test a configuration from the updated list. If you import a link manually, copy it in full to avoid it being truncated by a messaging app. Free nodes can also stop working, so test any free nodes provided on this site to confirm that they connect.
Try another recently updated node from a trusted source for comparison. If only one node fails, the node or its configuration is the most likely cause. If they all fail, continue checking the network and client. Don’t change the port, transport, or TLS settings at random—they must match the server settings. Don’t disable certificate verification just to connect, either.
4. Use the logs to narrow down the cause
Check the logs after starting the connection. A timeout usually means the connection could not be established in time, possibly because of the network path or an unavailable node. If domain name resolution fails, look at DNS. First, set your phone’s date and time to automatic, then check the system’s “Private DNS” setting. If you’ve configured a custom service, temporarily switch to automatic and test again. Note your original setting so you can restore it later.
Change only one setting at a time, and test immediately after each change. If it still doesn’t work, note the app version, network type, and error message before asking for help. Before sharing screenshots or logs, hide subscription links, UUIDs, passwords, and other sensitive information. Get updates from the project’s official channels, and don’t install modified versions from unknown sources.