This article addresses the issue of “what to do if v2rayNG won’t connect”: whether you have no internet after importing a node, it keeps spinning, shows a timeout, or it connects but webpages still won’t open, you can troubleshoot item by item using the checklist below. It’s suitable for ordinary Android users to follow step by step.
1. First, make sure the basic environment is working properly
Many connection failures are not caused by a broken node itself, but by abnormal phone network conditions, system permissions, or time settings. It’s recommended to complete the following checks first:
- Switch networks: change from Wi-Fi to mobile data, or test the other way around, to rule out restrictions on the current network.
- Turn off other proxies/VPNs: keep only one VPN app, v2rayNG, running at a time to avoid port and routing conflicts.
- Check the system time: go to your phone’s “Date & time” settings and enable automatic setting. A large time difference can cause TLS handshake failures.
- Allow VPN permission: when connecting for the first time, the system will pop up a VPN authorization prompt, and you must tap Allow.
- Disable battery-saving restrictions: in app management, allow v2rayNG to run in the background to prevent the system from killing it after it connects.
After completing these steps, reopen v2rayNG, tap the connect button in the lower-right corner, and then test whether your browser can access webpages.
2. Check whether the node or subscription is valid
If the basic environment is fine, the next step is to check the node configuration. v2rayNG supports protocols such as VLESS, VMess, Trojan, and Shadowsocks, and an error in any node detail may prevent it from connecting.
- For subscription users: open the menu in the upper-right corner, select “Subscription settings,” confirm that there are no extra spaces in the subscription URL, and then tap “Update subscription.”
- For manual import users: check whether fields such as address, port, user ID, transport protocol, TLS, SNI, and path are complete.
- QR code import: it’s recommended to scan the code again to avoid unclear screenshots or truncated copied content.
- For free node users: free nodes may expire or become congested, so you can test by switching to nodes in different regions or with different protocols.
This site compiles free node resources that can be imported, but node availability may change with network conditions, so it’s recommended to save multiple backup nodes at once.
3. Understand common error messages
The v2rayNG log is the key to identifying the problem. Tap the menu in the upper-left corner to enter “Logs,” and judge based on the prompts:
- timeout: usually means the node is unreachable, the network is blocked, or the port is inaccessible; try changing the network or switching nodes first.
- handshake failed: commonly caused by incorrect TLS, SNI, fingerprint, or system time.
- connection refused: the server port is refusing the connection, which usually means the node has expired.
- context deadline exceeded: connection timed out, possibly because the node is congested or the current network quality is poor.
If the log never shows any new content, the app may not actually be initiating a connection. You can restart v2rayNG, or clear the app cache in system settings and try again.
4. Recommended quick-fix process
- Update v2rayNG to a newer version to avoid old cores being incompatible with newer protocols.
- Update the subscription and choose a node with lower latency.
- Tap “Test all configurations with real connection” and delete nodes that are obviously unusable.
- In “Routing settings,” use the default rules first, and do not enable multiple complex traffic-splitting rules at the same time.
- If it still fails, enable logging, copy the error keywords, and then troubleshoot more specifically.
Finally, a reminder: do not install multiple VPN configuration tools from unknown sources at the same time, and do not casually import unknown links. If v2rayNG won’t connect, troubleshoot in the order of “network environment → node configuration → log errors → version and permissions,” and you can usually locate the problem quickly.