v2rayN Usage Guide · Help Index

v2rayN FAQ

Find answers by where the problem occurs. Note the error and current settings, change one thing at a time, then test again in the same app.

Getting Started

Identify the configuration source, core, and proxy endpoint before deciding what to check.

Browse the glossary →
What’s the difference between a subscription URL and a single-node share link?

Subscription URLs usually start with HTTPS and provide a set of configurations when the client updates them. Share links starting with vmess:// or vless:// usually describe a single node. For a subscription URL, open “Subscription Group Settings,” enter it under “Address (url),” and update the subscription. Import a single-node link from the clipboard instead. Regular web pages can also start with HTTPS, so check that you copied the subscription endpoint, not a service dashboard URL.

What are the client, core, and node?

v2rayN is a graphical client for importing configurations, choosing nodes, and changing settings. Cores such as Xray and V2Fly read compatible configurations and handle connections. A node is a remote endpoint the client connects to, along with its settings. Troubleshoot by layer: if the window won’t open, check installation and startup records; if it opens but the log reports a core startup failure, check the core configuration; if the core runs but one node fails, check that node’s settings and test results.

How do the system proxy, routing rules, and TUN differ?

“Set system proxy automatically” provides a proxy endpoint for apps that follow the system proxy settings. An app’s own proxy settings may take precedence, or it may ignore the system settings entirely. Routing rules determine whether traffic entering the core is proxied, sent direct, or blocked. TUN uses a virtual network interface to capture traffic covered by its routes, but doesn’t guarantee that every connection is proxied. For browser-only tests, start with the system proxy. Test TUN separately when checking whether an app bypasses the system proxy.

Which client should I use on desktop or Android?

Use v2rayN on Windows, macOS, and Linux. On Android, v2rayNG with the Xray core is the usual choice; consider v2flyNG if you need the V2Fly core. Choose a client for your device, then check which protocols and transports your configuration requires. Similar names don’t guarantee configuration compatibility. Before switching clients, keep your existing configuration and test one known-working entry. Once startup, access, and disconnect all work, migrate the full subscription group.

Installation and Setup

Start with the installation package, first launch, and subscription import. Handle permissions only when the error points to an authorization issue.

Check client and installation requirements →
Which Android package should I choose: arm64 or universal?

Choose arm64 if your device is confirmed to support arm64-v8a apps. If you’re unsure which ABIs the system supports, choose universal, which includes multiple architectures and is usually a larger download. A 64-bit processor doesn’t mean the device’s operating system can install 64-bit apps. If installation fails, note the error: for an architecture mismatch, try the universal package; a different architecture usually won’t fix a signature conflict or an unsupported OS version.

Subscription import failed. What should I check first?

First, check which import method you’re using. Don’t import a subscription URL through the single-node clipboard option. Open “Subscription Group Settings,” fill in “Remarks” and “Address (url),” save, then update the subscription. If saving fails, check for quotation marks, line breaks, or extra text in the URL, and make sure you copied the full query string after the question mark. If the update succeeds but the list is empty, select the relevant subscription group and check whether “Filter” excluded every entry. Then confirm the subscription contains configurations the client can recognize.

TUN reports insufficient permissions. What should I do?

First, identify what failed: creating the virtual network adapter, changing routes, or starting the core. On Windows, if the log explicitly reports insufficient permissions, close the client and relaunch the existing v2rayN program with “Run as administrator” to compare results. Authorization on macOS and Linux depends on the package and version; follow the client’s prompts instead of broadly weakening system permissions. Android uses the system VPN permission. If another VPN is running, disconnect it, then reconnect from the client and grant permission when prompted.

v2rayN does nothing when I open it after extracting the Windows archive. What should I do?

Don’t launch the program from the archive’s preview window. Extract the entire archive to a folder your account can write to, then run the program from there. If you’ve already launched it, check whether its icon is in the notification area. If a dialog reports a missing runtime, note its name, version, and architecture, then install what the release package requires. If there’s no dialog, check the “Application” log in Windows Event Viewer and look for errors around the startup time. Don’t overwrite your existing configuration first.

