Client downloads · Setup guides
Start with subscription import, choose a client for your platform, then learn about traffic routing and DNS settings.
Subscriptions → Rules → Outbound
The client organizes your configuration; the core handles connections. Get one connection working first, then add rules one at a time so you can pinpoint what changed when troubleshooting.
When subscriptions are mixed in one list, it is hard to tell where each server came from. Create a separate group in v2rayN for each source, add its subscription URL, then update the group. To narrow the list, filter by remark keywords. Filtering only changes what is displayed; it does not alter the remote subscription. Before updating, note the current group and selected entries. Check the log afterward so an empty list is not mistaken for a connection failure. Groups make subscriptions easier to update and roll back than pasting share links one by one.
Treat subscription URLs as sensitive information: they provide access to your configuration. Open the relevant section of the manual →geosite:category-ads-allblockgeoip:privatedirectgeosite:cndirectUnmatched trafficproxyRouting does not send every request through the same outbound. It selects an outbound based on conditions such as the domain or destination address. Handle blocked requests and local network traffic first, add explicit domain categories next, then decide where unmatched traffic goes. In this diagram, proxy, direct, and block are outbound tags and must match your actual configuration. Rule sets also require the corresponding data files. Clear routing rules keep traffic handling predictable and make it easier to identify which rule matched when something goes wrong.
Rule order matters just as much as match conditions. Open the relevant section of the manual →A system proxy affects only apps that honor that setting. TUN captures more connections through a virtual network interface, so the two have different scopes. First test the subscription and server configuration with the system proxy. Then try TUN if your apps require it, rather than changing the connection method and DNS policy at the same time. DNS resolves domain names to addresses and can affect routing decisions. Unlike a browser-only setting, TUN also requires attention to permissions, routes, and other networking software. After enabling it, check websites, local network services, and name resolution separately.
TUN is not a universal fix for subscription errors. Open the relevant section of the manual →Choose a package for your platform
For desktop, start with v2rayN; for Android, start with v2rayNG. Match the package architecture to your device. Different interfaces or packaging for the same client do not mean you need to buy a new subscription or switch providers.
v2rayN offers a desktop edition and a classic WPF edition. The desktop edition uses a cross-platform interface, while the WPF edition retains its familiar layout. Choose the one that suits your workflow, then check that your system meets its requirements.
Keep your subscription groups and custom routes before updating. If the app fails to start, check the runtime requirements and extraction path first; avoid repeatedly overwriting your configuration.
Check your chip under About This Mac, then choose the Apple Silicon or Intel v2rayN package accordingly. The setup is much the same for both; the main difference is the runtime environment.
After installation, grant any permissions required by the system, then test the system proxy. If you already use another proxy app, quit it first to avoid conflicting settings.
v2rayNG uses the Xray core and is a good first choice for Android. If you need a V2Fly core, see v2flyNG. Most recent devices use arm64; if you are unsure of your device architecture, look for a universal build.
On the first connection, approve the VPN permission request. Before switching clients, disconnect the current one and check system background restrictions so permission or sleep issues are not mistaken for server problems.
Choose a deb or rpm package for your distribution, then check whether your system uses x64 or arm64. Start with the desktop interface to import a subscription and test the connection. Once the basics work, consider settings related to virtual network interfaces.
The desktop system proxy and terminal environment variables are separate entry points. If your browser works but command-line tools do not, check each separately rather than reinstalling the client or replacing the subscription.
First-time setup
These three steps establish a simple baseline you can verify. Menu names may differ between v2rayN on desktop and v2rayNG on Android, but the sequence is the same: import a configuration, choose how to connect, then check the results.
In subscription settings, add a group and give it a name that identifies its source. Paste the full subscription URL and update it. A share link usually describes a single server; a subscription URL retrieves multiple configurations. Do not infer the format from the URL length alone. After importing, check the server list and update log. Make sure the URL has no extra spaces, is not truncated, and is not a regular webpage address.
Subscriptions often contain access credentials. When troubleshooting, share only error messages with sensitive details removed; never post a full URL or QR code.
Select a server configuration and keep the basic routing settings for now. In v2rayN, enable the system proxy so browsers that follow system proxy settings use the client. In v2rayNG, start the connection and approve the system permission. Do not enable multiple proxy apps or change TUN, DNS, and routing all at once; otherwise, it will be hard to tell what caused a problem.
“Client started” only means the app is running. It does not mean every app is using the proxy; check the connection entry point separately.
Visit a website you use regularly, then check the client logs for connection or DNS errors and make sure local network devices are still reachable. If only one app has a problem, check whether it follows the system proxy. If all requests fail, review the subscription, server configuration, and network status. Once a test succeeds, add routing rules one at a time and keep a record of each change.
When you are done, turn off any system proxy settings you no longer need. Otherwise, apps may keep sending requests to a local port after the client has closed.
Project V · V2Fly · Xray
When comparing options, separate three layers: protocols define how communication works, cores handle connections and routing, and GUI clients make these capabilities manageable. Similar names do not mean identical features or configuration formats.
V2Ray's modular architecture and project history
The community-maintained V2Ray core
v2flyNGIndependent core derived from V2Ray
v2rayNGv2rayN can manage different cores; actual support depends on the selected core and configuration.
V2Ray is a network proxy tool in the Project V ecosystem. Its configuration separates features such as inbound and outbound connections, routing, and DNS. GUI clients put common settings in menus, but the underlying layers remain. Understanding this structure helps distinguish an app that never reached the local proxy from a request that entered the core but took the wrong outbound route. Not every connection problem means the server is unavailable.
V2Fly continues the community-maintained V2Ray project, while Xray grew out of V2Ray and has developed independently. They share some concepts and history, but protocol capabilities, supported fields, and defaults may differ. When you see a protocol name, check the transport, security settings, and core support too. A complete configuration for one core is not necessarily a general-purpose configuration for another.
v2rayN, v2rayNG, and v2flyNG are all open-source GUI clients. v2rayN is designed for desktop use and configuration management; v2rayNG and v2flyNG target Android and follow different core lineages. Open-source licenses set the terms for using, modifying, and distributing code; refer to each project's license for details. An open-source client does not mean its server operator, subscription service, and client project are run by the same organization.
Updating the client replaces the program; updating a subscription fetches the server configuration again. They solve different problems. If a protocol feature is missing, check the client and its core. If subscription entries have changed, review the subscription update log first. Keep custom rules before updating, then recheck system proxy settings and permissions afterward. Do not enable every new option just because it appears in the interface; a stable configuration should make the purpose of each setting clear.
The client does not provide server access. After installation, you still need to import a configuration you are authorized to use. Subscription validity, service terms, and account status depend on the subscription provider. This site focuses on client operation and configuration concepts. Before choosing, read the comparison of the three clients, and look up unfamiliar terms in the glossary.
Setup guides and troubleshooting
Once the basics are set up, find a guide based on the specific symptoms. Startup failures, a system proxy that does not work, and choosing a core are different issues. Identify which layer is failing before following a troubleshooting path; this is more effective than changing everything at once.
Desktop crashes are often caused by a missing .NET runtime, the extraction path, or administrator permissions. On Android, common causes include VPN authorization and background restrictions. Check the startup environment for your platform, then adjust permissions if needed. Reinstalling repeatedly can hide the original error rather than fix it.
Read the article →From Project V's origins to community work on V2Fly and the Xray fork, this guide explains how cores and GUI clients differ. Understand the core differences between v2rayNG and v2flyNG, then choose based on your configuration needs—not just the name.
Read the article →If you are connected but webpages will not load, troubleshoot browser extensions and system proxy settings separately from terminal environment variables. This guide covers the order for checking PAC mode, bypass lists, and port conflicts, helping you distinguish an app entry-point issue from a connection problem.
Read the article →