V2Ray Troubleshooting

First, identify where the failure occurs. For import issues, check the subscription request. For startup failures, check the core logs. If the client connects but you can't access the internet, check whether the app is using the proxy.

Basics

Which should you choose: v2rayN, v2rayNG, or v2flyNG?

Choose v2rayN for Windows, macOS, and Linux. On Android, v2rayNG with the Xray core is usually the first choice; consider v2flyNG only if your configuration provider specifically requires the V2Fly core. Before switching clients, check the node's protocol, transport, and security layer. Importing the same subscription only confirms that the client can read it; it doesn't mean the current core supports every node.

What's the difference between a subscription URL and a single-node link?

A subscription URL retrieves a list of nodes. You usually add it in the subscription group settings and then update the group. A single-node link describes one connection and is usually imported from the clipboard. If you receive an account page, find the subscription URL clearly labeled on that page; don't add the login page to a group. Subscription URLs may contain access credentials, so redact the full URL and query parameters before sharing screenshots or logs.

Does system proxy mode route the same traffic as TUN mode?

No. System proxy settings mainly affect apps that read them. TUN uses a virtual network interface to receive traffic routed to it by the operating system, and can also cover some apps that don't use system proxy settings. TUN doesn't send every request through the proxy: client routing rules may still send traffic directly. When troubleshooting, enable only one mode at a time so you can distinguish between the two traffic paths.

Does the client showing as started mean the node is working?

No. A started status usually means the core process is running or an Android VPN session has been established. The remote handshake and connection to a website often don't happen until a request is made. Select a node, make a real request to a known-working site, then check the logs from the same time. A tray icon or VPN indicator alone can't tell you whether an app is using the proxy or whether the remote connection succeeded.

Setup

Which Android package should I choose: arm64 or universal?

Choose the arm64 package if both your device and Android system support arm64-v8a. If you're unsure which app architecture your system supports, start with the universal package. A 64-bit-capable chip doesn't necessarily mean the device runs a 64-bit version of Android. The universal package usually includes components for multiple architectures and may be larger; it doesn't remove the need to check the minimum Android version or permissions for installing apps from your chosen source.

What should I check first if my first subscription import fails?

First, determine whether the request failed or the response couldn't be parsed. If the request failed, check that the URL was copied in full, has no extra spaces, and that your current network can reach the subscription service. If you get an unauthorized or forbidden response, check your account status and whether the link has changed. If the request succeeds but no nodes are imported, make sure the response is a subscription format supported by the client—not a login page, error page, or single-node link.

What should I do if v2rayN closes immediately after launch?

First, check that the package matches your system architecture, then review the startup log or system error message. If a runtime is missing, install the one required by your chosen build. If writing is denied, make sure the actual configuration directory is writable. If the issue started after an upgrade, back up your configuration and test a clean setup in a separate directory. Don't delete your existing subscriptions or routing rules.

What should I do if TUN reports insufficient permissions?

Check whether the log reports a failure to create the virtual network interface or to add system routes. On Windows, restart as administrator if the client prompts you to. On macOS and Linux, grant the required permissions to the relevant components as instructed by your build. On Android, approve the system VPN connection request and check whether another VPN is already using the session. If your device is managed by an organization, ask your administrator about its policies; don't disable system protections to troubleshoot.

Tips

How can I confirm that routing rules are working?

Choose a target domain, confirm that the expected routing configuration is active, then make a new request and check the matched rule or outbound entry. If the result differs from what you expect, check whether a broader rule earlier in the list matched first, and whether the app supplied a domain or an already-resolved IP address. Change one rule at a time and keep a copy of the original configuration so you can compare results and roll back.

How do node latency tests differ from actual browsing results?

Start by checking the test type. A TCP test only checks whether a connection can be made to a specified port; it doesn't verify proxy authentication, transport security, or whether a webpage loads. A test sent through the proxy is closer to a real request, but still depends on the test URL and its routing. If test results differ from what you see in a browser, test the actual destination with the same node and confirm both requests used the same proxy entry point.

What else should I update after changing the local listening port?

Restart the core and confirm that it's listening on the new port. Then update any browser extensions, terminal proxy environment variables, and app proxy settings that still use the old port. If the client previously set the system proxy, reapply that mode and check the address in your system settings. Don't swap the HTTP and SOCKS ports. If the core uses a mixed port, enter it according to the proxy type supported by the app or tool connecting to it.

What information should I include when reporting an issue?

Include the client and core versions, operating system, proxy mode, and the steps that trigger the issue. Keep a few log lines from before and after the failure, and note whether it started with a fresh install, after an upgrade, or only on a particular network. Redact subscription URLs, node links, authentication fields, and any addresses you don't want to share publicly. You usually don't need to send your full configuration; the error type and sequence of events are more useful for diagnosis.

Troubleshooting

How can I narrow down the cause of a V2Ray node test timeout?

Using the same client, network, and test method, compare a known-working node with the one that times out. If only some nodes time out, check their addresses, ports, transport settings, and service status. If every node times out, first check that your local network and core are working, then review the logs from the test. If the logs show a certificate or authentication error, address the relevant settings rather than simply increasing the timeout.

The client connects, but I still can't access the internet. What should I check first?

Temporarily disable the proxy and check that a site you can normally access directly is reachable. Re-enable the proxy, retry the same address, and check the core logs from that moment. If there's no request in the logs, check whether the app is using the proxy and whether the relevant log level is enabled. If a request appears but DNS resolution fails, check the DNS path. If an outbound connection appears but fails, check the routing choice and remote handshake. Change one setting at a time.

Why does the system proxy work differently in my browser and terminal?

First, check that the system proxy address matches the client's actual listening address. Your browser may follow system settings, or an extension or separate proxy setting may override them; temporarily disable related extensions and restart the browser to test. Terminal programs may not read system settings, so check whether the command supports proxy environment variables and verify the address, port, and protocol in the current session. One working app doesn't mean the whole system is using the proxy.

Why did a subscription update fail when my existing nodes still work?

Your existing nodes come from a previously saved configuration, so they may still connect even when the subscription service is currently unreachable. Keep the existing group, run a manual update, and check the error. If domain resolution fails, check DNS. If the request times out, check the network path used for the update. If access is unauthorized, check whether the link has been rotated or the account has expired. If manual updates work but scheduled ones fail, check the group's update toggle and interval, and whether the client is running.