This guide is for users who already have a subscription or connection details from their provider and want to compare VMess and VLESS settings in Shadowrocket. Start by distinguishing protocol authentication from transport and TLS, then check each Add Server field. You’ll learn which values can stay at their defaults, which must match exactly, and what to check first when a connection fails.
VMess vs. VLESS: More Than a Difference in Name
VMess and VLESS are two different proxy protocols in Shadowrocket. Both commonly use a UUID to identify a user, but their message formats and authentication mechanisms differ. If the server is configured for VMess, changing only the client’s Type to VLESS won’t work. Even if the address, port, and UUID are identical, that doesn’t mean the server accepts the other protocol.
VMess supports encryption at the protocol level, using an encryption method compatible with the server. VLESS doesn’t provide the same kind of encryption, so its Encryption setting is usually none. That doesn’t mean VLESS traffic is necessarily sent in plaintext over the public internet: enabling TLS at the outer layer can protect the connection. Treat protocol Encryption and outer-layer TLS as separate settings.
| What to Check | VMess | VLESS |
|---|---|---|
| User ID | Usually a UUID | Usually a UUID |
| Protocol-level encryption | Supported; choose the option required by the server | No equivalent encryption; usually none |
| Outer-layer TLS | Can be enabled to match the server configuration | Can be enabled to match the server configuration; don’t infer it from the protocol name |
| Transport | Must match the server, such as TCP or WebSocket | Must also match; don’t reuse settings from another connection |
| Can you switch the Type? | No. The server must provide an endpoint for that protocol. | |
Protocol names aren’t speed ratings. Server load, the network path, congestion, and transport encapsulation all affect performance. The priority is to match the client settings to the server—not to pick the option that sounds newer.
Add Server: Check the Address, Port, and UUID First
The steps below use the interface labels Home, Config, and Settings. Open Home, tap the add button to open Add Server, choose the Type, then enter the address, port, and user ID. Field positions may differ between platforms or layouts. Match each value to its field by meaning, not by its position in a list.
- Type: Check whether the original details specify VMess or VLESS. Verify this field after importing, too; don’t guess the protocol from its display name.
- Address: Enter the server address. If the field expects a hostname, enter only the hostname, such as
edge.example.com. Don’t includehttps://or the WebSocket Path. - Port: Copy the number provided by the server.
443is commonly used with TLS, but the port number alone doesn’t enable TLS; other ports can also use TLS. - UUID: Copy the full value provided by your provider and check for leading or trailing spaces and missing characters. A UUID is an authentication credential, not a custom note, and can’t be replaced with the connection name.
- Protocol-specific fields: If VMess shows AlterId, use the value in the original details. Modern configurations commonly use
0, but don’t override a value that was explicitly provided. If VLESS includes Flow, it must also match the server and the selected transport combination.
The UUID length here is a check for the common standard text format, not a prompt to generate a new value. The sample value 00000000-0000-4000-8000-000000000000 illustrates the format only; it won’t work for a real connection. Redact authentication details from screenshots and logs before sharing them.
Transport, Host, and SNI: Check Each Separately
The protocol determines how proxy messages are structured; the transport determines how they’re carried. The protocol name alone doesn’t tell you whether VMess or VLESS uses TCP or WebSocket. If the server requires WebSocket, the client also needs the matching Path. Some setups also require a specific Host.
Address is the destination for the connection. WebSocket Host is the hostname sent in the HTTP handshake. SNI in TLS indicates which TLS hostname the client expects to reach. These values may be the same or different. Don’t set all three to Address just to make the configuration look consistent.
What to Check for Each Transport
TCP settings
- Confirm the transport is set to TCP if that’s what the server specifies.
- Use the original details to determine whether TLS is enabled.
- If TLS is enabled, check the SNI and certificate verification requirements.
- Don’t reuse the Host and Path from a different WebSocket connection.
WebSocket settings
- Confirm the transport is set to WebSocket.
- Keep the full Path, for example
/example-ws. - Enter the Host from the provided details. Don’t replace it with the IP address in Address.
- If TLS is also enabled, check SNI separately.
First match the transport combination required by the server, then investigate the specific error. Don’t change Type, TLS, and Path all at once.
Path capitalization, slashes, and query strings can all affect routing. Changing /example-ws to / may connect to the same server but fail to reach the proxy service. If the log shows HTTP 404, check Path and Host first. This is a troubleshooting clue, not proof that the protocol or UUID is correct.
TLS vs. Encryption: Keep Them Separate
VLESS using none for Encryption doesn’t mean TLS must be off. Likewise, VMess using protocol-level encryption doesn’t mean you should disable TLS when the server requires it. The client and server must use the same encapsulation; otherwise, the connection may fail before authentication.
TLS On, Certificate Verification Enabled
RecommendedWhen the server explicitly provides a TLS endpoint, enable TLS and check SNI. Proper certificate verification helps confirm the server’s identity. Skipping certificate verification shouldn’t be a routine setting.
Use when: Your provider’s connection details explicitly require TLS. This recommendation assumes the server requires it.
TLS Off, Only When the Configuration Specifies It
Keep TLS off only when the original details explicitly say not to use it. Port 443 alone isn’t enough to confirm that TLS is enabled, and checking the TLS box in the client can’t enable TLS on a server that doesn’t support it.
Use when: The details explicitly specify a non-TLS endpoint, or in a controlled environment with an already protected transport path.
Bottom line: Check the Hostname and Device Time for Certificate Errors
For a TLS certificate error, first check that your device’s clock is correct, then compare SNI and the certificate hostname with the original details. If they still don’t match, ask your provider to confirm the configuration instead of hiding the problem by disabling verification.
Device clock differences can also affect VMess authentication. To troubleshoot, enable automatic date and time in system settings, then reconnect. Don’t adjust the clock and switch protocols at the same time, or you won’t know which change made a difference.
After Importing: Test the Connection, Then Check the Rules
If you already have a subscription, it’s usually best to import the details from your provider to avoid manual entry errors. Get the subscription link from your provider. The example https://example.com/sub?token=xxxx shows the format only; it isn’t a working link. Subscription updates may overwrite provider-managed fields, so note the original values before making manual changes.
- Check the selected server: Return to Home and select the server you want to test. Check the selection marker for the default server so you don’t edit one server and test another.
- Connect: Turn on the connection toggle on Home and allow the VPN configuration when prompted by the system. A VPN status indicator doesn’t mean the destination website is reachable.
- Run a test: Run Connectivity Test, then visit the service you want to use. A successful test confirms only that the test request worked; it doesn’t prove that all domains are routed as expected.
- Isolate rule effects: Check Global Routing. Direct can’t be used to test the proxy exit. To troubleshoot rules, you can temporarily switch to Proxy and test the target request, then restore the original Config.
- Review the configuration: If it works under Proxy but not under Config, check the active configuration and matching rules in Config. Don’t keep changing the UUID at random.
Under Config, check the active configuration for rules such as DOMAIN-SUFFIX, GEOIP, IP-CIDR, and FINAL, along with the policies they reference. Rules are evaluated from top to bottom, and the first match determines how a request is handled. Global Routing’s Scene follows its own configuration, so it’s not a good way to isolate a single-server issue until you understand how that scene is set up.
Common Questions: Change One Setting at a Time
Why does the same UUID work with VMess but not after switching to VLESS?
A UUID is only one part of authentication; it doesn’t make the server accept a different protocol. Restore the original Type first. To use VLESS, get the complete VLESS configuration from your provider—don’t just change the protocol in the dropdown.
VLESS shows none. Does that mean there’s no encryption?
First check whether you’re looking at Encryption or TLS. VLESS protocol-level encryption is usually set to none, while outer-layer TLS can still be enabled. Return to the edit screen and check TLS, SNI, and certificate verification separately against the original details.
The connection keeps timing out after I copy the settings. What should I check first?
First confirm that the intended server is selected, then check Address and Port, and finally verify that your local network can reach the endpoint. A timeout alone doesn’t prove that the UUID is wrong. Don’t change the transport, TLS, and protocol at the same time. You can test on another local network and note both results.
What should I do if it works after setup but fails after a subscription update?
Compare Type, TLS, Host, Path, and SNI before and after the update to see which fields were overwritten. Share the redacted differences with your provider so they can fix the subscription source. Don’t post the full subscription link or UUID publicly, and don’t rely on repeatedly changing local values to work around a faulty source.
Keep a brief troubleshooting record: protocol, transport, TLS status, test network, Connectivity Test result, and the specific error. Recording what happened is more useful for identifying the cause than saying you tried everything. This guide doesn’t provide, sell, or recommend proxy servers or subscription services. A one-time client purchase doesn’t include a network service; get connection details from your provider.