If you already have a working node, stick with the protocol provided by the server. Changing the protocol name in the client alone won't work. When setting up a new server or choosing a node from a subscription, check authentication, transport, and encryption first, then compare connection stability on the same device and network. This guide is for anyone choosing a node, switching clients, or troubleshooting an import.
Authentication, encryption, and transport in four proxy protocols
Keep three fields distinct: the protocol defines how each side identifies a request, the transport carries proxy traffic, and security layers such as TLS protect the connection. The same port doesn't mean the same protocol. Even with VMess, one setup might use WebSocket while another uses TCP, so their client settings aren't interchangeable.
| Protocol | Authentication credential | Encryption layer | Common transports and what to check |
|---|---|---|---|
| VMess | User ID, usually a UUID. | Modern configurations use an AEAD-authenticated header. Payload encryption depends on the configuration; TLS can be enabled as an outer layer. | TCP, WebSocket, and more. Check the system clock and transport settings. |
| VLESS | UUID in common configurations. | In a common configuration with encryption=none, the protocol itself doesn't encrypt the payload and is usually paired with TLS or REALITY. | TCP, WebSocket, and more. The encryption layer, transport, and flow must all match the server. |
| Trojan | Password. | Standard setups rely on TLS. The password authenticates the proxy connection, while certificate verification confirms the server's identity. | Usually TLS over TCP. Check that the certificate covers the domain and matches the server name set in the client. |
| Shadowsocks | Pre-shared secret; format depends on the encryption method. | Common AEAD methods provide authenticated encryption. The base protocol doesn't require TLS. | Supports TCP and UDP. Both ends must support the same method, and UDP must be enabled on both sides. |
WebSocket is a transport, not an encryption switch. REALITY isn't another name for VLESS, and seeing VLESS doesn't mean you need to fill in REALITY fields. With Shadowsocks, distinguish traditional AEAD methods from the 2022 series: even if both are labeled Shadowsocks, older cores may not understand the newer key format.
Bottom line: connect with the original settings, then change one variable at a time
After importing a subscription, make a real request with the original entry first, then duplicate it for testing. Change one setting at a time. For example, if the certificate name doesn't match, check the address and server name before changing the port or transport, or disabling certificate verification.
Protocol support in v2rayN, v2rayNG, and v2flyNG
Being able to import a share link only means the client can read the entry; it doesn't guarantee the core can run every setting in it. Check three things for compatibility: the entry type, the core actually in use, and the transports and encryption methods supported by that core version.
- v2rayN: In the desktop client, check the protocol and transport in the node editor, then use the runtime log to confirm which core and version actually started. For VLESS entries, also check that the selected core supports the specified security layer and flow control.
- v2rayNG: Uses the Xray core. After importing an entry that combines REALITY with Vision flow control, check that both the security type and
flowhave the correct values. If the log reports an unsupported field or method, check the core version first, then make sure the entry imported completely. - v2flyNG: Uses the v2fly core. For VMess entries, start by checking the transport settings. When moving from a device running Xray, don't assume an entry with an Xray-specific combination can be reused as-is. For Trojan and Shadowsocks, check the transport or encryption method used by the entry too.
Choosing for desktop use, mobile battery life, or self-hosting
These recommendations are for everyday desktop use with an existing, stable node—not a protocol performance ranking. On mobile, compare actual battery use. For self-hosting, first consider whether you can maintain client versions, credentials, and certificates.
VMess: Keep a node that's already working
RecommendedIf you already have a stable VMess node, there's no need to switch just because the protocol is older. If it stops connecting after you move to a new computer, first check automatic time settings under Windows “Settings” → “Time & language” → “Date & time,” then check the transport and TLS settings.
Best for: Everyday desktop use with an existing, working VMess node.
VLESS: Choose a client for the complete setup
If the server explicitly provides VLESS, choose a core that supports the entire configuration. A standard TLS entry is not the same as one specifying REALITY and Vision. Before setting up a new device, make sure its core supports the same combination, then move your everyday traffic over.
Best for: Server settings are clearly specified, and desktop and mobile clients can both match the required parameters.
Trojan: Factor certificate maintenance into the cost
Trojan may be a good fit if you already have a domain and a verifiable TLS certificate, and can handle renewals. At a minimum, confirm that a client connects with certificate verification enabled. Test again after renewal so certificate problems aren't mistaken for password errors.
Best for: Self-hosted servers with an existing domain and certificate maintenance process.
Shadowsocks: A useful mobile comparison
If both ends support the same AEAD method, include it in your mobile comparison. Test on the same network with the same proxy scope, comparing reconnect counts and system-reported battery use. Fewer settings don't automatically mean better battery life; frequent reconnects can outweigh any difference in connection overhead.
Best for: Comparing mobile battery life when both ends use the same encryption method.
How to compare speed and battery use fairly
If two nodes in a subscription are hosted in different data centers, your results reflect differences between the nodes as a whole—not the protocols. If you control the server, compare protocols on the same machine. If you don't, limit your conclusion to which node works better on your current device and network.
- Verify real traffic first. On the same device and network, with the same proxy scope, visit the same destination. Record whether the request actually completes; a latency test doesn't prove a website will load. If your app depends on UDP, test it separately rather than substituting a TCP request.
- Then compare connection stability. Alternate between candidates A and B for three rounds each. Record whether the first request succeeds, how long a fixed-size file takes to download, and whether the connection drops and reconnects. Count failed downloads too; don't tally successes alone.
- Test mobile standby separately. Separate screen-on use from screen-off standby. For example, run the same activity for 15 minutes in each group, then compare longer standby periods of equal length. Keep automatic updates, proxy scope, and network type consistent. Check Android battery usage and reconnects in the client log. If readings differ by only one display unit, extend the test before drawing conclusions about battery life.
Common questions about importing subscriptions and switching protocols
Can I change VMess to VLESS just by editing the address and port?
No. Ask the server administrator to confirm that the corresponding inbound is configured for VLESS and to provide a matching entry. Import it as a new node and keep the original VMess entry. Switch your default node only after the new one connects successfully.
Trojan reports a certificate name mismatch. What should I check first?
First, compare the connection address provided by the service with the TLS server name. The address may be an IP, but the name used for verification must match a name covered by the certificate. If the name is correct and the connection still fails, check the certificate's validity period, system time, and certificate chain. Keep certificate verification enabled.
Why did my Shadowsocks connection stop working after updating the entry, even though the password hasn't changed?
Open the old and new entries in the editor and compare their encryption methods. If the server switched to the 2022 series, the new key format and core requirements may be different. Reimport the complete entry and confirm that the client core supports the method. Don't manually enter the old password in the new entry.
All four nodes pass latency tests, so why won't my desktop app load websites?
First, confirm that the app is actually using the client proxy. In Windows, check the system proxy under “Settings” → “Network & Internet” → “Proxy.” If the app has its own proxy settings, check its network settings for the local proxy address and port. Make a request and check the client log for a corresponding new connection.