Windows
Check your system type in Windows Settings → About, then pick the v2rayN desktop or classic WPF edition.
Before switching clients, note your settings. Let only one client manage the system proxy at a time.
Go to downloadsChoose an open-source client for your device, then work through subscription import and routing checks step by step.
First, understand the three roles: the client provides the interface, the core handles connections, and a subscription is one way to update your node list. Downloading a client is only the first step; it does not provide working nodes.
On the download page, check your operating system, processor, and package type. When switching devices, choose a package for the new device rather than reusing the old installer.
A subscription is an updateable source of nodes. After importing it, refresh the list and select a node. If you have a single share link, import it as an individual node instead of creating a subscription group.
First identify whether the list failed to update, the core failed to start, or only one app is affected. Note where the problem occurs, then check the relevant troubleshooting steps; this is usually more useful than reinstalling.
Troubleshoot each part separately: routing determines the path a connection takes, subscriptions determine where nodes come from, and DNS determines how domain names are resolved.
An outbound is the core’s connection exit: it can connect directly or send traffic through a proxy. Unlike a setup that sends every intercepted connection through the same outbound, routing can match domains or addresses. For example, send local services directly and route traffic that needs a proxy through the selected node. Start with a preset, then add only rules you need. After saving, test one destination that should connect directly and another that should use the proxy, then check the logs to see which rules matched. If traffic takes the wrong path, check whether a specific rule appears after a broader one.
{ "protocol": "freedom", "tag": "direct" }
This is a direct outbound snippet; routing rules refer to the matching tag with outboundTag.
One URL can return a list of nodes, which the client retrieves again when you update the subscription. Grouping nodes by source makes it easier to check update results and reduces the chance of accidentally deleting nodes from another source. In v2rayN, give each group a recognizable name, save its URL, and update that subscription by itself. Confirm the expected nodes appear before organizing the list with filters. If filtering removes everything, narrow the filter or temporarily disable it rather than replacing the original URL.
Subscription Group Settings → Update Current Subscription
DNS resolves domain names to addresses. A reachable node only shows that part of the connection path works; it does not prove that every domain queried by an app can be resolved. Rather than replacing every system and client resolver when something fails, change only the DNS settings currently used by the core so you can verify the effect. Note the failing domain and determine whether the error occurs during resolution or later in the connection, then choose a resolver if needed. If your browser uses its own secure DNS, include that in your checks, since its queries may not follow the resolver path configured in the core.
dns.servers specifies the resolvers used by the core’s DNS module; it is separate from the system’s DNS settings.
Check rule order, interception scope, and how to configure custom outbounds.
Learn what protocols, transport methods, and outbound tags each do.
Narrow down the cause by checking installation, import, and connection steps.
Check your operating system first, then your processor architecture. x64 and arm64 in package names refer to different hardware architectures, not feature levels, and are not interchangeable based on which name seems newer.
Check your system type in Windows Settings → About, then pick the v2rayN desktop or classic WPF edition.
Before switching clients, note your settings. Let only one client manage the system proxy at a time.
Go to downloadsCheck “About This Mac.” Choose v2rayN for arm64 on Apple silicon or x64 on Intel.
Make sure both the client and its core start before enabling the proxy.
Go to downloadsChoose v2rayNG for Xray or v2flyNG for V2Fly. Check which package your device supports.
Settings don’t carry over between clients. Save your server details and retest your apps after switching.
Go to downloadsMatch your processor and package format: deb for Debian and Ubuntu, rpm for Fedora.
Test v2rayN with an app that uses system proxy settings. Command-line tools may ignore them.
Go to downloadsFor your first setup, establish one testable connection path. Use the same test destination at each step, then add app-specific routing or custom DNS once the basic connection works.
Open subscription management in the client, add the URL to a new group, save it, and update that group. Note the group name before updating, then select it again to check the results. If the list is empty, confirm that the right group is selected, check for spaces or line breaks in the copied URL, and make sure the subscription is still valid.
If your provider gave you a single-node link, import it as a share link. Treating a single-node link as an updateable subscription often won’t produce the expected list. Subscription URLs may contain access credentials, so describe the error when asking for help but don’t share the full URL.
Choose a complete node from the imported list and set it as the current node. On desktop, start with the system proxy and test an app that follows system proxy settings. On mobile, use the client’s instructions to establish a system VPN connection. Core startup and proxy interception are separate: a successfully started core does not mean the test app is using it.
Keep the default routing in place at first and avoid enabling multiple interception methods at once. If the device already runs another proxy or has network settings managed by your organization, confirm which settings you can change and record their original values.
First visit a destination that normally connects directly, then test one that should use the proxy according to your rules. If logs are available, match the time and destination to confirm that the connection reached the core and used the expected outbound. Node speed tests can help with comparisons, but they don’t replace testing an actual request in an app.
When finished, stop the client and check the network state again. If your browser can no longer open websites after you exit, check whether the system proxy still points to a local port whose client has stopped before changing nodes or DNS.
Distinguishing the client, core, and service provider helps you determine whether a guide’s menus, configuration fields, or upgrade instructions apply to your device.
Project V provides a set of tools for building network proxies, with V2Ray as its core for handling connections. In the configuration, “inbound” describes where the core receives connections, while “outbound” describes how it handles them; routing chooses between outbounds. Graphical clients organize these settings into node lists, proxy controls, and routing pages, so you don’t have to edit configuration files section by section.
When you see “V2Ray configuration,” first determine whether it means a complete core configuration, a specific field, or a link to import into a client. These serve different purposes. For example, a guide that provides only an outbound snippet still needs to work with your existing inbounds and routing. Replacing the entire file with a snippet also removes your existing listening ports and rules.
V2Fly continues community maintenance of the V2Ray core, while Xray grew from related code into an independent core. They share many configuration concepts, but protocol features, transport options, and supported fields are not identical. Even if both display the same protocol name, check the transport, security settings, and server parameters together; the name alone doesn’t tell you whether a connection will work.
For example, two nodes using VMess can use different transport methods. Successful import only means the client understood the link; the connection also depends on whether the selected core supports the relevant fields and whether both ends are configured consistently. If a node imports successfully but won’t connect, check the active core and node settings before considering a different client.
v2rayN, v2rayNG, and v2flyNG are open-source graphical clients. v2rayN is for desktop and can use different core types for nodes, depending on client support. v2rayNG is a mobile client for Xray, while v2flyNG uses the V2Fly core and may suit configurations explicitly intended for it. The client provides the controls; the core handles connections. Don’t conflate their settings.
Choose based on your device and existing setup. For subscription group management on desktop, start with v2rayN; on mobile, compare the two clients against your node requirements. The easiest migration is often to import the existing subscription into the new client to rebuild the node list, then recreate custom rules one by one—not to copy the other client’s entire configuration file.
Open-source licenses define how code may be viewed, modified, and redistributed. They don’t provide remote nodes or set third-party service traffic limits, operating hours, or availability. Read the client’s license and the provider’s terms separately. If a subscription stops working, check its URL and the service status; if the interface won’t start, check the client’s system requirements first.
Screenshots, exported configurations, and logs may expose subscription URLs, node addresses, or personal browsing records. When describing a problem, include the client name, error category, steps to reproduce, and only the necessary redacted fields. If the issue is reproducible, note the network and test destination; that’s more useful than sharing a full-screen configuration screenshot.
Community-maintained clients, their bundled cores, and subscription lists follow different update schedules. A client update may change menus or import steps; a core update may affect protocol compatibility; a subscription update may replace nodes or rename them. If all three change at once, it’s hard to tell which one to roll back when something goes wrong.
Before updating, record the client in use, core type, current node, and system proxy mode locally, and back up essential settings using the client’s supported method. After updating, repeat the same tests that previously worked and check direct connections, proxy traffic, and shutdown behavior. If only one node group has problems, inspect that subscription first. If every app loses connectivity, check core startup and system-level interception.
Once your basic connection works, explore the next steps for your setup: organize subscriptions if the node list is too long, or read about router deployment before expanding the scope of traffic interception.
Separate nodes from multiple providers into subscription groups, filter out unwanted nodes by keyword, and use group speed tests and automatic updates to keep the list organized.
Read the subscription management guide →Answers to ten common beginner questions, from importing subscriptions and choosing a mode to diagnosing why a connection works but websites won’t load.
Read the beginner Q&A →Compare running the core on your main router, using a bypass gateway, and setting up a transparent proxy. Learn the hardware and firmware requirements and how each option differs from a desktop client.
Read the deployment overview →