What should you do if v2rayNG won’t connect? This guide walks you through troubleshooting in order: check your phone’s network, confirm the node is working, verify your proxy settings, and review the logs. This can help you tell the difference between an app that won’t start, a node that times out, and a connection that works but won’t load webpages. Don’t keep reinstalling the app or rush to clear all your settings.
1. Check your phone’s network and environment
- Disconnect v2rayNG and use your browser to visit a website you can normally access directly. If it won’t load either, first resolve any Wi-Fi sign-in requirements, mobile data issues, or signal problems. Public Wi-Fi often requires you to sign in before you can use it.
- Switch between Wi-Fi and mobile data, then test the same node again. If it only fails on one network, check for restrictions on that network before changing the node settings.
- Turn off other VPNs, accelerators, or filtering tools that use the system VPN channel. Android generally allows only one such service to be active at a time. When v2rayNG starts, allow it to create a VPN connection.
- Set your system date, time, and time zone to automatic. A significantly incorrect time can cause certificate verification to fail. If the connection only drops after you lock the screen, check battery optimization and background activity restrictions.
2. Confirm that the node and subscription are still working
A successful subscription import doesn’t mean the nodes are currently available. Open subscription management and update the relevant subscription. Check for download or parsing errors. After updating, check the configuration list and make sure you’ve selected an actual node, rather than just adding the subscription URL.
If you’re using free nodes from this site or another source, check the publication date, expiration date, and usage instructions. Free resources may stop working or become temporarily congested. Try another recently updated node for comparison, but don’t rely on switching nodes as your only troubleshooting step.
If you imported a node manually, check that the link is complete and hasn’t been truncated by a messaging app or had spaces added to it. Compare the address, port, UUID, transport, and TLS settings with the provider’s instructions. Don’t omit any additional parameters required for protocols such as VLESS. Don’t “fix” the connection by disabling certificate verification.
3. It says connected, but webpages won’t load
- Check whether “proxy selected apps only” or a similar per-app rule is enabled, and make sure your browser is included. You can temporarily disable per-app settings while troubleshooting.
- Check the routing mode. Temporarily switch to global proxy mode and test the same webpage. If global mode works but split routing doesn’t, focus on the routing rules, then restore your usual mode after testing.
- Run a connection test in the app, then open a webpage to verify access. The test name may vary between versions, and a single latency result doesn’t prove that every website is reachable.
- If the logs show a domain resolution error, check the app’s DNS settings and see whether Android Private DNS or another DNS tool is conflicting. Note the original settings, then restore them to their defaults or adjust them according to the provider’s instructions.
4. Use the logs to pinpoint the issue—change one thing at a time
Open the v2rayNG logs, reconnect, and visit the target webpage once. Then check the latest error. A timeout usually means you should check the network path or whether the node is reachable. “Connection refused” may mean the target port isn’t serving connections. Certificate-related errors call for checking the time, server name, and node settings. Treat errors as clues and consider the results of testing a different network or node before drawing conclusions.
Change one setting at a time, and record the result after each test. If several trusted nodes fail on two different networks, back up your configuration before updating the client from the project’s official release channel. When asking for help, share the app version, network type, and redacted logs. Don’t post subscription links, UUIDs, or full node QR codes, as these could expose your access credentials.