VMess and VLESS can both use a UUID to identify users, but they differ in request authentication and encryption. When importing a subscription, choosing a node, or troubleshooting a connection, check the protocol, transport, and outer security settings separately, then verify fields such as the UUID, path, and server name. Use existing nodes with the server-side settings they were configured for; changing the protocol name won’t fix a connection.
How VMess and VLESS handle encryption
A node label like “VMess + WS + TLS” doesn’t mean three equivalent protocol choices. VMess is the proxy protocol; it handles requests and user authentication. WS means WebSocket, which carries the proxy traffic. TLS protects the connection between the client and the TLS termination point and, when certificates are properly verified, authenticates the server. VLESS can also use WebSocket and TLS, so seeing ws or tls doesn’t tell you which proxy protocol the node uses.
| What to check | VMess | VLESS |
|---|---|---|
| User ID | UUID for request authentication | Typically uses a UUID to identify and authenticate users |
| Protocol-level encryption | Modern VMess uses AEAD to protect request headers; payload encryption depends on the selected method | Commonly, encryption=none means VLESS itself does not encrypt the payload |
| Additional identifier | Modern configurations typically use alterId=0 | No alterId field |
| Outer security | Can use TLS, depending on the server configuration | TLS is common; some core versions and setups also support REALITY |
The encryption setting in a VMess node editor may show auto or aes-128-gcm. These options describe VMess payload encryption; they don’t enable TLS. Likewise, encryption=none in a VLESS link describes only the protocol layer. If the same link also has security=tls, outer TLS is still active. Some newer Xray versions also offer optional VLESS encryption. Whether it works depends on the core versions and configuration at both ends, so don’t casually change none in an older configuration.
Having TLS between the two ends doesn’t mean TLS protects the entire route to the destination site. For example, proxying a request to an HTTP page doesn’t turn it into HTTPS. If TLS terminates at a reverse proxy, securing the connection between that proxy and the backend is a separate configuration choice.
Checking UUIDs, alterId, and ports
A UUID is commonly written as 32 hexadecimal characters separated by four hyphens. A valid format only means the value can be parsed as a UUID; it doesn’t prove the server recognizes it as an account. Even if VMess and VLESS happen to use the same UUID, you can’t connect to a server using the other protocol simply by changing the protocol name: the request formats differ.
- Modern VMess: When entering a node manually, use the user ID provided by the server. Modern AEAD configurations typically use
alterId=0; a nonzero value doesn’t improve security. The64found in older guides belongs to legacy configurations and may not work with current cores. If you have an old subscription, check with the provider rather than guessing different values. - VLESS: Make sure the ID matches the same node entry. VLESS has no
alterIdfield for carrying over an old VMess setting. If the node specifiesflow, check it as a separate field. - Remote port: Use the value in the share link or provided by the server.
443is common, but it doesn’t mean TLS is necessarily enabled. Don’t enter the client’s local proxy port here; this is the remote port.
Troubleshooting: pinpoint the failing layer
If the core log explicitly reports a certificate name mismatch, check the TLS server name and certificate first, not the UUID. If the port is reachable and TLS succeeds but the core still reports an authentication error, verify the protocol and user ID. For VMess, also make sure automatic time sync is enabled on the device.
How WebSocket, TCP, TLS, and REALITY fit together
Read each node in a subscription as three parts: proxy protocol + transport + outer security. For example, VMess + WebSocket + TLS and VLESS + WebSocket + TLS share the latter two settings, but the server still needs to handle the protocols separately. VLESS also commonly uses TCP/RAW with TLS or REALITY. Transport labels in the client may vary by core version.
What to check in two common transport setups
WebSocket + TLS
- Make sure the network type is WebSocket. If the server requires the path
/ws, don’t leave it as/; use the specified value if the path is different. - Keep the WebSocket HTTP
Hostseparate from the TLS server nameSNI. The former may be used for reverse-proxy routing; the latter is used during the TLS handshake. They’re often the same, but they’re different fields.
VLESS + TCP/RAW + REALITY
- First check that the active core supports the node’s combination. Then match the server name, public key, Short ID, and other parameters provided for the node. Don’t put these values in the WebSocket path or Host field.
- If the node explicitly specifies
xtls-rprx-vision, enter that exact value inflow. Vision is a flow-control setting, not a transport type or a switch for enabling REALITY.
Extra fields in the node editor aren’t a checklist of required settings. Check only what applies to the current transport setup; don’t copy an entire set of parameters from an older node.
Choosing a node in v2rayN or an Android client
When comparing two nodes in the same subscription, start with one the current client can fully parse and that matches the server configuration. v2rayN is a desktop client; supported combinations depend on the core assigned to the node. On Android, v2rayNG uses the Xray core, while v2flyNG uses the v2fly core. Successfully importing a link only means the client recognizes its basic structure—not that the active core supports every field in it.
Keep a node setup that you’ve verified works
RecommendedIf you have a stable VMess or VLESS node, keep it as a baseline. To try the other protocol, use a separate entry instead of changing the protocol, transport, or security settings on the working one.
Best for: everyday connections and troubleshooting after subscription updates
Try a separate VLESS node provided by the server
If your provider supplies a separate VLESS entry, first check that the core supports its transport, security, and flow settings, then compare it. If the node depends on REALITY or Vision, verify support for those specific features rather than checking only whether VLESS appears in the node list.
Best for: comparing or migrating when you have the full VLESS settings
- In v2rayN’s main list, open the node editor and check the protocol, address, remote port, and user ID first. Then check the transport type, path, and TLS or REALITY settings. Follow the same order on Android; the menu labels don’t need to match exactly.
- With the node selected, use the same device and network to visit the same HTTPS destination. Make sure the page loads fully, then check the logs for repeated disconnects. The latency shown in the node list reflects its specific test method, not sustained download speed.
- To compare protocol performance, keep the exit route, transport, and destination as consistent as possible, and run several tests for each node. If one uses a WebSocket reverse proxy and the other connects directly to a different server, you’re comparing two complete routes and configurations—not just VMess versus VLESS.
Common VMess and VLESS configuration questions
Can I change vmess:// to vless:// at the start of a link and use it as-is?
No. Typical VMess share links encode a set of fields in the link body, while typical VLESS links represent the ID, address, port, and parameters separately. Even if you rebuild the link manually, that won’t make the server switch protocols. To try VLESS, import a VLESS entry provided by the server.
If VLESS shows encryption=none, does that mean TLS is off?
They’re separate settings. Open the node editor and check whether outer security is set to TLS or REALITY. If a TLS node reports a certificate error, first verify the server name provided and check the system clock. Don’t bypass the problem by turning off certificate verification.
Why does the same VMess node work on one computer but fail on another device?
On the other device, enable automatic date and time, then reconnect; VMess request authentication is sensitive to clock skew. If it still fails, compare the node address, transport, and TLS settings on both devices, and check whether the active core supports the node’s parameters. Redact the user ID and full subscription link before sharing logs.
Why can’t I connect after updating my subscription if the node name hasn’t changed?
The same label doesn’t mean the configuration stayed the same. Select the updated node and compare its protocol, port, transport, and outer security. Make sure the connection isn’t still using the old entry. If the log shows a WebSocket handshake 404, check whether the path and Host match the correct reverse-proxy route before changing the UUID.