This article addresses the common question, “What should I do if v2rayNG won’t connect?” Whether you’ve just imported a node, a subscription stopped working after an update, or your phone suddenly can’t access the internet through the proxy, use the checklist below to troubleshoot each item and pinpoint the cause with as few steps as possible.
1. Check your phone’s network and system settings
Many connection failures aren’t caused by a faulty node, but by an issue with your local network environment. Before troubleshooting, close v2rayNG, then check the following in order:
- Make sure your phone can access domestic websites or apps—for example, open a frequently visited website in your browser.
- Switch between Wi-Fi and mobile data to test the connection. Some school or corporate networks restrict proxy connections.
- Close other VPNs, connection boosters, and proxy apps to avoid port or routing conflicts.
- Check that your system clock is accurate. A significant time discrepancy can cause TLS handshakes to fail.
- If your Android device has battery saver or background restrictions enabled, allow v2rayNG to run in the background.
If switching networks makes the connection work right away, the original network may be restricted. If none of your networks work, continue by checking your configuration.
2. Check that your nodes and subscription are valid
Open v2rayNG and long-press the current node. Check that the address, port, UUID, transport protocol, TLS, SNI, and other fields haven’t been accidentally deleted or changed. Most users are better off importing nodes using a subscription link to avoid manual entry errors.
- Tap “+” or the menu in the upper-right corner, then choose to import from the clipboard, scan a QR code, or add a subscription.
- After importing, tap “Test connection” or try switching between multiple nodes.
- If your subscription hasn’t been updated in a while, open the subscription settings and tap “Update subscription.”
- The free nodes provided on this site can be used for temporary testing, but they may stop working as the number of users or the status of the route changes.
If only one node fails, that node is probably unavailable. If all nodes fail, the issue is more likely related to the client settings, DNS, or network environment.
3. Check common v2rayNG settings
Open the menu in the upper-left corner of v2rayNG and check a few key options under “Settings.” If you’re new to the app, use the default routing mode or “Bypass LAN and mainland addresses.” Don’t switch to global direct mode without a specific reason. For DNS, try the app’s built-in DNS to avoid domain resolution issues caused by DNS poisoning from your carrier.
Pay attention to the status at the top while connecting. If it shows as connected but webpages won’t load, there may be a routing or DNS issue. If it disconnects immediately after starting, the node parameters may be incorrect. If it keeps waiting for a response, the network may be blocking the connection or the server may be unreachable. In these cases, check the v2rayNG logs and look for messages such as timeout, handshake failed, or connection refused.
4. Quick fixes for common symptoms
- Timeout message: Switch networks or nodes, and start by testing nodes in different regions or using different protocols.
- Certificate or handshake error: Check your system clock, TLS, SNI, and domain name.
- Connected but webpages won’t load: Switch routing modes, try a different DNS, and restart your browser.
- Subscription imports with no nodes: Check that the subscription link is complete and opens in a browser; recopy it if necessary.
- App can’t start a connection: Update v2rayNG to a newer version, or clear the configuration and import it again.
Finally, keep at least two working nodes as backups. If v2rayNG won’t connect, don’t keep reinstalling the app. Troubleshoot in this order: network environment, node availability, client settings, and log messages. This will usually help you find the problem faster.