FAQ Client Usage & Troubleshooting
Frequently Asked Questions about v2rayN
Start with package and subscription formats. If you’re connected but can’t access anything, troubleshoot the traffic entry point, routing, and outbound in that order.
Getting Started
Identify clients, subscription formats, and config fields.
What’s the difference between v2rayN, v2rayNG, and v2flyNG?
v2rayN is available for Windows, macOS, and Linux. v2rayNG and v2flyNG are Android clients that use the Xray and V2Fly cores, respectively. Choose a client for your device first, then check that it supports your node’s protocol, transport, and security options. Two clients may both import the same link without recognizing all of its settings. See available package formats and architectures for each platform on the client download page.
What’s the difference between a subscription URL and a single-node link?
A subscription URL provides a list of nodes. Add it to a subscription group, then update that group. A single-node link describes one connection and should be imported from the clipboard or added by scanning its QR code. Importing a subscription URL as a single node may result in an unsupported-format error; saving a single-node link as a subscription won’t produce a usable list when updated. If you’re unsure which format you have, ask the configuration provider. Don’t post the full URL in a public support forum.
Are system proxy, TUN, and global mode the same thing?
System proxy and TUN determine how traffic enters the client. System proxy relies on apps using the system proxy settings; TUN routes traffic through a virtual network adapter. Global mode determines the outbound choice after traffic enters the client, according to its routing configuration. Global mode doesn’t necessarily capture traffic from every app, and enabling TUN doesn’t disable direct-connection rules. Troubleshoot the traffic entry point and outbound route separately.
How should I understand inbounds, routing, and outbounds?
Follow the path of a request: inbounds define how it’s received, such as the local listening address, port, and protocol; routing uses rules to decide which outbound handles the traffic; outbounds define how the connection is made. When checking a config, first confirm the app sends requests to the right inbound, then review the routing conditions, and finally check that outboundTag points to a defined outbound tag. See the config reference for field structure and relationships.
Setup
Choose a package by operating system, architecture, and interface, then import your subscription.
Which Android package should I choose: arm64 or universal?
If your device’s Android system supports arm64-v8a, choose the arm64 package. If you’re unsure, check the manufacturer’s specifications or the supported ABIs listed in your device information. A 64-bit-capable processor alone doesn’t guarantee that the installed operating system can run 64-bit apps. If you still can’t confirm, try the universal package for the same client. Universal packages are usually larger and still require the minimum Android version. For an upgrade, also check for any signing-conflict warning.
Which macOS package should I choose: Apple Silicon or Intel?
Open About This Mac from the Apple menu. If it shows an M-series chip, choose the Apple Silicon arm64 package. If it shows an Intel processor, choose the Intel x64 package. Choose based on your Mac’s processor, not the client version you used before. If macOS displays a warning on first launch, check whether it concerns the system version, device management restrictions, or an app that can’t be opened. Ask your administrator about restrictions on a work device.
Which Windows version should I choose: Desktop or WPF?
Desktop uses a cross-platform interface; WPF has the classic Windows interface. Stick with WPF if your workflow depends on its familiar menus, or choose Desktop for an interface closer to those on other desktop platforms. Back up your nodes, subscriptions, and custom routing rules before switching. On the first launch of the new version, quit the old app and its tray process, then check the local listening port and system proxy settings to prevent both instances from changing settings at once.
I copied a subscription URL. Why are there no nodes after importing it?
Make sure the clipboard contains the full subscription URL, not the provider’s homepage or a single-node link. Add and save an entry in a subscription group, then update the group manually; saving the URL alone won’t fetch any nodes. If the log shows a successful request but nothing to import, check whether the response is a login page, an empty list, or a config format the client doesn’t support. If you copy the URL again, keep its query parameters intact—don’t remove or change them.
Tips
Verify proxy settings with new requests, and distinguish speed tests from actual connectivity.
How can I tell whether an app is using the system proxy?
First confirm the client core is running. Then check the system network settings to make sure the proxy address and port match the client’s local listener. Send a request from a browser that follows the system proxy settings, and check the client log for a corresponding entry. If the browser appears in the log but another app doesn’t, check whether that app has its own proxy settings, is affected by a browser extension or management policy, or needs to be restarted after settings change.
Which node speed test result should I look at?
Check the test method before comparing results. TCP latency measures how long it takes to connect to the node’s address and port; it doesn’t tell you whether the proxy handshake or target website will succeed. Tests sent through the proxy are also affected by the test URL and DNS resolution. Compare results on the same network using the same test method and URL, and retest if needed. If you use a particular site or app, verify it with an actual request instead of relying on latency rankings.
TUN reports insufficient permissions. What should I check first?
Check the startup log to see whether the failure involves creating the virtual network adapter, adding system routes, or obtaining system authorization. On Windows, grant permission as prompted by the client, then start it again. On macOS and Linux, check the permissions required for your version. On Android, confirm the VPN connection request and check whether another VPN is already running. Run only one tool that captures traffic at a time. Ask an administrator to handle permission restrictions on managed devices.
Why don’t existing connections seem to change after I switch nodes?
After switching nodes, test with a new request first. Existing long-lived connections may continue using their original route, or disconnect and reconnect when the core reloads. Close and reopen the app you’re testing, then check the outbound tag for the new request. If it still goes direct, check whether the active routing config matches a direct-connection rule. Changing the current node only affects requests routed through a proxy outbound; it doesn’t change existing routing rules.
Troubleshooting
Use logs from the time of the issue to distinguish subscription updates, proxy connections, and local listener problems.
A subscription used to update successfully. How do I troubleshoot update failures?
Update only the group that failed and note the error from that request. If domain resolution fails, check your current network and system DNS. For connection or read timeouts, check whether the network path used by the update request is available. If the response is unauthorized or access is forbidden, ask the provider whether the URL has expired or needs to be reissued. If the error occurs while parsing, check the subscription format and client compatibility. Keep your existing nodes; don’t delete the whole group just to retry.
Node tests keep timing out. How can I narrow down the problem?
On the same network and with the same test method, test the failing node and one known-working node. If only tests sent through the proxy fail, try a different test URL that you can access normally. If just one node fails, check the server hostname and port, then see whether the log reports a connection timeout or handshake failure. If several nodes fail at once, check your local network, whether the core starts, and DNS first. Change one setting at a time and keep the results from before and after.
The client says it’s connected. Why won’t websites load?
Connected usually means the local service or traffic-capture mode has started; it doesn’t mean a particular request succeeded. Open a website and check the log for that request. If there’s no entry, check whether the browser is using the system proxy or TUN. If the log shows a DNS resolution failure, troubleshoot DNS. If it shows the outbound but the handshake fails, check the node’s transport and security settings. If only one site fails, try another site in the same browser before reinstalling the client.
System proxy is enabled but still not working. What conflicts should I check?
Check that the port in the system proxy settings matches the port the current core is actually listening on, and confirm the proxy protocol. A SOCKS-only port can’t be used as an HTTP proxy port. Then check whether the browser has its own proxy extension, the system has an automatic proxy script, or another client is overriding the proxy settings. Close other proxy tools, reapply the settings, and verify with a new request. Clear the related system proxy settings before quitting the client.
The log says the local listening port is already in use. What should I do?
Note the listening address and port in the startup error log. Check whether another client instance is still running in the system tray, then use a system connection-monitoring tool to identify the process listening on that port. If it’s an old instance, quit it normally. If the port belongs to another app you still need, choose an unused port in the client. After restarting the core, update the system proxy and any app ports you configured manually, then test with a new request. Don’t terminate system processes you can’t identify.