What should you do if v2rayNG won’t connect? This article walks you through troubleshooting in the order of checking your device, verifying your nodes, and switching networks. It helps you tell whether the client isn’t routing traffic, a node is unavailable, or your current network is restricted. Start with steps that are easy to undo; there’s no need to immediately uninstall the app, reset your phone’s network settings, or change advanced parameters.
1. First, check whether the app fails to start or starts but can’t access the internet
Tap the start button in v2rayNG and check whether Android displays a VPN connection prompt and whether the VPN icon appears in the status bar. If the connection doesn’t start, check permissions or app conflicts first. If it starts but webpages won’t load, check the node and network. The VPN icon only means that a local connection has been established; it doesn’t mean the remote node is available.
- Make sure your phone can open regular webpages when v2rayNG is off. If it can’t connect to the internet at all, resolve any Wi-Fi sign-in, billing, or signal issues first.
- Check your system date, time, and time zone. We recommend enabling automatic settings; a significantly incorrect time can cause encrypted connection verification to fail.
- Stop any other VPNs, proxies, or filtering tools that use local VPN mode, then restart v2rayNG.
- If tapping Start does nothing, check whether the system VPN permission was denied. If another app has “Always-on VPN” or “Block connections without VPN” enabled, note the original settings before temporarily changing them.
2. Check your nodes and subscription; don’t change settings blindly
Make sure the node you want to use is selected in the list; importing it alone isn’t enough. If you use a subscription, update it in Subscription management, then select a node again. A failed update doesn’t necessarily mean that all nodes are unavailable. The subscription URL may have expired, or it may be inaccessible on your current network.
Run the connection test provided by the client, or test an actual connection, and check whether webpages load. Menu names may vary between versions, and some nodes may not respond to certain types of tests, so a single timeout isn’t conclusive. First, try a different node from a trusted source that has been updated recently. If you use free nodes provided through channels such as this site, keep in mind that their validity and availability can change. Successful import doesn’t guarantee that a node will connect.
If all nodes fail, check whether your client version supports the protocols used by the nodes. If necessary, update the client through the project’s official release channels. Don’t change ports, transport methods, or TLS options at random, and don’t disable certificate verification just to get rid of an error.
3. When should you try a different network?
If your phone can access the internet directly, VPN permission is enabled, and multiple nodes still won’t connect, compare different network connections. Keep the same node and client settings, and switch only between Wi-Fi and mobile data. After switching, stop and restart the connection, then test the same webpage. Keep an eye on your mobile data usage.
- Mobile data works, but the current Wi-Fi doesn’t: The issue is more likely related to that Wi-Fi network’s access policies, sign-in requirements, or network route.
- Wi-Fi works, but mobile data doesn’t: Check whether v2rayNG is blocked from using mobile data and whether your plan has any restrictions.
- Neither network works: Check the node status, subscription details, and client compatibility first; don’t keep switching networks repeatedly.
When using an office, campus, or public network, follow its usage rules and don’t try to bypass network restrictions. If you need to switch networks, use your own mobile data or a trusted hotspot when possible, and avoid connecting to unfamiliar open Wi-Fi networks.
4. What information should you collect if it still doesn’t work?
Open the logs and note the time of the failure, the client version, relevant error keywords, and which node failed on which network. A timeout may involve the node or network route; for a certificate error, check the time and node configuration; for a resolution error, investigate DNS or the domain name. When asking for help, redact subscription links, UUIDs, passwords, and other sensitive information. Sharing only the necessary logs is more helpful for diagnosing the problem than repeatedly reinstalling the app.