VMess and VLESS are protocols for individual nodes, not subscription formats. If you already have a subscription, check each node’s protocol, transport, and security layer first, then confirm your client supports it. If a connection fails, troubleshoot the import, handshake, and app routing separately.
Encryption: Separate the Protocol from the Security Layer
The protocol, transport, and security layer in a node’s details answer three different questions: how it communicates with the server, how data is carried, and how the client-to-node connection is protected. For example, in VMess + WebSocket + TLS, VMess is the protocol, WebSocket is the transport, and TLS is the outer security layer. WebSocket does not mean TLS is enabled, and TLS alone does not tell you whether the protocol is VMess or VLESS.
VLESS + TLS
RecommendedA common VLESS configuration uses encryption=none, meaning no encryption is applied at the protocol layer represented by that field. If TLS is explicitly configured as the security layer, TLS still protects the connection between the client and the node. These settings are not contradictory.
Best for: A matching VLESS + TLS node provided by the server, with a core that supports the full configuration.
VMess
VMess request authentication and payload encryption are separate mechanisms. Common payload encryption options include AES-128-GCM and ChaCha20-Poly1305, though configurations with unencrypted payloads also exist. Check the security layer separately to see whether TLS is also enabled; the protocol name alone is not enough.
Best for: An existing, reliable VMess node that you need to keep using with its current server configuration.
Bottom line: Don’t switch protocols on the client alone
If your provider gave you a VMess node, import it as VMess. Even if the address, port, and user ID fit into a VLESS form, that does not mean the server accepts VLESS on the same endpoint. Get a matching node configuration before switching protocols.
Time checks: Check your system clock first with VMess
VMess authentication relies on timestamps. After waking a computer from sleep, switching between operating systems, or using manual time settings on a phone for a long period, a large difference between the device’s clock and the server’s can cause connection timeouts or authentication errors in the core logs. The time zone controls how local time is displayed; changing it alone will not fix an incorrect system clock. alterId is not a clock-tolerance setting.
- On Windows, go to Settings → Time & language → Date & time and turn on Set time automatically. If Sync now is available, select it once.
- On Android, automatic time settings are usually under Settings → System → Date & time. If your device manufacturer has moved the menu, search for “Date & time” in Settings.
- After syncing, retry the same node without changing the port or transport at the same time. If two devices with accurate clocks both fail to connect to the same VMess node, check the user ID and ask the server administrator to review the server clock and authentication logs.
VLESS does not use VMess-style timestamp authentication, but that does not mean you can ignore the clock. With TLS, an incorrect device clock can still make a certificate appear not yet valid or expired. Correct the clock and verify the certificate’s domain name; do not disable certificate verification just to get the connection working.
Performance: Compare complete node configurations, not protocol names
With VMess configurations that encrypt the payload, the core handles encryption and decryption at the protocol layer. A common VLESS configuration with encryption=none does not have this overhead. But if both configurations use TLS, the TLS handshake and encryption still apply. Less protocol processing does not automatically mean faster page loads or higher download speeds.
- Measure first-byte latency or throughput: The first request may include DNS lookup, connection setup, and the security handshake. A sustained download better reflects link capacity, packet loss, and server-side throttling. Record these separately; a single latency test cannot predict download speed.
- Keep test conditions consistent: Test the same destinations on the same device and network, at roughly the same time. If the nodes differ in location, transport, or server load, the results can help you choose a node for current conditions, but they cannot rank the protocols.
- Keep routing consistent: Use the same system proxy or TUN settings throughout the comparison, and make sure the test app is actually routed through the node. A fast result from a direct connection says nothing about the protocol.
Client compatibility: Importing a node doesn’t mean it will connect
Test the same subscription on desktop and Android
Desktop: v2rayN
- Go to Subscription groups → Subscription group settings to add the URL, then use the Subscription groups menu to update that group. Menu labels may vary slightly between builds.
- Open the node details and check the protocol and transport. For nodes with Xray-specific settings, make sure the active core is Xray and supports those settings.
Android: v2rayNG and v2flyNG
- v2rayNG uses the Xray core and supports VMess and VLESS. For entries with
flowor REALITY, check whether your specific build supports that combination. - v2flyNG uses the v2fly core, so a standard VMess entry is a good first test. For VLESS, check parsing and runtime support in your specific build; Xray-specific combinations are not universal configurations.
A successful subscription update only verifies part of the retrieval and parsing process. To validate the configuration, both clients must start the node and complete a real request.
Subscription URLs usually start with https://; that only describes how the node list is retrieved. A single subscription can contain both VMess and VLESS nodes. For an individual share link, vmess:// or vless:// at the beginning identifies the protocol. In v2rayNG, add and update subscriptions under Subscription group settings in the sidebar. Import individual links from the clipboard option under the “+” menu at the top right of the main list. After importing, check the protocol shown in the node details; labels such as “high speed” or “dedicated line” do not identify the protocol.
When checking the settings, start with the address, port, and user ID, then check the transport and security layer. For example, the WebSocket path must match the server configuration, and the TLS server name must match the node settings. If the address is an IP, do not replace the configured domain name with that IP. When sharing troubleshooting details, describe the field types and where the error occurs; you do not need to reveal the full subscription URL, share link, or user ID.
Import and Connection Troubleshooting
The subscription updated successfully. Why do I only see VMess?
First, make sure you’re viewing the group you just updated, not an old group or filtered results. Ask your provider whether the subscription includes VLESS and whether it offers an output format supported by your client. If VLESS appears in the same subscription on another device, check whether your build is ignoring entries it does not recognize.
I imported the subscription on two devices. Why does it only work on my computer?
Test the same node on the same network, and make sure both devices selected the same entry—not just one with the same name. Compare the protocol, transport, security layer, and core logs. If the phone reports an unsupported field while starting the core, try a compatible build or node instead of repeatedly changing system proxy settings.
The node test succeeds. Why won’t my browser load pages?
A node test only reflects the route used by that test request. On desktop, check whether the browser follows the system proxy or is set to bypass it by the current routing rules. On Android, first confirm that VPN permission is granted and the VPN is running, then check whether per-app proxy settings exclude the browser. Change one setting at a time, then retest the same URL.
The port is 443. Can I just change the security layer to TLS?
A port number does not tell you which security layer to use. Port 443 is only a common convention. If the logs show a handshake or certificate error, compare the security layer and server name with the original configuration. If you copied the settings manually, reimport the original node first and compare the details.