This article addresses the question “What should I do if v2rayNG won’t connect?” Start with the safest steps that require the fewest changes: check your nodes, subscription, system network, and client settings. It also explains when to switch between Wi-Fi, mobile data, or a hotspot, making it easy for everyday users to follow along.
1. Start with basic, low-risk checks
If the connection fails, don’t rush to reinstall the app or change settings at random. First, check a few common causes. v2rayNG relies on node details, your phone’s network, system time, and client routing rules. An issue with any one of these can result in “connected, but webpages won’t load” or “latency test failed.”
- Open v2rayNG and make sure the selected node isn’t an empty configuration and that its address, port, and protocol look correct.
- Tap the menu in the upper-right corner and use “Test current service connection” or a similar test option to see if it times out.
- Check whether your phone can access domestic websites normally. If regular webpages won’t load either, troubleshoot your local network first.
- Make sure your phone’s time is set to update automatically. A significant time mismatch can cause TLS handshake failures.
- Turn off power-saving mode, data-management apps, and third-party firewalls, then try connecting again.
If you use a subscription link, update your subscription first. If you’re using free nodes provided by this site, they may also be temporarily unavailable, so try nodes using the same protocol or from a different region.
2. Check whether your subscription or node has expired
Many connection problems aren’t caused by v2rayNG itself. The node may have expired, be rate-limited, have a DNS resolution issue, or use an incompatible configuration format. A low-risk approach is to keep your existing configuration and copy or update it before switching nodes to test.
- Update your subscription: Go to the subscription group and update it manually to avoid using outdated nodes.
- Switch nodes: Try two or three nodes from the same subscription instead of repeatedly reconnecting to just one.
- Check the protocol: Configurations such as VLESS, VMess, and Trojan require client support. Older versions of v2rayNG may have compatibility issues.
- Import again: If fields are missing after importing a QR code or link, delete that configuration and scan or paste it again.
We recommend updating to a recent stable version of v2rayNG from your app store or the project’s release page. You can export a configuration backup first to avoid accidentally deleting a working node.
3. When to switch network environments
If the node works on someone else’s phone, or several nodes all fail for you, your current network environment may be the problem. Switching networks is a low-risk step that won’t change your node configuration and can help narrow down the cause.
- Switch from Wi-Fi to mobile data, close v2rayNG, reopen it, and try connecting again.
- If mobile data works but Wi-Fi doesn’t, the issue may be your router’s DNS, your broadband provider, or restrictions on a company or campus network.
- If Wi-Fi works but mobile data doesn’t, try toggling airplane mode to reconnect through a new network route.
- If you’re having trouble on public Wi-Fi or a company or campus network, try a personal hotspot or home network instead.
If the connection succeeds but websites won’t load, check the routing mode in v2rayNG settings. For everyday use, we recommend starting with the default rules to avoid accidentally setting all traffic to bypass the proxy or be blocked. If “Proxy only selected apps” is enabled, make sure your browser is selected.
4. Safe steps to try if the problem persists
As a last resort, try clearing the app cache, restarting your phone, turning off Private DNS, or testing with a different browser. Don’t install unofficial “accelerated” clients or share your node credentials with strangers who offer to check them for you. We recommend troubleshooting in this order: confirm your network is working → update your subscription → switch nodes → update the client → change network environments. This helps you avoid accidentally deleting your configuration while quickly identifying whether the problem is with the node, client, or current network.