This article addresses common issues with “what to do when v2rayNG won’t connect,” including being unable to access the internet after importing a node, connection timeouts, being connected but unable to open webpages, and subscription update failures. Work through the checklist below to identify the cause. Most issues can be traced to the network environment, node details, client settings, or system permissions.
1. Check your login and network environment
Many connection failures aren’t caused by v2rayNG itself, but by issues with your phone’s network, time, permissions, or local proxy status. Start with these basic checks:
- Switch networks: switch from Wi-Fi to mobile data, or vice versa, to rule out network blocking, DNS issues, or restrictions on school or company networks.
- Check your system time: an incorrect time or time zone can cause TLS handshake failures. Turn on “Set time automatically.”
- Close other proxy/VPN apps: use only one VPN app at a time to avoid routing conflicts.
- Check v2rayNG permissions: the system will ask you to authorize VPN access the first time you connect. You must allow it. If you denied the request, restart the app and authorize it again.
- Test your regular internet connection: before connecting to a node, make sure your browser can open domestic websites.
If everything checks out, move on to troubleshooting the node and configuration. Don’t immediately reinstall the client repeatedly, as you could also remove configurations that were working.
2. Check that your nodes, subscription, and configuration are valid
v2rayNG relies on node details to connect. Invalid nodes, formatting errors, or expired subscriptions can all cause connection failures. Try the following:
- Update your subscription: open the subscription group and tap Update. Make sure there are no download or parsing errors.
- Switch nodes: test two or three nodes in the same subscription rather than judging by a single node.
- Check the latency test: long-press a node or use the test feature. If all nodes time out, the subscription may be unavailable or your current network may be blocking connections.
- Check that the protocol parameters match: VLESS, VMess, Trojan, and other protocols use different parameters. When copying a link, make sure you include fields such as uuid, port, security, sni, and path.
- Import the link again: if you copied a node manually, delete the old entry and reimport it from the complete share link.
This site collects free nodes that you can use for testing, but their availability may vary. If you can’t connect, try updating your subscription and switching nodes first.
3. How to handle common error messages
If v2rayNG displays “connection timed out,” the node may be unreachable, its port may be blocked, or your network environment may be restricted. Try switching networks and nodes first. If you see “TLS handshake failed” or a certificate-related error, check your system time, SNI, and TLS settings. If the app shows that you’re connected but webpages won’t open, there may be a routing or DNS issue.
In v2rayNG settings, check the following options:
- For routing mode, start with “Bypass LAN and mainland China addresses” or use the default rules. If you’re not familiar with the settings, don’t change them arbitrarily.
- Leave DNS settings at their defaults to start. If you’ve changed them before, restore the defaults and test again.
- Allow connections from LAN usually doesn’t need to be enabled. For regular phone use, leave it off.
- If per-app proxying is enabled, make sure apps such as your browser, Telegram, and YouTube haven’t been excluded.
4. Quick recovery steps
If you still can’t connect, follow these basic troubleshooting steps: close other VPN apps and restart your phone; open v2rayNG and delete any obviously invalid nodes; reimport your subscription; update it and select a node with relatively low latency; tap Connect in the lower-right corner, then test your connection in a browser.
Avoid changing several settings at once, or it will be difficult to determine what caused the problem. The safest approach is to change one variable at a time: switch networks first, then switch nodes, then restore the settings. If all nodes fail across multiple networks, the subscription or node source is probably no longer available, and you’ll need to switch to a new, working subscription.