HELP / FAQ
v2rayN FAQ & Troubleshooting
Find the right setting for your issue, from choosing a client and importing subscriptions to connection problems. Each answer starts with what to check and identifies the fields to compare.
01 / Basics
Understand clients, cores, and protocols
The interface manages settings; the core handles connections. Learn what each does before deciding where the problem lies.
What are v2rayN, V2Ray, and Xray?
v2rayN is a desktop GUI client for managing server lists, subscriptions, and proxy settings. V2Ray usually refers to the Project V ecosystem and its proxy tools. Xray is one of the cores a client can use. The GUI and core have separate roles: after you select a server and configure routing in v2rayN, the selected core handles the connection. When troubleshooting, first determine whether the issue is with the GUI settings, core startup, or server connection.
Which client should I use on Windows, macOS, Linux, or Android?
For Windows, macOS, and Linux, start with v2rayN and choose the package that matches your operating system and processor architecture. On Android, v2rayNG uses the Xray core; for an Android client with the V2Fly core, consider v2flyNG. A client does not provide server settings: after installing it, you still need to import a working subscription or enter the parameters supplied by your server provider. The downloads page lists separate options for all four platforms.
How do VMess, VLESS, and transport security relate?
VMess and VLESS are protocol options in a server configuration. Transport security is a separate set of settings that must also match the server. After importing a node, don't assume the connection is fully configured just because the protocol name matches. Check the address, port, user ID, transport protocol, and transport security as well. For a VLESS node using REALITY, enter the SNI, Fingerprint, PublicKey, ShortId, and other fields exactly as provided by the server.
Can you freely switch between the Xray and V2Fly cores?
Don't switch cores based only on a node's name. Xray and V2Fly share ecosystem roots, but their feature support and configuration fields are not identical. For example, before using a REALITY configuration, confirm that the client’s core supports it. If a node stops starting after you switch cores, check the client log for unsupported fields or parsing errors, then compare the server configuration and choose a compatible core. Avoid changing several parameters at once.
02 / Installation & Setup
Packages, subscriptions, and server fields
If an import fails, first identify the link type. When adding a server manually, use the parameters provided by the server.
Which Android package should I choose: arm64 or universal?
Most newer Android phones use 64-bit ARM processors, so arm64 is usually the best choice. If you don't know your device architecture or the arm64 package won't install, try the universal build. Package architecture affects whether the app runs on your device; it doesn't change subscriptions or node protocols. If installation still fails, check your Android version and available storage, then make sure you downloaded the package for v2rayNG or v2flyNG as intended.
What should I check if v2rayN can't import a subscription URL?
First make sure you copied a subscription URL, not a share link for a single node, and check for spaces at either end. Add the URL under Subscription Group Settings in v2rayN and save it before updating the subscription. Don't paste it into the server address field in the server editor. If fetching fails, open the URL in a browser to see whether it's still accessible, then check the client log for request errors. If the subscription content isn't recognized, ask the subscription provider which format it returns.
Which fields should I check when adding a VLESS server manually?
Open the server editor in v2rayN. Enter the address, port, and user ID from the server details, then check flow control, encryption, transport protocol, and transport security. If the server uses REALITY, enter the SNI, Fingerprint, PublicKey, and ShortId exactly as provided; don't guess these values. Save the server, select it, then enable the system proxy or the mode you need. If fields don't match, compare each one against the original server configuration.
What should I do if a v2rayN subscription update fails but the old nodes are still there?
Seeing the old nodes only means a previous list is saved locally; it doesn't mean the latest update succeeded. Check whether the subscription URL in the group has expired and whether your current network can reach it. Then review the update message and logs to distinguish a connection timeout, access denied, or content parsing error. Don't delete the old group yet. If the URL opens in a browser but the client can't parse it, ask the subscription provider whether the returned content uses a supported format.
03 / Using v2rayN
Proxy modes, routing, and DNS
First check how traffic reaches the client, then review routing rules and domain resolution. Different toggles control different modes.
How do I enable the system proxy in v2rayN?
Select the node you want in the server list and make sure the client core is running. Then choose the appropriate proxy state from v2rayN's System Proxy menu. The system proxy is for apps that follow the operating system's proxy settings; it doesn't automatically route every program through the client. After switching it on, test with a browser. If an app still connects directly, check for its own proxy settings and consider whether it needs TUN mode.
How do I fix a permissions error in v2rayN TUN mode?
TUN creates a virtual network interface and usually requires more permissions than the standard system proxy. Follow the permission prompt from the client and grant the access required by your operating system, or launch the client with appropriate permissions, then enable TUN again. If it still fails, check whether another virtual networking tool is using the interface and review the client log for the specific error. TUN and system proxy are separate settings. If you only need to proxy browser traffic, test the node with the system proxy first.
Should I use routing rules or global proxy?
Use rule mode for everyday split routing by domain or address. To check whether a node can connect at all, temporarily switch to global proxy and compare the results. Global proxy reduces the effect of routing rules on the test, but it won't fix incorrect server parameters. If a site behaves unexpectedly in rule mode, check which rule matches and its order, then confirm whether the traffic is proxied, direct, or blocked before editing the relevant rule. Switch back to the mode you need when testing is complete.
Should DNS and FakeDNS both be enabled?
Not necessarily. DNS settings determine how domains are resolved and which upstream servers are used. FakeDNS can return a virtual address first, then work with traffic sniffing to recover the domain name; it's commonly used in TUN setups that need to capture more traffic. If DNS works normally with the system proxy, there's no need to enable FakeDNS just to turn on more options. If local network devices or specific apps become inaccessible, disable FakeDNS for comparison, then check DNS upstreams, sniffing, and routing.
04 / Troubleshooting
Timeouts, no internet, and apps bypassing the proxy
Narrow down the issue in order: local network, server connection, proxy status, routing, and DNS. Keep the client logs for reference.
In what order should I troubleshoot a node connection timeout?
First confirm that your local network is working, then check the node address and port and whether the server is still available. Next, verify the protocol, user ID, transport protocol, and transport security, paying particular attention to changes after a subscription update. A test only reflects that connection attempt; one timeout doesn't mean every node in the group is down. Compare with another known-working node. If all nodes time out, check whether the core started and look for the first connection error in the client log.
The node is connected, but web pages won't load in my browser. What should I do?
First confirm that the intended node is selected in v2rayN, the core is running, and the system proxy state matches how your browser connects. Test several domains to see whether nothing loads or only certain sites are affected; for specific sites, check routing and DNS first. If no pages load, temporarily try global proxy for comparison and check the client log for connection or resolution errors. Don't change proxy, routing, and DNS settings all at once, or it will be hard to tell what fixed the issue.
Why isn't an app using the proxy even though the system proxy is on?
Some apps ignore the operating system's proxy settings or have their own proxy address configured. First use a browser to verify that the system proxy works, then check the app's network settings. If the app only supports direct connections, try TUN mode if appropriate. If the browser also bypasses the proxy, return to v2rayN and check the system proxy and core status, then see whether another program has changed the operating system's proxy settings. After quitting the client, confirm that the system proxy has returned to the expected state.
Where should I start if connections are slow or the client closes unexpectedly?
For slow speeds, first separate node issues from local issues: test another node on the same network and compare rule mode with global proxy. Then check DNS resolution and make sure TUN isn't enabled unnecessarily. If the client closes unexpectedly, note what you were doing when it happened, reopen the client, and check the logs for core startup failures or configuration parsing errors. Change one setting at a time and keep the steps needed to reproduce the issue. For a more systematic walkthrough, see the troubleshooting guide.
More troubleshooting
Follow a complete diagnostic walkthrough
Need to check logs, nodes, system proxy, and DNS step by step? The troubleshooting guide breaks common symptoms into focused sections.