This article addresses the common question, “What should I do if v2rayNG won’t connect?” If you can’t access websites after importing a node, keep getting timeouts, see a handshake failure, or have no internet access after connecting, work through the checklist below. It should help you quickly determine whether the issue is caused by the node, your network environment, the device’s time, DNS, or client settings.
1. Check that your basic environment is working
Many connection failures aren’t caused by v2rayNG itself, but by issues with your phone’s network or system environment. Before repeatedly deleting and reinstalling the app, check the following in order:
- Check your phone’s time: Open your system settings and enable “Set time/time zone automatically.” A significant time discrepancy can cause TLS handshake failures.
- Switch networks: Try switching between Wi-Fi and mobile data. Some campus, corporate, and hotel networks restrict proxy connections.
- Disable battery-saving and background restrictions: Android may kill v2rayNG’s background process, making it look connected even though traffic is being interrupted.
- Make sure your phone can access the internet: Disconnect v2rayNG and visit a local website or open your app store to rule out a local network issue.
If everything checks out, continue by checking the node and client configuration.
2. Check whether the node is working
The most common reasons v2rayNG won’t connect are an inactive node, an expired subscription, or an incomplete configuration. Here’s how to troubleshoot:
- Long-press a node in the node list and select “Test current configuration connection” or a similar test option. Check whether it times out.
- If you’re using a subscription, tap the menu in the upper-right corner and select “Update subscription” to make sure you’re not using outdated nodes.
- Test other nodes in the same subscription. Don’t keep trying to connect to just one node.
- If the node came from a free share, it may be temporarily unavailable. Try again later, or choose another configuration from our free nodes page.
Keep in mind that free nodes are heavily affected by routing, load, and regional network conditions, so their availability can change.
3. Check your v2rayNG client settings
If the node is working but your phone still can’t open websites, check the client settings:
- Make sure you’ve tapped the connect button in the lower-right corner and that the VPN icon appears in the status bar.
- Open “Settings” and make sure the routing mode isn’t set to block all traffic. Most users can start with “Bypass LAN and mainland China addresses” or the default rules.
- You generally don’t need to enable “Allow connections from the LAN” unless you want to share the proxy with other devices.
- If per-app proxying is enabled, make sure apps like your browser, Telegram, and YouTube haven’t been excluded from the proxy.
- Try disabling “Mux” or switching transport compatibility options. Some nodes have unstable Mux support on certain networks.
After changing settings, disconnect and reconnect rather than simply refreshing the webpage.
4. Use the logs to identify the error
v2rayNG’s built-in logs can be very useful. When a connection fails, open “Logs” from the menu and look for the following messages:
- timeout, i/o timeout: Usually means the node is unreachable, the network is blocking the connection, or the port is restricted.
- TLS handshake failed: Check the time, domain, SNI, or whether the node is inactive.
- invalid user, failed to read response: The UUID, encryption, or protocol parameters may not match.
- Connection succeeds but webpages won’t open: Check DNS, routing mode, and per-app proxy settings first.
If you scanned a QR code or imported a link, it’s generally best not to change the parameters manually. A single incorrect field can prevent the connection from working.
5. What if it still won’t connect?
As a last resort, try these steps in order: update v2rayNG to a recent version; delete the problematic node and reimport the subscription; restart your phone; switch network environments; and test another set of nodes. If all nodes fail, the current network is probably imposing strict restrictions, or the subscription source is unavailable. Keep one principle in mind while troubleshooting: change only one variable at a time. For example, change only the node without also changing DNS and routing. That makes it easier to identify the actual cause.