At a glance

Installing for the first time or moving to a new device? Narrow down your options by operating system, then check the subscription format and node core requirements. Learn how to tell whether one subscription works on both desktop and Android, and how to distinguish download failures, import issues, and apps that bypass the proxy after connecting.

Platform and interface comparison

ClientPlatformCore optionsWhere to manage it
v2rayNWindows、macOS、LinuxChoose based on the node configuration and cores available in your versionManage nodes and subscription groups in the main window; configure the system proxy or TUN separately
v2rayNGAndroidXrayManage nodes and subscriptions in the node list and subscription settings; approve the VPN prompt when starting
v2flyNGAndroidv2flyManage subscriptions and nodes in the Android interface; approve the VPN prompt when starting

On desktop, first check the operating system and processor architecture. For example, for a macOS installer, choose ARM64 for an Apple chip or x64 for an Intel chip. On Linux, check the package format used by your distribution as well as the architecture. Whether an installer runs on your device is separate from whether a subscription can be imported; changing subscriptions won't fix an installer that won't open.

On Android, subscription management and system authorization are separate steps. Updating a subscription loads the remote configuration into the local list. After selecting a node and starting the client, the system's VPN connection request determines whether traffic is routed through it. Seeing a node name doesn't mean the client is running or that an app's traffic is being proxied.

Choosing an Android client: Xray or v2fly

The client reads share links, manages the node list, and generates the runtime configuration; the core uses that configuration to establish connections. Switching clients can affect both import parsing and core behavior. Compatibility isn't just a matter of whether VLESS or VMess is supported: check that the current version supports the transport, security layer, and required parameters too.

v2rayNG: Xray core

Recommended

Choose this first when the subscription documentation explicitly requires Xray. For VLESS nodes using REALITY, also check that the current client imports the relevant fields correctly; seeing the node name in the list isn't enough.

Best for: Providers that specify Xray, or troubleshooting against an Xray configuration on desktop.

v2flyNG: v2fly core

If you already have a configuration tested with v2fly, you can keep using that core. For example, with a VMess and WebSocket configuration, check the path, hostname, and TLS settings. Using the same protocol doesn't mean those fields can be skipped.

Best for: Subscriptions that explicitly provide a v2fly configuration, or migrating existing v2fly nodes.

How to choose: Test a representative node first

For subscriptions with mixed protocols, test the node you actually plan to use long term: import it, start the client, and verify access. Other nodes connecting successfully doesn't prove that the one you need is compatible.

Subscription formats and node fields

A subscription URL returns configuration; a single-node share link describes one node. They may use different import paths in the interface: add a subscription URL in the group settings and update it, while importing a single-node link such as vmess:// or vless:// through the node import option. An HTTPS URL alone doesn't tell you whether all three clients can parse its contents.

  1. Check the output format. If the provider offers a client-specific option, use the format it recommends. Common outputs include share links on separate lines and lists of links encoded with Base64. Even if two clients accept a subscription URL, they may not support the same output format or set of additional fields.
  2. Check which group you're updating. In v2rayN's main window, open “Subscription Groups” → “Subscription Group Settings,” save the URL, select the relevant group, and update it; menu wording may vary by version. On Android, save the URL in Subscription Group Settings in the side menu, then update subscriptions from the main screen. Check the group you updated—don't judge the result by stale nodes in another group.
  3. Inspect the parsed result. Check the protocol, transport, and security layer in the node details. For WebSocket, the path and hostname are separate fields; when using TLS, don't substitute the node remarks for the server name. Keep the provider's original values—don't remove security fields just to get a configuration to parse.

Testing connections on desktop and Android

10808
Common SOCKS or mixed inbound port examples in v2rayN
10809
Example port for a separate HTTP inbound in some v2rayN configurations

These are examples of local desktop inbound ports—not remote node ports or values to enter when authorizing the Android VPN. Depending on the version and configuration, v2rayN may use a mixed listener or separate listeners. Check the active inbound type and port under “Settings” → “Parameter Settings.” If only a mixed listener is enabled, don't assume a separate HTTP port is running.

Test on both devices: check the same node separately

Desktop: v2rayN
  • Select the node you want to test and check the core startup log for configuration or listener errors.
  • For a system proxy test, check whether the target app uses the system settings. For manual setup, use the local port that matches the proxy type.
Android: choose a client based on the core
  • Update the relevant subscription group, select the same node, start the client, and approve the system VPN prompt.
  • Make sure the test app isn't excluded by per-app rules, then test the same destination you used on desktop.

You can use the same subscription on both devices, but node selection, update timing, and local routing rules are stored separately and don't sync automatically.

Switching clients and import FAQs

Why is my subscription empty on my phone when it has nodes on my computer?

First, make sure the phone updated the group you just saved, then check the update log. If the request timed out, troubleshoot the phone's connection to the subscription server. If the request succeeds but no nodes are parsed, ask the provider for the Android-specific output URL. Then try importing a compatible single-node link to distinguish a subscription parsing issue from a node-field issue.

Why can't one app connect when Android says it's connected?

Test another app with the same node, then open the client's per-app settings and check whether the affected app is included in the allowed list or excluded. If multiple apps fail, check the connection log for handshake or connection errors. The system VPN icon alone doesn't prove that the remote server is reachable.

Can I restore a v2flyNG backup directly in v2rayNG?

Don't assume the two clients use compatible backup formats. Keep your old configuration, then add the subscription or import the nodes you need in the new client. Reconfigure per-app rules separately. Before testing, stop the old client's VPN session so the system doesn't keep routing traffic through the previous app.

My subscription only has VMess. Do I still need to switch to Xray?

Not just because of the protocol name. If your current v2fly configuration updates and connects successfully, you can keep using it. If you need to migrate, first check the transport and TLS parameters against the original configuration, then test a known-good node. Don't change the core, node, and routing rules all at once, or it will be hard to pinpoint the cause of a problem.