This guide addresses the common question, “What should I do if v2rayNG won’t connect?” If you see a timeout or TLS handshake failure after importing a node, or you connect successfully but can’t open webpages, the cause is usually the node status, your phone’s network or IP, DNS, system proxy settings, or browser environment. Follow the steps below in order. They’re intended for everyday users and don’t involve configuring your own server.
1. Check the node and basic v2rayNG settings
- Open v2rayNG and make sure the correct node is selected. Don’t leave an outdated, non-working node selected.
- Tap the test button in the upper-right corner and check “Test real connection” or the latency results first. If every node times out, your local network may be the issue, or your subscription may have expired.
- Make sure your phone’s date and time are correct. A significant time discrepancy can cause some TLS nodes to fail to connect.
- Update v2rayNG to a recent version. Older core versions may not support some VLESS, Reality, or TLS fingerprint configurations.
- If you use a subscription, update it first. If you copied a node from this site’s free nodes page, copy the latest link and import it again.
Note: A successful latency test doesn’t guarantee that webpages will open. You may still need to check the proxy mode, DNS, and browser.
2. Network and IP issues that can prevent a connection
Many cases where a node seems fine but won’t connect are caused by the current network environment. First, try switching between Wi-Fi and mobile data. If Wi-Fi fails but mobile data works, your router, ISP’s DNS, or local network restrictions may be involved. If neither works, look into the node or client.
- Turn Airplane mode on and off to get a new mobile network IP.
- Restart your router and try getting a different public IP address.
- Turn off other VPNs, accelerators, and ad-blocking tools on your phone to avoid conflicts between VPN services.
- On networks at work or school, UDP, TLS, or specific ports may be restricted. Try a different node protocol or network.
If a node only fails on a particular network, don’t keep changing client settings. Try another network or node first.
3. Check DNS and your browser
If v2rayNG shows that you’re connected but your browser can’t open websites, common causes include DNS poisoning, browser cache issues, or traffic not being routed through the proxy. In v2rayNG settings, make sure “Routing” isn’t set to direct connection only by mistake. Try switching to global proxy mode to see if websites load, then switch back to a commonly used rule, such as bypassing mainland China addresses.
For your browser, first try an incognito window or switch to Chrome, Firefox, or Edge. Clear the browser cache and disable any suspicious proxy extensions, especially if you’ve installed SwitchyOmega, ad blockers, or DNS extensions. Some Chinese browsers have built-in secure DNS or proxy optimization features that may bypass the system VPN.
If only certain websites won’t open, try enabling remote DNS or a built-in DNS option in v2rayNG settings. Disconnect and reconnect after changing the setting. The goal isn’t to create a complicated configuration, but to prevent domain lookups from going through your local network and failing.
4. Quickly identify the source of the problem
- All nodes fail to connect: Check your network, VPN conflicts, client version, and system time first.
- Only one node fails: The node is probably down, or its protocol may be restricted on your current network. Try another node.
- Connected, but no internet access: Check the routing mode, DNS, browser cache, and extensions.
- Works on your phone but not your computer: The node is working; check the computer’s proxy or firewall settings.
It’s a good idea to keep two or three backup nodes using different protocols or regions, so you can compare them when issues arise. Free nodes are affected by availability and network conditions, so occasional disruptions are normal. The steps above can usually help you quickly determine whether the issue is with the node, your network or IP, or your DNS and browser environment.