This article addresses the common question, “What should I do if v2rayNG won’t connect?” Starting with low-risk steps that don’t involve changing your system or tinkering with low-level settings, it walks you through checking nodes, subscriptions, your network environment, and client settings—and helps you decide when to switch between Wi-Fi and mobile data or try a different node.
1. First, check whether the problem is with the node or subscription
If v2rayNG won’t connect, don’t uninstall and reinstall it right away. In many cases, the node has stopped working, the subscription hasn’t been updated, or the QR code was imported incorrectly. Check the following in order:
- Open v2rayNG and make sure a node is selected. A checkmark should appear next to its name.
- Tap the menu in the top-right corner, select “Update subscription,” and wait for it to finish before trying to connect again.
- Long-press a node and select “Test latency” or “Test real connection.” If it keeps timing out, try another node in the same subscription first.
- Make sure your phone’s time is set to sync automatically. A significant time difference can cause TLS handshakes to fail.
- If you imported a link manually, copy the entire vmess, vless, or trojan link again to make sure no characters are missing.
If you’re using free nodes provided on this site, update the subscription before testing. Free nodes may change when routes are adjusted, so they can’t be guaranteed to remain available long term.
2. Check common v2rayNG client settings
If the node is working but you still can’t connect, check the client itself. In v2rayNG, make sure VPN permission is granted. The first time you connect, Android displays a system confirmation prompt; tapping Cancel prevents the tunnel from being established.
- Routing mode: Most users should start with “Bypass LAN and mainland China addresses” or the default rules. Avoid importing complex rules unnecessarily.
- Local DNS: If enabling it causes problems, turn it off and test again. If pages won’t load even though the connection shows as successful, try changing the DNS settings.
- App proxy: If you’re proxying only selected apps, make sure your browser or target app is selected.
- Background restrictions: Allow v2rayNG to run in the background in your phone’s system settings, and remove any battery-saving restrictions on the app.
When troubleshooting, change just one setting at a time and test immediately. This makes it easier to tell what fixed the problem or caused it.
3. When should you switch network environments?
If multiple nodes time out and the subscription updates normally, but connections still fail, the issue may be with your current network. A low-risk approach is to switch networks rather than reinstalling your system or installing tools from untrusted sources.
- Switch from company, school, or shopping mall Wi-Fi to mobile data and test again. Public networks may restrict UDP, proxy connections, or specific ports.
- Switch from 5G/4G to your home Wi-Fi and test again. Some mobile networks may be unreliable with certain routes.
- Restart your router and toggle your phone’s network connection off and on. Once you’ve obtained a new IP address, try connecting again.
- Turn off other VPNs, accelerators, and packet-capture tools to avoid conflicts between local proxies.
The rule of thumb is simple: if the same node connects over mobile data but not on a particular Wi-Fi network, the Wi-Fi network is probably restricting it. If it fails on every network, the node may no longer be working or its configuration may be incompatible.
4. What if the connection still fails?
As a final step, try these three things: update v2rayNG to a newer version; delete the problematic node and reimport the subscription; or test with another client, such as Clash or sing-box. If a node using one protocol consistently fails while other protocols work, your current network may not support that protocol well. Switching routes is usually quicker.
In short, if v2rayNG won’t connect, work through these steps in order: “update the subscription → try another node → check permissions → switch networks.” This approach is low-risk, reversible, and ideal for quickly troubleshooting the issue yourself.