FAQ / Client Setup
v2rayN FAQ
From choosing an installer and importing subscriptions to system proxy, routing, and connection issues. Find answers by task or symptom.
01 / BASICS
Basics
Understand the client, core, servers, and traffic entry points.
What do the client, core, and server each do?
v2rayN is a desktop GUI client that manages subscriptions, saves settings, and starts the core. Cores such as Xray and sing-box listen on local ports, apply routing rules, and handle outbound connections. A server is a set of remote connection parameters, not a service bundled with the client. When troubleshooting, first identify which layer is failing: if the client will not open, check the installation environment; if the core fails to start, review its startup logs; if only one server is unreachable, check that server’s settings and service status.
What’s the difference between a subscription link and a single-server link?
A subscription link points to a list of configurations that can be fetched again. Save it in a subscription group, then update the group. A single-server link contains the parameters for one connection and should be imported from the clipboard as a server. If the remote settings change, you’ll usually need to import the link again. Don’t identify a link by its length; use the purpose specified by its provider. Subscription URLs may contain credentials, so hide the full URL and query parameters before sharing screenshots, recordings, or logs.
Are system proxy, routing mode, and TUN the same setting?
No. The system proxy provides a local proxy endpoint for apps that follow system settings. TUN uses a virtual network interface to capture traffic according to its configuration. Routing mode determines whether traffic entering the core is sent direct, through a proxy, or blocked. To test a browser, start by enabling the system proxy and leaving the current routing mode unchanged. If an app doesn’t use the system proxy, check whether it supports its own proxy settings or whether TUN is needed. Don’t change the traffic entry point and routing mode at the same time.
Should I use v2rayN, v2rayNG, or v2flyNG?
Use v2rayN on Windows, macOS, or Linux, and check your OS and processor architecture before installing. On Android, v2rayNG with the Xray core is usually the first option to consider; choose v2flyNG if you already have configurations maintained for V2Fly features. Base your choice on the protocols, transport, and security settings your servers require—not just whether a link imports successfully. After switching clients, review routing, DNS, and local proxy settings instead of copying the old client’s options one by one.
02 / INSTALLATION
Installation & setup
Check installer architecture, subscription formats, and TUN permissions.
Why is the server list empty after importing a subscription on desktop?
Add an entry in a subscription group, enter a label and the full subscription URL, save it, then manually update that group. Return to the server list, select the group, and clear any search filters. Adding a group only saves the URL; it doesn’t fetch servers. If the menu reports an import failure, make sure you copied a subscription URL rather than a sharing page or single-server link. If the update completes but the list is still empty, check the logs for parsing errors and confirm the provider returned a format the client can read.
Which Android APK should I choose: arm64 or universal?
If your device’s Android system supports arm64-v8a, choose arm64 for a typically smaller APK. A 64-bit processor alone doesn’t guarantee that the system supports this architecture; some devices still run a 32-bit OS. If you’re unsure, check the manufacturer’s system specifications or choose the universal package, which includes multiple architectures. If an update fails because the signatures don’t match, back up your settings and check where the existing app came from. If the system version is too old, switching architecture packages won’t help.
What’s the difference between the Windows desktop and classic WPF versions?
The desktop version uses a cross-platform interface, with menus and layout closer to those on other desktop platforms. The classic WPF version is designed for Windows and keeps its familiar layout. Choose based on your preferences and system requirements; a different interface doesn’t mean different server speeds. Before switching, back up your subscriptions and custom routing, fully exit the old client, then launch the other version and check its local listening ports. Don’t let both versions use the same port or alternate between them to change system proxy settings.
What permissions does TUN require?
TUN creates a virtual network interface and modifies system routes, so the required permissions depend on your OS and installation method. If startup fails, check the core logs first to distinguish insufficient permissions from interface creation failures or routing conflicts. On Windows, if the client explicitly reports insufficient permissions, follow its instructions to restart a trusted installation with administrator privileges. On Linux, configure the required permissions according to your distribution and package instructions. If the device is managed by an organization, check its policies first; don’t disable system protections to obtain access.
03 / USAGE
Tips & usage
Check outbound routes, keep your settings, and change one thing at a time.
How can I tell whether a website is actually using the proxy?
Select a server and leave the routing mode unchanged, then visit the site in a browser that uses the system proxy. Check the client’s access logs around the time of the request and confirm the target domain or address and its outbound route. If the page loads but the log shows a direct connection, connectivity is working, but that request didn’t use the proxy. To test routing rules, start a new browser connection. An already-open page may use cached data or an existing connection, so it shouldn’t be your only test.
How can I keep manually managed servers and routes when updating a subscription?
Put manually managed servers in a separate group, and don’t edit entries that subscription updates can overwrite. Before updating, use the export or backup feature available in your version to save your settings, and note the names and activation order of custom routes. After the update, check the server list in the original group and confirm that the currently selected server is still there. If an old server was removed, select and test another one; don’t assume an old alias still works. Store backups as sensitive configuration data.
Do existing connections change immediately when I switch routing modes?
Don’t use pages that were already open before the switch to judge the result. Routing rules are usually matched when a connection is established; existing connections may keep their original outbound route or drop if the core restarts. After saving the routing settings, make the test app establish a new connection, then check the logs for the matched rule and actual outbound route. If the result differs from what you expected, check rule order and the fallback outbound. A broader rule earlier in the list may already match the request, leaving later, more specific rules unused.
What should I check before switching between Xray and sing-box?
Note the current server’s protocol, transport, and security settings, then confirm the target core supports that combination and can apply your existing routing and DNS settings as expected. Switch only the core—not the server and routing settings at the same time—so you can isolate the cause if something breaks. After restarting, confirm the core is running and listening on its local ports before making a real request. If the logs show unrecognized fields or an unsupported transport, switch back to the original core and consult the client and core documentation before making changes.
04 / DIAGNOSTICS
Troubleshooting
Use logs to distinguish subscription requests, server connections, and app proxy issues.
A subscription used to update successfully but now fails. What should I check first?
Manually update the affected group once, note which network path the update uses, and check the logs. For connection timeouts or DNS failures, first check whether your current network can reach the subscription service. For unauthorized, forbidden, or not-found responses, ask the provider whether the URL changed or the credentials expired. If the request succeeds but parsing fails, check whether the response is now a login page or error page. Keep the existing group; there’s no need to delete servers or repeatedly recreate settings before finding the cause.
A server test times out. How can I tell whether it’s a server or local issue?
On the same network, test two different servers using the same method, then try a real request. If only one server times out, check its address, port, transport, and required connection settings. If several servers fail, first check whether the core is running, whether the test address is reachable, and whether the device clock is correct. A handshake timeout isn’t the same as a failure to reach the test site. If real requests work but speed tests fail, check the test method and target.
v2rayN says it’s connected. Why won’t web pages load?
Make a new request in a browser that follows system proxy settings, and confirm the system proxy points to the address and port the client is currently listening on. If the request doesn’t appear in the logs, check the app’s proxy entry point first. If it does, find out whether the failure occurred during DNS resolution, route matching, or the remote handshake. On the same network, compare a site that should connect directly with one that should use the proxy to narrow down the issue. A running core doesn’t mean the remote server has responded, and it isn’t a substitute for testing an actual connection.
Why does the system proxy work in some apps but not one particular app?
If the browser uses the proxy successfully, check whether the affected app reads system proxy settings and whether it has a separate proxy, bypass rules, or an always-direct option. Some apps read system settings only at startup, so fully quit and reopen the app after saving changes. If it supports manual proxy settings, enter the local address and port for the proxy type it accepts; don’t mix up HTTP and SOCKS ports. If there’s no manual proxy option, consider TUN or ask your device administrator.