Choose an open-source client for your platform, follow the guides to import subscriptions and configure routing, then check node and core compatibility in the protocol reference.
Check your operating system and processor architecture before choosing a package. The package determines whether the app runs on your device; the proxy protocol determines which core handles the connection. These are separate choices: after installation, configure the node using the parameters supplied with your subscription or by the server.
v2rayN Desktop has a cross-platform interface; Classic uses WPF. Check the system requirements before installing and locate your settings folder before switching editions.
If v2rayN won't start, check the CPU architecture, required desktop runtime, and write permissions for the folder you extracted it to.
Choose v2rayNG for Xray or v2flyNG for V2Fly. Both offer ARM64 and universal packages. Pick ARM64 if your device supports it.
Allow the VPN connection when Android prompts you. If another VPN is active, disconnect it before retrying. Test the same node on Wi-Fi and mobile data.
Subscriptions provide nodes; the system proxy and virtual network interface determine how traffic enters the client; routing rules decide which outbound connection it uses. During initial setup, change one layer at a time: verify a single node, check that the target app is sending traffic through the client, then enable routing rules. This gives you a known set of settings to compare against if something goes wrong.
Settings / Subscription Groups
Subscriptions make it easy to manage a changing set of nodes. Create a group, enter the subscription URL provided by your service in the optional address field, and update it. If you only have a single share link, import it from the clipboard instead of treating it as a subscription URL. After the list updates, select one node and test the connection before checking the others. If the update succeeds but no entries appear, check whether the response uses a subscription format the client can read and whether you selected the right group during import. Keep manually added nodes in a separate group so they do not get mixed up with subscription entries.
Subscription Groups
Add Subscription Group
Optional address
Enter the subscription URL provided by your service
Update Subscription
Update the current subscription group
Settings / System Proxy
Automatic system proxy setup registers the client's local proxy with the desktop operating system. It works for browsers and apps that follow system settings. Start with a node you know works, enable the system proxy, and try the connection again. Testing the node from the client alone does not confirm that an app is using this proxy entry. Apps with their own proxy settings may still connect directly or use a saved address. Check the proxy type and port in the app first; if you need to route traffic from more apps, consider TUN mode and its permission requirements.
System Proxy
Set system proxy automatically
Stop Test
Clear System Proxy
Settings / Routing
After traffic enters the client, routing rules choose an outbound connection based on the domain, address, or other conditions. Start with an existing ruleset and test destinations expected to go direct and through the proxy before adding custom entries. Put specific exceptions before broader rules, and check which outbound connection handles traffic that matches no rule. Domain and address rules also depend on whether the core receives a hostname or a resolved address. If only some sites fail, check rule matches and name resolution before switching nodes or reinstalling the client.
Routing Preset Example
Bypass mainland China
outboundTag
Choose a direct or proxy route based on the matching rule
Settings / TUN
A virtual network interface is useful for apps that ignore system proxy settings but need their traffic routed through the client. Before enabling it, check the required permissions, temporarily quit other tools that may change system routes, and note your existing proxy settings. After enabling TUN, test your usual apps, name resolution, and local network access one by one. Do not judge the setup by a single webpage. If local devices become unreachable, disable TUN to compare, then check the traffic capture scope and route exclusions. Change only one thing at a time while troubleshooting; otherwise, it is hard to tell what caused the change.
TUN Mode
Enable virtual network interface
Automatic routing
Configure for the active network interface and traffic scope
Settings / Core Type
The core interprets node settings and establishes outbound connections; after switching cores, fields in an existing configuration may not mean the same thing. For nodes that require REALITY and Vision, choose an Xray core that supports both. With an existing VMess configuration, check the transport and security settings as well—protocol names alone do not determine whether a configuration can move between cores. If the client lets you switch cores, duplicate the node first, then compare startup logs and connection results. On mobile, you can also test with a client that uses the corresponding core.
Core Type
Xray / V2Fly (depending on client options)
flow
Use Vision flow control only when required by the node
Settings / Subscriptions Across Devices
Add the same subscription URL separately on desktop and mobile, then update the node list on each device. This syncs the nodes provided by the subscription, not the selected node, system proxy status, or local rules—and it does not share an account between clients. When moving to a new device, create a group there, update it, and check the node count and protocol types. Then configure the traffic entry point and routing for that device's network. If a node is missing on just one device, check the update result and subscription format first. Before sharing troubleshooting screenshots, hide the subscription URL and user identifiers.
Subscription URL
Enter it separately in each device's subscription group
The client provides the configuration interface, the core runs the connections, and the protocol defines how the two endpoints communicate. A single client can support multiple configurations, and the same protocol name may cover only some of the same transport and security options across different cores.
How Project V Is Structured
Project V is the open-source ecosystem that includes V2Ray. V2Ray's core design separates connections into inbound, routing, and outbound stages: inbound receives app traffic, routing selects an exit, and outbound establishes the connection using the relevant protocol. Graphical clients map these pieces to node lists, proxy toggles, and routing options. A lit connection indicator usually means only that the relevant service is running; it does not mean your browser, terminal, and other apps are all using the same proxy entry.
For example, a browser and a command-line tool may access the same domain differently: the browser might follow the system proxy, while the command-line tool might read only environment variables. Even with the same domain and node, one may work while the other fails. First determine whether the problem occurs before traffic reaches the client or during the outbound connection; this is more useful than repeatedly refreshing the subscription. If the log shows no connection from the target app, check that app's proxy settings. If a connection is logged, inspect the matched rule and outbound result.
Core Families and Configuration Compatibility
V2Fly continues the community maintenance of V2Ray, while Xray developed independently after branching from related code and added capabilities such as REALITY. They share some concepts and configuration structures, but they are not two names for the same program. Choose a core based on the server requirements: check the proxy protocol, then the underlying transport, security layer, and flow control, and finally confirm that the client passes all required fields to the core. Seeing a node name and server address in a subscription only confirms that the client read some of its contents.
When testing across cores, keep the original configuration for the same node; do not delete an entry that currently works. If switching cores adds or removes a field in the editor, check whether that setting is configured elsewhere or whether the combination is unsupported. A configuration error during startup and a handshake failure after startup are different starting points for troubleshooting: first check which fields the core supports; then verify that the values match the server. Compare Xray and V2Fly.
Protocols, Security Layers, and Flow Control
VMess, VLESS, Trojan, and Shadowsocks are proxy protocol options. In Xray's VLESS configuration, REALITY appears under transport security and Vision under flow control. A share link beginning with VLESS identifies the proxy protocol, but does not tell you which security layer it uses or whether it uses Vision. Use the node's parameters when editing it; do not apply the same security settings to every configuration. The server name in a standard TLS configuration also cannot replace the other parameters required by a REALITY node.
Public protocol specifications and open-source implementations can help explain what each field does, but protocol names alone do not predict real-world speed or battery use. To compare configurations, use two confirmed working setups on the same device and network, at roughly the same time, and run the same task. Evaluate page load time separately from sustained transfers. On a phone, also note whether switching Wi-Fi networks triggers repeated reconnects; one connectivity test does not represent the full experience.
Clients, Cores, and Rules Update Separately
v2rayN is an open-source desktop client, commonly used to edit servers and manage subscription groups. v2rayNG is an open-source Android client that primarily uses Xray; v2flyNG is an open-source option for Android users who need the V2Fly implementation. Each project maintains its own interface and release packages. Even with the same subscription on two devices, menus, local listening behavior, and system permissions may differ. A desktop configuration directory cannot replace subscription groups or network settings on a phone.
Before updating, identify what you plan to change. Updating the app package may affect menus, runtime dependencies, or how the core is invoked; changing only the core primarily affects protocol and field support; updating a subscription refreshes nodes; updating routing data can change some match results. To find out what caused an issue, note the working node, proxy mode, and routing preset, then make one update and retest with the same app. If the network also changed, treat that as a separate variable. Read the protocol and core reference.
Recent Technical Articles
Start with the stage where the problem occurs: check platform notes if the app will not start, investigate the traffic entry point if it is running but an app cannot connect, and review security layers and flow control when choosing a node protocol.
Starting with the TLS handshake, this guide explains how REALITY handles certificates and how Vision reduces redundant encryption. When comparing connection speed, CPU usage, and battery drain, assess the handshake separately from sustained transfers.
Check the system proxy and local listener first, then verify node settings and system time. Finally, investigate routing mismatches, name resolution, and virtual network interface conflicts. Following these steps helps avoid repeatedly changing subscriptions when the node is working.
Distinguish developer verification on first launch from network permission issues after the app is running. Use the system prompt to identify whether the issue affects app startup, local network access, or proxy settings, then grant the relevant permission.