For readers with existing nodes or subscriptions who are choosing a client or switching devices. Narrow down your options by operating system, then check your node’s protocol, transport, and security layer. Finally, test with one node and two apps to distinguish successful import, a working core connection, and app traffic reaching the client.
Platforms and Cores: Rule Out Incompatible Clients First
A client imports, edits, and manages nodes; the core establishes connections and applies routing. v2rayN is a desktop client that can use different cores depending on the node type and local version. v2rayNG and v2flyNG are both for Android, but use the Xray and v2fly cores, respectively. Similar interfaces don’t mean they can read the same configuration.
v2rayN
RecommendedThe go-to desktop option for Windows, macOS, and Linux. Choose an installer for your operating system and CPU architecture. The Windows desktop and classic WPF editions may have different menu layouts. When troubleshooting, check which core the node actually launches.
Best for: desktop subscription management, system proxy settings, and routing rule troubleshooting
v2rayNG
An Android client powered by the Xray core. If a node specifically requires REALITY or XTLS Vision, first check that your client version and node editor support the required fields.
Best for: using Xray nodes on Android and routing traffic by app
v2flyNG
An Android client powered by the v2fly core. Consider it when the node was specifically provided for v2fly, or when you mainly use VMess over WebSocket with TLS. Check the transport and security layer too—protocol names alone aren’t enough.
Best for: Android configurations confirmed to work with v2fly
How to Choose: Test the Node That’s Hardest to Support
If your subscription includes both VMess and a REALITY node you need, don’t choose a client based only on testing VMess. Import the REALITY node, make sure its required fields are preserved, then use it to access a real destination.
Protocol Compatibility: Check the Protocol, Transport, and Security Layer Separately
VMess and VLESS are protocols, WebSocket is a transport, and TLS and REALITY are security layer options. XTLS Vision is a flow control option in VLESS configurations, commonly set to xtls-rprx-vision. So, being able to import VLESS doesn’t guarantee that a client can use a particular VLESS node: an importer may recognize the link prefix but fail to preserve all security layer or flow control parameters.
| Node configuration | Preferred option | Check after import |
|---|---|---|
| VMess + WebSocket + TLS | All three can be tested against the actual configuration, depending on the version | Address, port, WebSocket path, request Host, and TLS server name |
| VLESS + REALITY | Use v2rayN with Xray on desktop; use v2rayNG on Android | Check that the security layer, server name, public key, short ID, and other fields match the original configuration |
| VLESS + XTLS Vision | Use an Xray version that supports this flow control option | Check flow, along with the transport and security layer required by the node |
Don’t switch the security layer to TLS just because the port is 443, and don’t remove flow control fields just to make an older client save the node. The port doesn’t tell you which protocol the server is running. To compare compatibility, keep the original configuration and change only the client. Changing the path, port, and security layer at the same time makes the results hard to interpret.
Moving a Subscription: Share the Source, Not Local Settings
A subscription provides a node list; it isn’t a backup of all your client settings. Even when two clients use the same URL, their results can differ because of their importers, core support, or update timing. When switching for the first time, keep the working configuration in your old client, add the subscription as a group in the new one, then update and check the nodes you rely on. A matching node count doesn’t prove compatibility.
Switching Between Devices: Test Nodes Before Restoring Split Tunneling
Desktop: v2rayN
- Go to “Subscription Group” → “Subscription Group Settings” to add the URL, then update the active group from the “Subscription Group” menu. Older versions may label the menu “Subscription.”
- Select a known working node and check its details and runtime log. Once the connection is confirmed, enable the system proxy mode you need.
- Note your existing direct-connect domains, local network access needs, and fallback rules separately. Your apps’ system proxy settings aren’t part of the subscription.
Android: v2rayNG or v2flyNG
- In v2rayNG, open “Subscription Group Settings” from the top-left menu and add the URL. Return to the configuration list, open the top-right menu, and select “Update Subscription.”
- First test a node known to work with the current core. When you start VPN mode for the first time, grant permission when prompted by Android.
- After testing with the default settings, restore your per-app proxy list. Then retest with one app included in the list and one excluded.
A subscription syncs the source of your nodes. Choose the core and confirm routing, DNS, and app traffic settings separately on each device.
Traffic and Routing: Make Sure Traffic Reaches the Client First
A desktop system proxy usually affects only programs that follow the system proxy settings; programs that ignore them may still connect directly. On Android, VPN mode uses VpnService to capture traffic, while per-app proxy settings determine which apps enter the VPN. The core’s routing then decides whether captured connections go direct, through the proxy, or to another configured outbound. If an app isn’t routed through the VPN, changing core rules won’t change how it connects.
- Check the listener. In v2rayN, go to “Settings” → “Parameter Settings” and check the local listening ports. Some versions offer a mixed inbound; others have separate SOCKS and HTTP settings. If you set an app’s proxy manually, match both the port and inbound type. Don’t enter the remote node’s port as the app’s local proxy port.
- Check traffic capture. On desktop, start by testing a browser that follows the system proxy, then check the target program’s network settings. On Android, check the list under v2rayNG “Settings” → “Per-app proxy,” and confirm whether selected apps are included or excluded.
- Check routing rules. Test one destination that should connect directly, then one that should use the proxy. When editing custom routes, make sure specific rules come before broader ones. For domain-based rules, also compare access by entering a domain name versus entering an IP address directly.
Common Issues After Switching Clients
Why are some nodes missing on Android with the same subscription?
First, check that the update succeeded and both clients are using the same subscription group. Try importing a share link for one missing node. If it’s unsupported, check the protocol, transport, security layer, and flow control instead of repeatedly refreshing. If the link imports on its own but the subscription still omits the node, check whether the subscription’s response format is supported by that client.
Why can’t my browser connect when v2rayN’s node test shows latency?
First, check what the test measures. A TCP probe only shows that the remote port might be reachable; even a successful proxy test doesn’t prove your browser is using the proxy. Check that “System Proxy” in the tray menu is set to “Automatically configure system proxy,” then see whether the browser has its own proxy settings. Finally, visit a site to generate logs and check whether the failure occurs during DNS resolution, connection, or handshake.
Can I use the same node with both Android clients, one at a time?
Yes, if the node is supported by both clients; test each one separately. Stop the active client’s VPN before starting the other. If Android has always-on VPN enabled, check which app it’s bound to. Keep the network, node, and target app the same for both tests so differences in per-app lists aren’t mistaken for differences between cores.