This article addresses a common problem: after importing a node or subscription into v2rayNG on an Android phone, you tap Connect but still can’t access the internet, latency tests fail, or the app stays stuck on “Connecting.” Follow these checks in order. They’re suitable for everyday users and don’t require any server configuration knowledge.
1. Check your phone and sign-in environment
Many cases of “What should I do if v2rayNG won’t connect?” aren’t caused by a faulty app, but by network issues, missing permissions, or an incorrect system clock. Start with these basic checks:
- Switch networks: switch from Wi-Fi to mobile data, or vice versa, to rule out restrictions on your current network.
- Turn off other VPNs: Android usually allows only one VPN connection at a time. First disconnect any accelerators, ad blockers, or work VPNs.
- Check the system clock: enable “Set time and time zone automatically.” An incorrect time can cause TLS handshake failures.
- Check permissions: when connecting for the first time, allow v2rayNG to create a VPN connection. Don’t tap Cancel.
- Restart your phone: Android’s network stack can occasionally misbehave after running in the background for a long time. Restarting can rule out many issues.
If you’re using a subscription from a VPN service or one of the free nodes provided on this site, also make sure the subscription link was copied correctly, without missing characters or extra spaces, and that the node is still available.
2. Check that the node was imported correctly and its settings are valid
Open v2rayNG, long-press the current node, and open the edit screen. Check that fields such as the address, port, user ID, encryption, transport, TLS, and SNI are present and haven’t been changed accidentally. For most users, the safest option is to avoid editing node settings manually and instead update the subscription or import the complete share link.
- For a subscription: tap “Update subscription” in the top-right corner, then select a new node to test.
- For a vmess/vless link: copy the complete link again and select “Import from clipboard.”
- If importing a QR code fails: increase your screen brightness or import using a link instead.
- If only one node fails: try other nodes in the same subscription rather than repeatedly changing the client settings.
Before connecting, you can tap “Test all configurations for a real connection” or a similar test option. Keep in mind that a failed latency test doesn’t necessarily mean the node is unusable, but a failed real connection test usually indicates a problem with the node, network, or settings.
3. What to do if the connection succeeds but websites won’t load
Sometimes v2rayNG shows that it’s connected, but your browser still can’t open websites. In this case, check your routing and DNS settings first. In v2rayNG settings, make sure options such as “Enable local DNS” and other DNS settings haven’t been changed to an unavailable address. For routing, start with the default or global mode to test the connection. Once you can access the internet, switch back to a mode such as bypassing mainland China addresses.
You can also try clearing your browser cache or testing with Chrome, Edge, or Firefox. Some apps cache their previous network state, so try closing and reopening them. If only certain websites won’t load, the cause may be restrictions imposed by those sites, the node’s exit route, or DNS resolution—not necessarily a fault with v2rayNG itself.
4. Quickly identify the source of the problem
Follow this order to save time: switch networks, try another node, update the subscription, and then reinstall the client. If all nodes fail on every network, your subscription may have expired, the links may no longer work, or your client may be outdated. Update v2rayNG from a trusted source, then import your subscription again.
Keep two things in mind when troubleshooting: first, don’t run multiple proxy tools at the same time; second, don’t repeatedly change advanced settings at random. Most connection problems can be resolved by updating the subscription, switching nodes, correcting the system clock, or changing networks. If the problem persists, take a screenshot of the key error messages in the log and continue troubleshooting TLS, DNS, and network blocking.