V2Ray FAQ

Start by checking where the problem occurs: for installation failures, check your system and architecture; for an empty list, check subscription import; if the client starts but webpages won’t load, check the proxy entry point and routing. Covers v2rayN, v2rayNG, and v2flyNG.

Fundamentals

What are clients, cores, and nodes?

The client manages configuration, the core handles connections and routing, and nodes provide remote connection details. v2rayN is a desktop client; v2rayNG uses the Xray core, while v2flyNG uses the V2Fly core. Installing a client does not mean you have a working node configured. If the list is empty, check the import first. If entries are listed but the service fails to start, check the core logs. These issues require different troubleshooting steps, so identify which layer is failing before reinstalling or switching clients.

What’s the difference between a subscription link and a single-node share link?

A subscription link points to a list of configurations that can be retrieved again, while a single-node share link describes just one connection. Add a subscription URL to a subscription group, then update it. Import a single-node link from the clipboard or a QR code. Updating a subscription syncs changes made by the provider; individually imported entries do not update automatically. If you only have the provider’s account page, look for a dedicated subscription link—don’t use the login page as the subscription URL.

Are system proxy and global routing the same setting?

No. The system proxy determines whether apps that follow the setting send requests to the local proxy. Global routing determines which outbound route is used for requests that have already reached the core. Selecting global routing does not automatically capture traffic from apps that ignore the system proxy. Conversely, with the system proxy enabled, custom rules may still send requests directly. To verify, make a request from a browser that follows the system proxy, then check whether the client logs show that request and its outbound route.

Can protocol, transport, and TLS settings be changed independently?

These are separate fields, but the connection settings must match the server configuration. VMess and VLESS are protocols, WebSocket is a transport, and TLS is a security layer option. When using a configuration from a provider, don’t replace any of these with an option that merely seems faster. For handshake errors, check the server address, port, transport type, and server name. If the configuration came from a subscription, update it first, then compare the old and new entries.

Further reading: Protocol, Core, and Routing Terminology

Installation and Setup

Which v2rayN version should I choose: Desktop or WPF?

For a first install, choose the Desktop version. If you prefer the classic interface, choose the WPF version for Windows. Check your processor architecture in the system’s About page, then verify that you have the right installer. If the client won’t open, note the system error first. If a runtime is missing, install the one specified by the package rather than changing your subscription or nodes. When trying both versions, don’t enable the local proxy in both at once: they may conflict over the listening port, or one may affect the system proxy when you exit it.

Which Android package should I choose: arm64 or universal?

If your device supports arm64-v8a, choose arm64. If you’re unsure about its architecture, choose universal. Universal packages usually include native libraries for multiple architectures, so they’re larger, and they won’t solve problems caused by an outdated Android version or installation restrictions. If you can’t install over an app with the same name, check whether the installer reports a signature mismatch, then verify the download source. Don’t uninstall the existing app first: that could erase local settings. Back them up on your device.

Why are no nodes showing up after importing a subscription?

Make sure you saved the subscription URL and ran an update, then open the relevant group to check the list. If the URL is reported as invalid, copy the full link again, remove any leading or trailing spaces, and keep its query parameters. If the request succeeds but parsing fails, check that the subscription’s output format is supported by your client and core. A login page or expiration notice is not a node list, even if the request returns a success status. When checking logs, record only the time and error type; don’t share the full subscription URL.

What should I do if TUN or Android VPN reports insufficient permissions?

On desktop, check the logs to see whether access was denied, a virtual network adapter could not be created, or a route could not be added. Follow the client and system prompts to use an account with the required permissions; don’t disable system protection. On Android, approve the system VPN request the first time you start the app. If another VPN is active, disconnect it before trying again. On a device managed by an organization, first check whether this feature is allowed. If you only need to test a browser, you can verify the node using your existing system proxy settings.

Further reading: Subscription Import, Connection, and Verification Guide

Usage Tips

Should I use a TCP test or a real latency test?

A TCP test usually only shows whether the client can reach the server port; it doesn’t confirm that the protocol handshake or forwarding works. A real latency test sends a request to a test URL through the selected node, making it more representative of actual use. Results still depend on the target, network, and current load. When comparing nodes, use the same test URL and network, and retest outliers. A timeout only means that request didn’t complete in time; it doesn’t prove the node is down.

How do GeoSite and GeoIP routing rules differ?

geosite:cn matches a set of domains in the rule database, while geoip:private matches a set of private IP addresses. They are not interchangeable. The core checks routing rules in order and uses the first match, so put specific exceptions before broader rules. If a domain rule doesn’t match, check the logs to see whether the target is a domain or an IP address. For IP-based matching, also check the address resolution strategy. After changing rules, retest with the same target.

Why can’t I open just a few websites, and how can I tell if DNS is the problem?

Keep the current node and routing settings unchanged. Open the affected site and a known working site, then compare the logs for the same time period. If domain resolution fails, check which resolution path the system, browser, and core are each using; the browser’s secure DNS may differ from the system setting. If the logs show successful resolution followed by a connection or certificate error, investigate that stage instead. Don’t change every DNS option at once.

Should I set subscriptions to update as often as possible?

No. First confirm that a manual update succeeds, then set the interval based on the provider’s guidance and how often nodes change. Short intervals only increase the number of requests and may cause update failures if the provider rate-limits them. Scheduling options vary between clients and versions, so check the subscription group or relevant settings in your current version. After updating, check the selected entry to make sure you aren’t still testing an old node that has been removed from the subscription.

Further reading: Updating and Using GeoIP and GeoSite Rule Databases

Troubleshooting

When a node times out, should I check the client or the server first?

First determine whether one node is timing out or all nodes are timing out on the same network. If only one node has a problem, compare it with working nodes in the same group, then check its address, port, and transport settings. If all nodes fail, make sure your device has a working network connection, the core starts correctly, and the local proxy port is listening. The test target may also be temporarily unreachable, so try a known working target. If it still fails, use the logs to distinguish a connection timeout from a handshake failure.

The client says it’s connected, but webpages won’t load. What should I do?

A connected status doesn’t mean web requests are successfully passing through the proxy. On desktop, reproduce the issue in a browser that follows the system proxy. On Android, check first whether per-app proxy settings exclude the app. If the logs show no matching request, check whether traffic is reaching the client. If the request uses an unexpected outbound route, check the routing order. If the route is correct but the request fails, investigate DNS, connection, or certificate errors. Change one setting at a time and retest the same URL.

Why doesn’t system proxy work in some apps after I enable it in v2rayN?

Use a browser that follows the system proxy as a control. If it works but the target app doesn’t, check whether that app uses its own proxy settings or connects directly. If the browser also fails, confirm that the system proxy address and port match the client’s current listening address and port, and make sure the core is running. If you changed the local port, update any apps where you entered the proxy settings manually. If the logs report that the port is in use, identify the process using it before deciding whether to close the old instance or choose another port.

A subscription that used to work suddenly won’t update. How do I troubleshoot it?

Keep your existing nodes and check the type of error first. For a 401 or 403 response, check whether the subscription expired or its access permissions changed. For domain resolution or certificate errors, check DNS and the system time. If updates use the current proxy and the current node is no longer working, try updating without the proxy if the subscription URL allows direct access; this can rule out a dependency loop. If the update reports success but no new nodes appear, check the group, response format, and parsing logs. Don’t delete the existing group first.

Further reading: Step-by-Step Troubleshooting for Subscription Update Failures, How to Find and Fix Local Port Conflicts

Download Clients