Already have a subscription? Open a node and check its protocol, transport, security, and Flow settings first. If it explicitly requires REALITY or XTLS Vision, v2rayNG is the better choice on Android. For VMess + WebSocket + TLS, either app may work, depending on its version. This guide is also for anyone switching clients and wondering whether an existing configuration can be imported as-is.
Project History and Core Roles
V2Fly continues the community development of the V2Ray core. Xray began as a V2Ray code fork in 2020 and later became an independent project. The two share support for combinations such as VMess, WebSocket, and standard TLS, but their implementations and maintained features are not identical. Here, “V2Fly core” means the V2Ray core maintained by V2Fly—not another name for Xray.
v2rayNG and v2flyNG are Android clients built around the Xray and V2Fly cores, respectively. Both offer subscription management, node editing, and VPN connectivity. The flow above separates two issues that are often confused: during import, the client must recognize the share format and preserve the required fields; when connecting, the core must load the generated configuration and complete the handshake required by the server. Seeing a node name in the list only confirms that the import process recognized at least that entry.
VLESS, XTLS Vision, and REALITY: What’s the Difference?
VLESS is a proxy protocol. Vision is a flow-control mode selected in Xray with flow. REALITY is a connection security setting, distinct from standard TLS in the configuration. A VLESS node doesn’t necessarily use Vision or REALITY. Likewise, port 443 alone doesn’t tell you which security setting is in use.
| Name | Where to find it in the node settings | How to check compatibility |
|---|---|---|
| VLESS | Protocol type, such as vless:// | Supported by Xray. Some older V2Fly versions had related implementations, but that doesn’t mean your particular build supports every parameter required by the node. |
| XTLS Vision | Flow: xtls-rprx-vision | Check against Xray’s feature support. Other XTLS Flow values in older configurations are not interchangeable with Vision. |
| REALITY | Transport security (Security): reality | Check that the Xray configuration supports REALITY. You can’t replace it with standard tls and still use the original server configuration. |
Vision can be used with standard TLS or with REALITY. If a subscription node uses VLESS + TLS, check its Flow setting too: explicitly specifying Vision is different from leaving Flow blank. If the server requires Vision, don’t remove Flow just to make another client save the configuration. That may stop the error message, but it won’t resolve the mismatch between the client and server settings.
Check the Security setting before switching clients
If REALITY isn’t available under Security after import, or the node details no longer show the original Vision Flow setting, check the client and core versions first. Don’t start by changing the port, domain, or certificate settings through trial and error.
Check the Fields in These Two Common Setups
These cards help identify node types; they aren’t ready-to-use connection settings. On Android, tap the edit icon beside a node to check “Transport Protocol,” “Transport Security,” and “Flow.” Labels may vary slightly between versions. Use the original values from your subscription provider—don’t fill in blank fields with common defaults.
VLESS + Vision + REALITY
- Protocol
- VLESS
- Transport
- Raw TCP (labeled RAW in some versions)
- Security
reality- Flow
xtls-rprx-vision- Related parameters
- Check the server name, public key parameters, and Short ID against the original values
The server name may differ from the connection address; check each one after import.
VMess + WebSocket + TLS
- Protocol
- VMess
- Transport
- WebSocket(
ws) - Path
- For example,
/ws; use the value set on the server - Security
tls- Domain settings
- Check the WebSocket Host and TLS server name separately
Host is used for WebSocket requests, while the TLS server name is used during the handshake. Don’t use one as a substitute for the other.
A single subscription may contain both node types, so a successful connection with one node doesn’t prove that the whole group can be migrated. For WebSocket nodes, preserve the leading slash and capitalization in the path. If the VMess editor shows auto for Encryption, that’s a protocol setting; it doesn’t mean transport security is enabled with TLS.
Choosing an Android Client and Migrating Safely
- Record the original configuration first. Keep the subscription group that currently works, and note the client version, core version (if shown), and one verified node. The app version and core version are not interchangeable; don’t infer feature support from the installer’s name alone.
- Choose a client that supports the most demanding node. If your commonly used nodes require Vision or REALITY, start with v2rayNG. If you already use VMess + WebSocket + TLS and v2flyNG updates the subscription and connects successfully, you can keep using it—there’s no need to switch just because the core has a different name.
- Migrate one node as a test. Import a single share link into the target client, then open its edit screen and compare the settings. If the provider only supplies a full subscription, create and update a separate group, then check one sample node to avoid overwriting the original group. Disconnect the other client’s VPN before testing so its system connection state doesn’t affect the results.
- Verify with a real request. Check the fields, start the connection, then load a page or app that worked before. If startup fails immediately, check the logs for a configuration loading error. If the core starts but requests fail, check the handshake parameters and network. A VPN icon doesn’t prove that the remote server is reachable.
Share links usually describe a single outbound connection. Custom JSON may also include DNS, routing, inbound listeners, and local outbound tags, so you can’t safely migrate it by changing only the protocol name. For a standard node, start with the share link and let the target client generate the configuration. If you need to migrate custom JSON, verify one outbound connection first, then restore DNS and routing one item at a time, checking that requests still work after each change.
Common Import, Startup, and Handshake Issues
Both say VLESS. Why doesn’t the node work after importing it into v2flyNG?
Open the node editor instead of relying on the protocol name in the list. If the original node specifies security=reality or flow=xtls-rprx-vision and the corresponding setting is missing after import, switch to a v2rayNG version that supports those options and reimport the original share link. Don’t copy the entry after its fields have been lost.
Switched to v2rayNG, but the REALITY node still fails the handshake?
Compare the editor with the original configuration: connection address, port, server name, public key parameters, and Short ID. If the original also specifies a fingerprint and Flow, check those separately. Enable automatic date and time, note when you retry, then check the corresponding core logs. A timeout alone doesn’t prove the key is wrong; also confirm that the address and port are reachable.
Why does the new client reject a JSON field that worked in the old one?
Find the first field name or configuration section mentioned in the startup log, then determine whether it belongs to the transport, security settings, DNS, or routing. Generate a minimal configuration in the target client using the same node parameters and compare it. Then migrate to a format supported by the target core. If the unknown field is a security setting required by the server, simply deleting it won’t fix the problem.