Start with the Desktop edition. Choose WPF if you prefer the classic interface or follow a guide that uses it. Both support the same proxy protocols.
Go to downloadsV2Ray Guide HubDownloads & Setup
Choose an open-source client for your device, import a subscription, then configure routing rules.
The core determines which protocols and transport settings are supported.
Licensing varies by project; the core and the interface are maintained separately.
Download a V2Ray client for your OS
Check your operating system and CPU architecture before choosing a package. Start with v2rayN on desktop or v2rayNG on Android; consider v2flyNG only when your configuration specifically requires V2Fly.
Check “About This Mac”: choose arm64 for Apple silicon or x64 for Intel. Subscription and routing setup is the same for both.
Go to downloadsStart with v2rayNG (Xray), or choose v2flyNG for an existing V2Fly setup. Pick the slim arm64 package if supported; otherwise, use the universal package.
Go to downloadsChoose deb for Debian-based systems or rpm for Fedora-based systems. Match the package to your CPU (x64 or arm64), then launch v2rayN from your app menu.
Go to downloadsSubscriptions, proxy modes, and routing
A subscription tells you which nodes are available. Proxy mode determines which traffic enters the client, while routing determines which outbound handles that traffic. When a connection fails, identify the layer involved before changing its settings.
Save a subscription URL as an updatable group
In v2rayN, open “Subscription group settings,” enter a group name and subscription URL, save, then use the subscription menu to update it. In v2rayNG, add the URL under “Subscription group settings” in the sidebar, then update from the main menu. Unlike importing a single share link from the clipboard, a subscription repeatedly fetches the same URL, so the list may change after an update. If the list is empty, first check that the URL returns subscription data rather than a login page, then verify which group is currently selected.
Subscription group settings → Update subscription
Check whether the app uses the system proxy
In the v2rayN tray menu, select “Set system proxy” and test with a browser that follows the system proxy. Unlike entering a local port manually in one app, the system proxy uses a shared OS setting; unlike TUN, it does not capture traffic from every app. Some programs have their own proxy settings, while others ignore the system setting. Before exiting, use “Clear system proxy” to restore the previous setup—especially if the system still points to a local port that is no longer listening.
Set system proxy / Clear system proxy
Choose an outbound based on the destination
In the client's routing settings, select a rule set and check the order of its rules. The core checks them in sequence and uses the specified outbound for the first match. Put narrow exceptions, such as local network rules, before broader rules. Routing by destination preserves access paths for local services instead of sending all proxied traffic through the same outbound. The example below matches private addresses only; before using it, define an outbound named direct in the configuration and check whether domain requests are also matched by address.
{
"type": "field",
"ip": ["geoip:private"],
"outboundTag": "direct"
}
Route apps that don't use the system proxy
First verify that the node works through the system proxy, then clear the system proxy and enable “TUN mode” to compare the two connection methods. TUN receives traffic through a virtual network interface, so apps don't need to read proxy settings; enabling it may require system authorization. After switching, test name resolution, commonly used apps, and local network services. If problems occur only with TUN enabled, turn it off to restore the previous setup, then check for other virtual interfaces, conflicting routes, or different DNS settings.
Enable TUN mode
Check the core type against configuration fields
On desktop, check the core type alongside the node protocol, transport, and security settings. In v2rayN's node editor, check “Core type” and use the options available for the current node. Switching cores is not the same as switching nodes: the server address may stay the same, but a different program reads and runs the configuration. Save the original settings, change one item, and test against the same destination. On Android, when comparing the two cores, check which settings each client supports rather than looking for the same menu as on desktop.
Edit node → Core type
A successful connection doesn't mean a rule matched
An enabled proxy status only shows that the client has a connection method configured. To check whether a rule is working, verify that the app's traffic enters the client, whether the request uses a domain or an IP address, and whether a broader rule matched earlier. Test one local destination expected to connect directly and one destination expected to use the proxy; this is more useful than checking a single page load.
Keep settings that already work
Record the current node, connection method, and routing configuration before trying something new. If you change the node, enable TUN, and change DNS all at once, it's difficult to find the cause if things fail. To roll back, undo changes one at a time in reverse order. You can record setting names and results, but don't include publicly accessible subscription URLs.
From importing a subscription to testing the connection
Make your first connection with one configuration, one connection method, and two test destinations. Establish a reproducible baseline before adding more nodes and rules.
-
Import a subscription and select a node
Open “Subscription group settings,” add the URL, and update it. Once the list appears, return to the main screen and select a node. If you have a
vmess://orvless://share link, import it from the clipboard instead of pasting it into the subscription URL field.If you have multiple subscriptions, name them and switch to the group you just updated to avoid testing an old configuration. If you import just one share link, you'll need to import it again or edit it manually when its parameters change; updating a subscription won't replace it automatically.
-
Connect the app you want to test
In v2rayN, start by setting the system proxy from the tray menu, then test with a browser. In v2rayNG, select a configuration, tap the connect button, and approve the system's network connection request. The connection methods differ, but both require you to select the current node first.
If a desktop browser works but another app doesn't connect, check whether that app has its own proxy settings. On mobile, if another app is already using the system's virtual network interface, check which app currently controls it before reconnecting.
-
Test direct and proxied connections separately
First open a destination you can normally access to confirm the app can make requests. Then check one local service expected to connect directly and one destination that should use the proxy according to your rules. Compare the client logs to see whether both requests reached the core and used the expected outbound.
If both destinations fail, first check whether the connection was established. If only one fails, check its routing rules and DNS resolution. Test again after disconnecting to rule out a misleading result caused by page caching and to confirm that the system's original network settings have been restored.
Project V, V2Fly, and Xray
The GUI client lets you edit settings; the core reads the configuration and handles connections. Keeping these layers separate helps you identify whether to check the interface, protocol parameters, or rule execution.
From Project V to community maintenance
Project V is the name of the original project ecosystem, and V2Ray is its proxy core. The early project used inbound, outbound, and routing components to separate receiving connections, choosing a path, and making connections, allowing one configuration to handle different types of requests. The V2Fly community later continued core development and documentation. In everyday usage, “install V2Ray” often means installing a GUI client. When troubleshooting, identify the specific software first: different clients may generate or modify the same rule before it reaches the core.
V2Fly and Xray compatibility
Xray originated as a fork of the V2Ray core and is now maintained independently. It still shares many configuration concepts with V2Fly, such as matching rules by domain or address and referencing defined outbound tags, but the available parameters aren't identical. VMess, VLESS, and Trojan are protocol names; REALITY is a transport security mechanism, not a node type interchangeable with the other three. When you receive a configuration, check its protocol, transport, and security layer. A protocol appearing in a dropdown doesn't guarantee that all remote requirements are met.
What the three GUI clients are for
v2rayN is for desktop devices, bringing node lists, subscription groups, and proxy settings together in one interface. v2rayNG is for Android and uses the Xray core; v2flyNG is also for Android but uses the V2Fly core. All three clients are open source, but their capabilities depend on the core and on which configuration options the client supports. If you already have a working node, use its parameters to determine which core you need before switching apps. If the only difference is where a menu appears, check the guide for that client instead of reconfiguring the server.
Open-source licenses and what downloads include
The core code for V2Fly and Xray is licensed under the Mozilla Public License 2.0. The license sets conditions for using, modifying, and distributing code; it doesn't describe runtime requirements or protocol compatibility. Clients and cores are separate projects, so check each project's license. Downloading a client doesn't give you access to a remote service: the installer provides configuration and connection tools, while subscriptions and nodes come from independent sources. Check what a link contains before importing it, and hide credentials, subscription identifiers, and private addresses in screenshots you share.
Track four types of changes separately
A client update may move menus or change default settings; a core update may affect which parameters are accepted; a ruleset update may send the same destination through a different outbound; and a subscription refresh may change the available node list. These changes can happen at different times. If something that worked yesterday now fails, first recall which layer was updated most recently. Keep the configuration that worked and retest against the same destination on the same network. If parsing fails, check configuration fields first; if the connection succeeds but uses the wrong outbound, check rule order and match conditions.
V2Ray speed troubleshooting and setup guides
A slow page after connecting and a connection that won't establish are different problems. These notes cover performance, local network access, and protocol fields so you can find guidance by symptom.
How to troubleshoot slow V2Ray speeds: Check the node, network path, and local settings
Troubleshoot layer by layer: node load → network path quality → transport settings → local proxy mode and DNS. Each step includes checks you can run directly in the client.
First distinguish a slow connection handshake, slow DNS resolution, and low sustained throughput. They may have different causes. Change one setting at a time, record the test destination and connection method, then compare the results.
Allow LAN connections in v2rayN: Share your PC's proxy port with phones, TVs, and tablets
After enabling LAN connections, note your computer's local IP address and SOCKS/HTTP ports. Configure the proxy on other devices, allow access through the firewall, and keep the network boundary secure.
First confirm that the two devices can reach each other. Limit the proxy listener and firewall rules to the trusted local network that needs access.
VMess vs. VLESS in a minute: Encryption, UUIDs, and transport layers
No deep dive into obscure details—just the points that matter to everyday users: how the protocols differ in encryption, authentication, and transport options, and what to choose in your client.
Choose a node type based on the remote configuration. Two configurations using the same UUID format doesn't mean their protocols or security settings are interchangeable.