This article addresses the common question “What should I do if v2rayNG won’t connect?” You may have imported a node and tapped Connect, yet still be unable to open web pages—or the app may show that it’s connected when it isn’t actually working. Follow these troubleshooting steps in order, starting with the easiest checks for most users: nodes, IP, DNS, and browser settings.
1. First, check that your nodes and subscription are working
When v2rayNG fails to connect, the most common causes aren’t a faulty phone, but an inactive node, an expired subscription, or an incomplete configuration import. Start with these steps:
- Open v2rayNG, long-press the current node, and select “Edit.” Make sure the address, port, UUID, and transport protocol are all filled in.
- If you use a subscription, open the menu in the upper-right corner, tap “Update subscription,” then select a node and try connecting again.
- Test other nodes from the same subscription. Don’t keep retrying the same node.
- Check that your phone’s clock is accurate. A significant time difference can cause TLS handshake failures.
This site curates free nodes that you can import, but their reliability can vary depending on how many people are using them and the status of the connection. We recommend keeping several backup nodes available.
2. Check your local IP and network
If none of your nodes connect, try switching networks. For example, switch from Wi-Fi to mobile data, or connect to a different Wi-Fi network. Some campus networks, company networks, and public hotspots restrict proxy connections, causing v2rayNG to time out repeatedly.
Before connecting, try opening a domestic website to confirm that your internet connection is working. After connecting, visit an IP lookup site and see whether your outgoing IP has changed. If v2rayNG reports a successful connection but your IP hasn’t changed, your traffic probably isn’t actually going through the proxy. This may be due to the routing mode, VPN permissions, or a conflict with the system proxy.
The first time you connect on Android, you’ll be prompted to grant VPN permission. If you accidentally tapped Cancel, tap Connect again and allow it. We also recommend turning off other VPNs, accelerators, and ad-blocking apps to prevent multiple VPN services from competing for access.
3. How to troubleshoot DNS issues
Sometimes a node connects, but web pages won’t open—or only some websites have problems. This may be a DNS issue. DNS translates domain names into IP addresses. If DNS is being interfered with or using the wrong route, you may appear to be connected but still be unable to access websites.
- In v2rayNG settings, enable “Bypass LAN and mainland addresses” or choose an appropriate routing rule.
- Try changing the “Domain strategy,” for example, to AsIs or IPIfNonMatch, then reconnect.
- Clear your browser cache, close the browser, and reopen it.
- If you use Private DNS, temporarily turn off “Private DNS” in Android settings and test again.
Don’t change too many settings at once. Change just one setting at a time so you can tell which step fixed the problem.
4. Browser settings can also affect access
If v2rayNG connects normally but your browser still can’t open pages, the cause may be the browser cache, an extension, proxy settings, or Secure DNS. Try testing with your system browser and Chrome. If only one browser has the problem, open its settings and turn off features such as “Secure DNS,” “Data Saver,” and proxy extensions.
If only one website fails, try opening it in incognito mode or clearing that site’s cookies. Some websites flag sessions based on old cookies or IP addresses, so you may need to sign in again after switching nodes.
5. Quick troubleshooting checklist
- Update your subscription and test two or three different nodes.
- Make sure your phone’s clock is correct and allow v2rayNG to establish a VPN connection.
- Switch between Wi-Fi and mobile data to rule out network restrictions.
- Check whether your IP changes after connecting.
- Adjust your DNS, routing, and browser settings.
If you still can’t connect, check the logs in v2rayNG for these keywords: “timeout” usually indicates a network issue or an unreachable node; “TLS handshake failed” is often related to the time, certificates, or configuration; and “connection refused” usually means the node’s port is unavailable. Troubleshooting based on the logs is more effective than reinstalling the app without knowing the cause.