This article addresses common questions about what to do when v2rayNG won’t connect, including no internet after importing nodes, websites not loading despite a successful connection, failed latency tests, and subscription update failures. Use the checklist below to troubleshoot the issue step by step. It’s suitable for everyday Android users looking to quickly identify the cause.
1. Check your basic network environment first
Many connection failures aren’t caused by a faulty client, but by problems with your phone’s network or system environment. Before troubleshooting, check the following:
- Make sure your phone is connected to Wi-Fi or mobile data and can access websites in China normally.
- Turn off other VPNs, accelerators, and data-saving tools to avoid conflicts between multiple proxies.
- Check that your system time is set to sync automatically. A significant time difference can cause some nodes to fail the handshake.
- Make sure you’re using a recent version of v2rayNG. Older versions may not support some VLESS, Reality, or TLS configurations.
If you’ve just switched from another app, try restarting your phone’s network connection, or turn on Airplane mode for 10 seconds and then turn it off.
2. Check whether your nodes and subscription are valid
Whether v2rayNG can connect depends largely on whether the node information is correct. Free nodes in particular often stop working because they expire, are restricted, or have been reconfigured.
- Open v2rayNG, long-press the current node, and select “Test current service connection” or a similar test option.
- If the latency test fails, try another node instead of repeatedly attempting to connect to the same one.
- If you use a subscription, open the subscription settings, tap Update subscription, and check that no download error appears.
- Make sure the node protocol and configuration are complete. Check that the address, port, UUID, encryption, transport method, TLS/SNI, and other details are all present.
We compile free nodes that you can import, but free nodes are generally less reliable than nodes you use over the long term. If one fails, try switching between several nodes.
3. Check key v2rayNG settings
Some nodes work, but unsuitable client settings can still leave you “connected but unable to access the internet.” Check the following:
- Routing mode: If you’re new to the app, start with “Bypass LAN and mainland addresses” or use the default rules.
- Local DNS: If you can connect but websites won’t load, try switching to system DNS or enabling remote DNS.
- Allow LAN connections: This generally doesn’t need to be enabled for regular phone use, and may cause interference.
- Per-app proxy: If per-app proxying is enabled, make sure your browser or target app is selected.
After connecting, check whether a VPN icon appears at the top of your phone’s screen. If it doesn’t, the proxy hasn’t actually started. If the icon is there but you still have no internet, the issue is usually related to the node, DNS, or routing rules.
4. How to handle common errors
When something goes wrong, don’t rely only on the “Connection failed” message. Check the logs for more specific details. Here are some common errors and what to try:
- timeout: Usually means the node is unreachable, the network is blocking the connection, or the server is busy. Try another node.
- connection refused: The port may be unavailable, which usually means the node is no longer working.
- tls handshake failed: Check that the TLS, SNI, and Reality parameters are complete, or try a different client version.
- no such host: The domain name could not be resolved. Try switching networks or changing your DNS settings.
If all nodes fail, first check your phone’s environment: turn off power-saving mode, remove background restrictions, and allow v2rayNG to use mobile data and background network access.
5. Recommended troubleshooting order
The quickest order is to confirm that your domestic network is working, update v2rayNG, update your subscription, test several nodes in a row, and then check DNS, routing, and logs. Don’t start by changing a lot of settings at once, or it’ll be difficult to tell which change caused the problem.
In short, v2rayNG connection failures usually have more than one possible cause. Troubleshoot in this order: network environment, client version, subscription and nodes, routing and DNS, then error logs. This will help you identify most issues. If the problem persists, note the error logs, node protocol, and current network environment so you can investigate further.