This article addresses the common question, “What should I do if v2rayNG won’t connect?” Follow this checklist to troubleshoot your phone’s network, system settings, node details, subscription updates, and log errors. It can help you quickly determine whether the problem is with your device, an inactive node, or an incorrectly imported configuration.
1. Check your network environment first: the node may not be the problem
If v2rayNG won’t connect, don’t keep tapping Start. First, make sure your phone’s network environment is working properly. A weak connection, system restrictions, or an incorrect clock can all cause connection failures.
- Try a different network: If you’re on Wi-Fi, switch to mobile data; if you’re using mobile data, try another Wi-Fi network. Some public Wi-Fi, campus, and workplace networks may restrict proxy connections.
- Disable battery-saving and background restrictions: Go to your phone’s system settings, find v2rayNG, and allow it to run in the background and start automatically. This helps prevent the system from stopping it after you connect.
- Check your system clock: Set the date and time to “Automatic.” A significant time difference can cause a TLS handshake to fail.
- Turn off other proxies or VPNs: Don’t run multiple VPNs, accelerators, or VPN-based ad blockers at the same time, as they can cause port conflicts.
- Make sure your phone can open regular websites: If you can’t even access domestic websites, troubleshoot your phone’s network first.
2. Check that your nodes and subscription are working
If your network environment is fine, check the nodes next. Free nodes often become unavailable due to maintenance, congestion, or expiration, so it’s a good idea to have several nodes to test. We also compile information about free nodes on this site. Check whether they actually connect before using them; their long-term stability isn’t guaranteed.
- In the v2rayNG node list, long-press or tap a node and run “Test real connectivity” or “Test latency.”
- If all nodes fail, first check whether your subscription link has expired or was copied in full.
- Tap the menu in the top-right corner, select “Update subscription,” then select a node and reconnect.
- If only one node fails, it’s most likely temporarily unavailable. Simply switch to another node.
When importing a node, note that protocols such as vmess, vless, trojan, and ss use different formats. A QR code or link with missing parameters can also cause a connection failure. Don’t manually remove or edit fields such as the port, UUID, host, path, or security in the link.
3. Use the logs to identify common errors
When v2rayNG won’t connect, checking the logs is more reliable than guessing. Open v2rayNG, go to the logs page, connect once, and check the last few lines.
If you see “timeout” or “i/o timeout,” the network probably can’t reach the node. Try a different network or node. If you see DNS-related errors, try switching DNS in v2rayNG settings or restarting your phone’s network. If you see “certificate,” “TLS,” or “handshake failed,” common causes include an incorrect system clock or mismatched TLS settings on the node. Try importing the subscription again instead of using an old cached configuration.
Sometimes v2rayNG shows as connected, but your browser can’t open external websites. In that case, check “Routing” or “Per-app proxy.” If per-app proxy is enabled, make sure your browser is selected. If only certain apps are routed through the proxy, apps that aren’t selected won’t use v2rayNG.
4. Recommended quick-fix checklist
- Restart v2rayNG: disconnect, then reconnect.
- Switch between Wi-Fi and mobile data to rule out network restrictions.
- Update your subscription and test 2–3 different nodes.
- Check your phone’s clock, background permissions, and battery-saving settings.
- Review the logs and look for keywords such as timeout, DNS, and TLS.
- If the problem persists, delete the old configuration and reimport the subscription or QR code.
In short, if v2rayNG won’t connect, don’t focus on just one node. Troubleshoot in this order: network environment, system permissions, subscription and nodes, log errors, and reimporting. This usually helps you find the cause quickly. If you use free nodes, keep several alternatives and update your subscription regularly so an inactive node won’t interrupt your connection.