This article addresses the common question, “What should I do if v2rayNG won’t connect?” In many cases, the node isn’t necessarily down—the issue may be caused by your phone’s network, DNS, system proxy, browser cache, or an incorrectly imported configuration. The steps below are ordered so that everyday users can follow them, and apply when using nodes such as VLESS, VMess, or Trojan.
1. First, check that the node and import method are working properly
After opening v2rayNG, avoid repeatedly switching settings. Start by checking the basics. If the node came from a subscription link, pull down to refresh the subscription. If you copied the link manually, make sure no characters are missing and there are no extra spaces or line breaks.
- Open v2rayNG and tap “Update subscription” in the upper-right corner, or import the node again.
- Select a node and tap the connect button in the lower-right corner.
- After connecting, tap “Test connection” or open a webpage in your browser.
- If the connection times out, try another node from the same subscription.
We also compile free nodes for testing, but their reliability can vary. We recommend keeping at least 2–3 backup nodes so you don’t mistake a problem with a single node for a software issue.
2. Your IP network environment may be preventing the connection
v2rayNG relies on your phone’s current network. If you’re using a corporate network, campus network, or public Wi-Fi, it may restrict certain ports or proxy traffic. The easiest way to check is to switch networks: if Wi-Fi doesn’t work, try mobile data; if mobile data doesn’t work, try another Wi-Fi network.
- Turn Airplane mode off and back on to have your phone obtain a new IP address.
- Restart your router to rule out local network cache issues.
- If the connection fails only on a particular Wi-Fi network, that network may have restrictions.
- Don’t run other VPNs, accelerators, or proxy apps at the same time.
If it works as soon as you switch networks, v2rayNG itself is probably fine—the issue lies with your current IP network environment.
3. How DNS and your browser environment can affect access
Sometimes the app shows that you’re connected, but webpages won’t load. This is often related to DNS or your browser environment. Incorrect routing or DNS settings in v2rayNG can cause domain lookups to use the wrong route. If you’re an everyday user, start with the default settings and avoid changing complex rules without a reason.
Try finding the DNS options in v2rayNG’s settings and restoring them to their defaults, or enabling a common mode such as “Bypass LAN and mainland China addresses.” If you’ve imported a lot of rule files, try creating a clean configuration and testing again.
For your browser, first test with the built-in system browser or Chrome, and clear the cache for the website you’re trying to access. Some browser extensions, ad blockers, DoH secure DNS, and privacy proxy features may conflict with v2rayNG. If so, turn off the browser’s built-in proxy or secure DNS, then reload the webpage.
4. Quick checklist if you still can’t connect
- Check that your phone’s date and time are correct. An incorrect time can cause TLS handshake failures.
- Make sure the system allows v2rayNG to create a VPN connection.
- Update v2rayNG to a newer version; older versions may not support some protocol parameters.
- Delete any problematic nodes and import them again from the subscription link.
- Check the logs. If you repeatedly see “timeout,” the node or network is probably unreachable.
In short, if you can’t connect, try another node first, then another network, and then check DNS and your browser. Don’t start by changing a bunch of advanced settings. Following these steps usually helps you quickly determine whether the problem is a down node, network restrictions, or your device’s environment.