System ProxySet System Proxy AutomaticallyClear System ProxyLeave System Proxy Unchanged
RoutingBypass Mainland China ▾Enable TUN
Routing Ruletype: fielddomain: geosite:cnoutboundTag: direct
DNS Settingsdns.servers→ https://1.1.1.1/dns-query
FakeDNS
v2rayNG
VPN ModeProxy Only
VLESS
VMess
Trojan
Connect
VLESS
REALITY
Xray
Configuration Layers
v2rayN Core Settings
Subscriptions determine where the server list comes from. System proxy or TUN determines which traffic reaches the client, and routing determines where that traffic goes. When troubleshooting, check these three layers separately instead of resetting everything at once.
Add Subscriptions by Source
Subscription Groups → Subscription Group Settings → Add
Save subscriptions from different sources separately and give each group a recognizable alias. Before updating, select the group you want and use the option to update the current subscription; update all only when you need to refresh every group. Unlike adding servers one by one, a subscription update reloads the list returned by its source and may overwrite manual changes. Save any manual configurations you need to keep separately. If an update fails, check whether the error is a download failure or a parsing issue before changing settings.
This rule sends requests matching the specified domain set to the outbound named direct. To use it, your configuration must define that outbound and include the required rule data. Routing is separate from the system proxy toggle: rules are matched in order only after traffic reaches the core. Put specific exceptions before general rules, change one thing at a time, and test addresses that should go direct as well as those that should use the proxy. If a request falls through to the default outbound, first check whether the client received a domain name or an IP address.
This configuration sets a DNS over HTTPS resolver endpoint for the core; it does not automatically change DNS settings for every app. A browser with secure DNS enabled may still use its own resolver. To troubleshoot domain access, first check whether the app passes domain names to the client, then whether the core can reach the resolver endpoint. Note which domains are affected. Avoid changing the resolver and routing policy at the same time, or it will be hard to tell which change fixed the issue.
The system proxy works only when an app reads the proxy settings. TUN uses a virtual network interface to receive traffic sent through system routes. First confirm that your platform supports TUN and grant any required system permissions. Then enable TUN with other traffic-routing tools turned off, and check the target app and local network access. If the problem disappears when TUN is disabled, investigate the virtual interface, default route, and local network exceptions before reinstalling the client or changing subscriptions.
After importing a server, check its protocol, transport, and security settings, then confirm that the selected core supports those fields. Even when two cores support the same protocol, they may differ in supported combinations and configuration fields. Before switching, note the current core and settings, test one server, and check the startup log for unrecognized fields. If startup fails, fix the configuration issues reported in the log; a server appearing in the list does not mean the configuration is compatible.
Use v2rayN on desktop. On Android, choose between v2rayNG and v2flyNG based on the core you need. Check your device's processor architecture before downloading; packages for the same client may target different chips or installation formats.
The download page lists the v2rayN desktop edition and the classic WPF edition. The desktop edition uses a cross-platform interface. If you prefer the familiar layout or are following an older guide, check the classic WPF instructions. The interfaces may place controls differently, so look for features by name—such as subscription groups, routing, and system proxy—instead of matching screenshots item by item.
Before downloading, check your system type under Settings → System → About. For your first connection, select one server and test it in a browser that uses the system proxy. Consider TUN only if you need to cover other apps. After quitting, if the system still tries to connect through a local proxy, check whether the system proxy settings have been restored.
Check the chip or processor under About This Mac. Choose arm64 for Apple silicon and x64 for an Intel processor. The installers target different architectures, so the OS name alone is not enough to choose one. After installation, open the client to confirm it reaches the main screen, then add a subscription.
An app that will not open and an app that opens but cannot configure a proxy are two different problems. For the first, check the system's app-opening warning. For the second, check network permissions and proxy settings. Managed devices may restrict these settings; do not assume that means you chose the wrong installer.
Choose v2rayNG if you need the Xray core, or v2flyNG to match a V2Fly configuration. Confirm that your system supports arm64 before choosing the corresponding installer; if unsure, check the universal build. The installer architecture determines whether it can be installed on your device, while core selection determines whether it can handle the protocols and transport fields in your subscription.
If the system reports an installation conflict, first confirm that you are updating the same app and check the specific reason shown. Before uninstalling and reinstalling, make sure you can restore your subscriptions and local settings. When granting VPN permission for the first time, also check whether another app is already using the VPN connection.
Choose a package format for your distribution: Debian and Ubuntu typically use deb, while Fedora and openSUSE typically use rpm. Then select x64 or arm64 to match your system architecture. A matching package format does not guarantee that all dependencies are installed. If the installer reports missing components, resolve those dependencies first, then check for the desktop menu entry.
These instructions assume a graphical desktop session. If the app opens but traffic does not use the proxy, first check whether your desktop environment applies system proxy settings, then whether the target app reads them. A successful browser test does not prove that another app uses the same settings.
Before migrating, separate subscription URLs, manually added servers, and device-specific settings. You can add subscription URLs again on the new device; save manual entries separately. System proxy settings, virtual network interfaces, and per-app routing are usually device-specific and should be checked again on the new device. If a backup contains subscription links or connection details, store it separately from screenshots shared publicly for troubleshooting.
Start with a minimal setup on the new device: add one source, select a known working server, and test one connection mode. Once the basic connection works, restore custom DNS and routing rules one at a time. If even the basic setup fails, check the architecture, core, and permissions first rather than relying on the entire old configuration.
The client provides the interface for settings and configuration management; the core establishes connections and applies routing rules. These projects can release independently, so troubleshooting means knowing both where a setting appears in the interface and which core actually handles it.
How the Project V Ecosystem Fits Together
Project V is the name of an early project ecosystem, with V2Ray as its core proxy software. As the original project evolved, the community carried on its maintenance and releases through V2Fly. Xray branched from related code and has developed independently. Names shown in a client may refer to the wider ecosystem or to a specific running core, so use the context to tell them apart when following a guide.
A graphical client organizes subscription entries into selectable server configurations and translates routing and network-mode settings into options the core can use. If no servers appear, first check the import or update. If a server is selectable but the core will not start, check the logs before importing the same address again.
Core and Protocol Compatibility
To decide whether V2Fly or Xray suits a configuration, check the protocol, transport, and connection security mechanism together. VMess, VLESS, and Trojan are protocol names; WebSocket is a transport; REALITY is a connection security mechanism. A protocol abbreviation in the server list alone does not show whether the other fields are supported.
For example, if a server requires VLESS with REALITY and a specific flow setting, use a core that supports the full combination and configure it with the server's parameters. Do not just change the protocol menu to VLESS. When migrating a full configuration, check DNS and outbound fields too: compatible connection settings do not guarantee that the same custom routing rules will work unchanged.
Three Open-Source Clients at a Glance
v2rayN is a desktop graphical client released under GPL-3.0, with subscription, core selection, routing, and network-mode settings. v2rayNG and v2flyNG are open-source Android clients for Xray and V2Fly, respectively. They manage connection settings on your device; they do not provide subscriptions or remote servers.
When reviewing licenses, distinguish the client from the cores and other components used with it. The client's open-source license covers the terms applicable to its code; check the licenses for cores and other components separately. Getting a client for free does not grant access to a remote service; that depends on the service provider.
Client, Core, and Subscription Updates
Client releases may change the interface or platform support; core releases may change configuration fields or protocol support; refreshing a subscription reloads the server list provided by its source. These updates are independent: a successful subscription refresh does not mean the app has been upgraded, and the same client download does not guarantee that subscriptions from different sources will behave alike.
Before updating, note the core, routing setup, and connection mode you use. Afterward, retest one task that worked before, then re-enable custom settings. If a problem started after a subscription refresh, compare the changes in that group first. If it began after a client update, check for migrated settings or core startup warnings.
Field Notes
Core Selection & Protocol Notes
Choosing an Android client? Start by comparing Xray and V2Fly. To tell whether a name refers to a graphical client or a core, review the ecosystem overview. If you already have a REALITY configuration, check the security mechanism and flow fields to avoid confusing two separate settings.
Illustrated with handshake diagrams, this guide explains how REALITY borrows TLS characteristics from a target website, how XTLS Vision reduces redundant encryption, and how to enter flow and public key parameters in a client.
From Project V's origins and the V2Fly community takeover to the Xray fork, learn how v2rayN, v2rayNG, and v2flyNG use cores and which open-source licenses they adopt.
Explore why Xray and V2Fly diverged, how protocol support and configuration compatibility differ, and how to choose v2rayNG or v2flyNG for Android based on your subscription's protocols.
Subscription updated successfully, but why can't I connect?
A successful update means the client received a server list. After selecting an entry, check whether the core starts and whether the app sends traffic through the client. Then use the troubleshooting guide to distinguish connection failures from DNS resolution issues.
Why does just one app bypass the proxy?
First check whether the app reads the system proxy, has its own proxy configured, or is excluded in VPN mode. Only after confirming that its traffic reaches the client should you check routing rules and outbound tags.
How do I troubleshoot after changing DNS or TUN?
Switch back to the last working mode, keep the server unchanged, and test common apps and local network access. Then restore DNS or TUN settings one at a time. If a change brings the problem back, use the FAQ to troubleshoot that setting layer.
Can one subscription be used with two different clients?
Whether a client can read a subscription depends on its returned format; whether it can connect after import depends on the core and configuration fields. Simultaneous use on two devices is a separate matter governed by the service provider. See subscription and server terminology to distinguish these three questions.