This article addresses common questions about “what to do when v2rayNG won’t connect,” including imported nodes that can’t access the internet, a connection that appears active but won’t load webpages, and websites that won’t open. Follow the steps below to check your IP, DNS, browser environment, and client settings. They’re suitable for Android users to follow step by step.
1. First, check that the node and basic settings are working
Many connection failures aren’t caused by a problem with your phone. The node may be down, the subscription may need updating, or the wrong proxy mode may be selected. Start with these basic checks before changing more advanced settings.
- Open v2rayNG and tap “Update subscription” in the top-right corner, or re-import your subscription link.
- Select a node, tap the connect button in the bottom-right corner, and confirm that the VPN icon appears at the top of the screen.
- Open “Settings” and make sure Enable local DNS and any routing-related options haven’t been changed inadvertently.
- Try 2–3 different nodes to rule out a temporary issue with a single node.
- Close other VPNs, accelerators, and firewall apps to avoid conflicts with ports or VPN permissions.
If you’re using the free nodes provided on this site, copy the latest subscription and import it again. Free nodes may become unavailable due to routing changes or fluctuating traffic.
2. IP issues: What to do if you’re connected but sites still won’t open
A successful connection in v2rayNG doesn’t guarantee that external websites are accessible. Open a browser and search for “IP lookup” to check whether your current public IP has changed. If it still shows your local ISP, your traffic isn’t going through the proxy, so check your routing mode.
In v2rayNG settings, temporarily switch the routing mode to Global Proxy for testing. If websites open with Global Proxy but not with the bypass-China or custom rules, the problem is likely caused by traffic-splitting rules. Try updating the Geo assets, switching routing modes, or using Global Proxy to confirm that the node works.
3. DNS issues: Connected, but domain names won’t resolve
Typical signs of a DNS issue include Telegram working while webpages won’t load, or being able to visit a site by IP address but not by domain name. First, clear your browser cache, then enable the DNS-related options in v2rayNG to prevent interference with DNS lookups handled directly by your phone’s system.
- Switch networks: test Wi-Fi and mobile data separately.
- Turn off Private DNS: search for “Private DNS” in Android settings and set it to Off or Automatic.
- Reconnect in v2rayNG, then restart your browser.
- If needed, restart your phone to clear the old DNS cache.
Company or campus Wi-Fi may have strict restrictions that block DNS or VPN traffic. Try mobile data to find out whether the issue is with your current network.
4. Your browser environment can also affect the results
Sometimes v2rayNG is working fine and the problem lies with the browser. For example, the browser may have Secure DNS, a proxy plugin, or an ad-blocking extension enabled, or it may be using a stale connection. Test with both your system browser and Chrome, and try opening the site in incognito mode.
Some browsers also have built-in features such as “Data Saver,” “Cloud Acceleration,” or “Secure DNS” that may bypass the system VPN. For troubleshooting, turn these features off to keep things simple. If apps work but the browser doesn’t, focus on the browser’s proxy and DNS settings.
5. Quick troubleshooting steps if you still can’t connect
Try these steps in order: update your subscription, switch nodes, enable Global Proxy, switch networks, turn off Private DNS, restart your phone, and reinstall the latest version of v2rayNG. Don’t change too many settings at once, or it will be hard to tell what fixed the problem.
Finally, if all nodes time out, your subscription may have expired, the nodes may be down, or your current network may be blocking the connection. If only one website won’t open, the cause may be a traffic-splitting rule or a restriction on the target website. Check these four areas—node, IP, DNS, and browser—to diagnose most v2rayNG connection problems.