Usage Tips

Verify a node switch with a new connection. Note the original settings before comparing options so you can restore them.

View the complete setup guide →
How can I confirm that a node switch took effect?

Select the new entry in the v2rayN node list and choose “Set as active server.” Highlighting a row alone doesn’t switch nodes. Confirm the active entry has changed, then start a new connection. Browsers may reuse existing connections, so quit and reopen the browser and test the same known-accessible page. If the main window shows the new node but access still fails, check the log after switching and find the first error during active configuration startup—not just the last line.

How can I tell whether a problem is caused by routing rules or the node?

Keep the node and proxy endpoint unchanged, and note the current routing preset. In the same app, visit one working destination and one failing destination, then temporarily switch to “Global” and test the failing destination again. If it fails only with the original preset, check which rules match, their order, and DNS resolution. If both presets behave the same, check whether the app’s traffic reaches the proxy and whether the node can connect. Restore the original preset afterward; don’t change the node, routing, and DNS all at once.

Does “Do not change system proxy” clear existing settings?

No. This option leaves the current system proxy unchanged; it doesn’t mean direct connection and isn’t the same as “Clear system proxy.” If a system proxy pointing to this computer was already configured, it may remain in place after selecting “Do not change system proxy.” To remove settings written by v2rayN, choose “Clear system proxy,” then verify the result in your system’s network settings. On a managed device with existing proxy settings, note the original configuration before testing and don’t overwrite it.

How can I keep manually edited nodes when updating a subscription?

Entries in a subscription group may be regenerated during an update, so editing one directly isn’t a reliable way to keep changes. Import the entry you want to keep as a separate configuration in a group that isn’t linked to a subscription URL, then edit that copy. Update only the original subscription group, confirm the copy is still there, and check whether the original active node still works. Share links may contain connection credentials; don’t post them in public chats or show a full subscription URL in support screenshots.

Troubleshooting

First determine whether the failure affects one node, one app, or all connections, then check the logs.

Browse troubleshooting by symptom →
Node latency tests keep timing out. How can I narrow down the cause?

Test one node first and note whether you’re using a connectivity test or a real connection test. Reaching a port doesn’t guarantee that the protocol handshake will succeed. Then test another known-working node on the same network using the same test method. If only one node fails, check its server address, port, and transport settings, and look for handshake errors. If all tests time out, confirm the core has started, then check the log for the earliest DNS, connection, or authentication error. An unreachable test target can also produce misleading results.

The client says it’s connected, but why won’t web pages load?

A connected status doesn’t mean the destination is reachable. In your usual browser, first open a page that normally works without a proxy, then compare it with the page that won’t load. If both fail, temporarily clear the system proxy or turn off TUN for one test on a network where direct access is allowed. If direct access fails too, troubleshoot your local network first. If only proxied access fails, check the active node and logs: investigate DNS for resolution errors, the local proxy port for connection refusals, and the remote configuration for handshake failures.

Why isn’t an app using the proxy after I choose “Set system proxy automatically”?

Check your system’s network settings to confirm the proxy is enabled and its address and port match v2rayN’s local listening settings. Then make a new request in a browser that follows the system proxy and check whether the client logs the corresponding connection. If the browser uses the proxy but the target app doesn’t, check for an app-specific proxy setting or whether it explicitly ignores the system proxy. If the browser also fails, check core startup and port conflicts. If the log shows traffic entering the core but going direct, review the routing rules.

A subscription used to update successfully. What should I do if it now fails?

Keep your existing groups and nodes, and check the update log first. Don’t delete and recreate them. For a 401 or 403 response, check whether the subscription is still valid and whether its URL has changed. If the request succeeds but parsing fails, check whether the response is a login or error page. For timeouts, compare the two update methods when network conditions allow: try “Update through proxy” if the current node works, or “Update without proxy” if the node itself is unavailable. Update only the affected group at a time so you can compare results.