V2Ray FAQ

Subscription setup, client installation, and connection troubleshooting. If the list is empty, start with setup. If nodes are available but apps can’t connect, follow the steps in Troubleshooting to check local traffic, routing rules, and outbound connections.

Basics

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

A subscription URL usually starts with HTTPS and provides a list of nodes. Refreshing the same group fetches the latest list from the server. Share links starting with vless:// or vmess:// usually describe a single node and won’t update when you refresh a subscription. A provider’s login or plan page is not a subscription URL. Before copying a link, check which type the provider gave you, then add it as a subscription or import it from the clipboard. Don’t paste a share link into the subscription URL field.

Which devices are v2rayN, v2rayNG, and v2flyNG for?

Use v2rayN on Windows, macOS, or Linux, and choose an installer that matches your operating system and processor architecture. On Android, v2rayNG with the Xray core is usually the first choice; consider v2flyNG if you specifically need the V2Fly core. Device compatibility is only the first check: make sure your client and core support the subscription format, node protocol, and transport options. If the same URL updates in one client but fails in another, check the subscription format before changing protocols.

Does a successful subscription update mean my traffic is using the proxy?

No. Updating a subscription fetches node configurations. Selecting a node determines the outbound connection, while system proxy settings or TUN mode determine which apps send traffic through the client. Even with a healthy node list, requests won’t be routed as expected if no node is selected or your browser isn’t using the system proxy. To verify, check the active node, test a destination that should use the proxy, and review the client logs to confirm the request arrived and which route it matched.

What’s the difference between a system proxy, TUN mode, and routing rules?

A system proxy provides a local proxy address to apps that honor the system setting. TUN mode uses a virtual network interface to receive traffic routed to it by the operating system, covering more apps that don’t use the system proxy. Routing rules determine whether requests that reach the client go direct, through the proxy, or are blocked. When troubleshooting, first check whether traffic reaches the client, then check which rule it matches. Changing routing rules alone won’t make an app that ignores the system proxy connect automatically.

Setup

Should I choose arm64 or universal for an Android package?

If your system supports 64-bit ARM apps, choose arm64; its package is usually smaller. If you’re unsure which architectures your system supports, or the arm64 installer reports an architecture mismatch, try universal and check the version’s minimum Android requirement. Don’t rely only on the processor specifications for your phone model: some devices still run a 32-bit operating system. If an older version installs but the new one won’t update over it, also check whether the installed app and new package have matching signatures.

v2rayN shows no nodes after I add a subscription URL. What should I check first?

Saving a subscription group doesn’t fetch its nodes. First make sure the selected group is the one you just saved, then update the current subscription and check the logs. If the URL is reported as invalid, check that you didn’t copy a login page, a block of instructions, or a link containing line breaks. If parsing fails, confirm that the provider returns a subscription format supported by the client—not a login page or error page. If the list is still empty after updating, check the group’s filters and the current list filter.

What should I do if TUN mode reports insufficient permissions?

First, check that the client has permission to create a virtual network interface and modify routes, as allowed by your system. On Windows, grant administrator privileges when prompted by the client and try again. On macOS and Linux, follow the authorization steps for your version; don’t disable system protections to bypass the error. If it still fails, temporarily stop other network tools that may be managing the same routes, then check the logs to tell whether interface creation or route configuration failed. If you only need proxy access in a browser, try the system proxy instead.

Which v2rayN package should I choose for macOS or Linux?

On macOS, check your chip under About This Mac: choose arm64 for Apple Silicon or x64 for Intel. On Linux, check both the system architecture and package format: x86_64 corresponds to x64, and aarch64 to arm64. Debian and Ubuntu users generally need deb; Fedora users generally need rpm. The right architecture doesn’t guarantee all dependencies are available. If installation reports missing dependencies or an unsupported system version, check your distribution’s supported versions using the package manager’s guidance rather than trying a different package format.

Usage Tips

Should I enable automatic subscription updates?

Update manually once to confirm the list downloads and see which nodes belong to the group. Then set an interval based on the provider’s update schedule. There’s no need to refresh frequently if the list rarely changes. Automatic updates may replace the group’s nodes with the remote list, so keep manually imported or separately maintained configurations in another group. If an update removes the active node, select another one and test an actual connection; a new entry in the list alone doesn’t mean the connection is working again.

Why isn’t the node with the lowest latency always the fastest?

Latency measures how long the client takes to complete a particular probe. It isn’t the same as download throughput and doesn’t predict performance for every destination. A TCP probe usually checks only whether a connection can be established; a test through the proxy also depends on the protocol handshake, test destination, and network conditions. Compare nodes using the same test method and destination, ideally within a similar time window. Before choosing a node, run a small test with the activity you actually need instead of relying on a single result.

When should I enable “Use proxy for subscription updates”?

If your device can fetch the subscription directly, leave this option off to avoid making updates depend on the active node. Enable it only when direct access to the subscription endpoint fails and an available node can reach it. This setting changes the route used for subscription requests; it doesn’t control how everyday app traffic is routed. If the active node is down, enabling the option may also prevent updates. Try a working node, or confirm the endpoint allows direct access and turn the option off before trying again.

Why do terminal tools connect directly when my browser uses the proxy?

Many terminal tools ignore the system proxy or use only their own proxy settings. First, make sure the client’s local HTTP or mixed inbound port is enabled, then configure the proxy address as described in the tool’s documentation. If the tool supports environment variables, try setting HTTP_PROXY or HTTPS_PROXY temporarily for the current session, and check whether NO_PROXY excludes your test destination. Tools may handle these variables differently. Clear the temporary settings when you’re done so changes to the local port don’t affect later commands.

Troubleshooting

Node tests time out. How can I tell whether one node or my device is at fault?

First, turn off the proxy and check whether a regular page loads directly. Then compare other nodes in the same group using the same test method. If only one node times out, check that its address, port, and transport settings match the provider’s details. If several nodes time out, check whether the client core is running, whether another process is using the local listening port, and whether the test destination is reachable. If the problem occurs only on one network, keep the node and test method unchanged and try again on another trusted network.

The client says it’s connected, but I can’t access the internet. Where should I start?

Temporarily turn off the system proxy or TUN mode you enabled and check that a regular page loads directly. Then re-enable just one mode and test again. A “connected” status in the client doesn’t mean app requests have reached the core. If the retry produces no matching log entry, check whether the app uses the system proxy or whether its traffic is routed to the virtual interface. If a request appears in the logs, use the error to distinguish DNS resolution failures, blocked routes, and outbound handshake failures. Change one setting at a time.

How can I tell whether my browser is using the enabled system proxy?

Open your system proxy settings and check that the proxy address and port match the client’s current listening address and port. If they do, check browser extensions, automatic configuration scripts, and proxy exceptions to see whether the test destination is being sent directly. Try the same destination in another browser known to use the system settings, and check the client logs. If only one browser has the problem, focus on its configuration. If neither browser produces an inbound log entry, check the system settings and local listener.

My subscription used to update but now fails. How should I interpret the error?

Keep the existing group and the last successfully fetched nodes so you don’t lose the configuration before resolving the issue. If the logs show 401 or 403, check whether the subscription expired, the URL was reset, or the provider restricts access. For connection timeouts, check the network path to the subscription endpoint and whether updates depend on a proxy that’s no longer working. For certificate errors, verify the system clock and subscription domain; don’t skip certificate checks. If you share the logs, remove the full subscription URL and any credentials it contains.

For initial setup, follow the user guide to import a subscription, connect, and verify it. If you need a different installer, check the platform and system requirements on the download page.