For users who have imported a proxy configuration and need to verify its settings or troubleshoot a failed connection. Start by separating the protocol, transport, and connection security, then check the existing entry under Home. VMess and VLESS are not interchangeable by simply changing Type; even with the same address and port, use the complete set of parameters provided by your service provider.
VMess vs. VLESS: Protocol Encryption and TLS Operate at Different Layers
VMess and VLESS both define how a client exchanges requests with a proxy server. Both can use a UUID to identify a user, but their authentication methods and message formats differ. VMess offers protocol-level payload encryption options, commonly aes-128-gcm and chacha20-poly1305; whether payloads are encrypted depends on the configuration. VLESS commonly uses encryption=none, meaning the VLESS protocol itself does not encrypt payloads. Connection security depends on the outer layer.
TLS can protect the connection between the client and the TLS termination point, and verify the server's identity when certificate validation is enabled. Seeing VLESS encryption=none is not a reason to disable TLS; seeing an encryption algorithm selected for VMess is not a reason to disable TLS required by the server. Port 443 alone does not prove that TLS is enabled, nor does it tell you which protocol or transport the current entry uses.
Edit a proxy entry under Home: Check the address, transport, and identity
Find the entry you want to check under Home, then open its details or editing screen. Note its current settings and compare them with the configuration from your service provider. If the entry came from a subscription, update the subscription or check the original configuration first; manual changes may be overwritten during the next update. Don't post a complete subscription URL, UUID, or proxy share link publicly.
| Field | What to check |
|---|---|
| Type | Keep the VMess or VLESS type used when importing the entry. A protocol name in the entry's label does not confirm that Type is actually set to that protocol. |
| Address / Port | Confirm the domain name or IP address used for the connection and the port specified by your service provider. Don't change the port to 443 just because TLS is enabled. |
| UUID | Copy the complete value and remove any accidental leading or trailing spaces. Different entries may use different UUIDs; a correctly formatted UUID is not necessarily accepted by the server. |
| Transport / Path / Host | First confirm that the transport is WebSocket, then check Path and Host. Use the original configuration for Path, preserving its leading slash and capitalization; Host may differ from Address. |
| TLS / SNI | Check whether TLS is enabled and whether an SNI value is specified. SNI is used during the TLS handshake; the WebSocket Host is used in the HTTP request. Even if they happen to match, they are separate fields. |
| Alter ID / Flow | For VMess Alter ID or VLESS Flow, check against the existing configuration only. They serve different purposes, so don't copy a value from one protocol to the other. |
With WebSocket over TLS enabled, the client first connects to Address and Port, performs the TLS handshake, sends a WebSocket upgrade request, then exchanges VMess or VLESS data over the established transport. This sequence determines the troubleshooting order: if TLS certificate validation fails, changing the WebSocket Path or UUID won't fix the problem at this stage.
Choosing between the protocols: Keep the existing entry or test both
Keep the Type specified by your service provider
RecommendedIf you have only one entry, leave its Type, transport, and TLS settings unchanged to start. If you've already changed something, restore the full set of fields from the original configuration rather than just changing Type back and stopping there.
Best for: First-time imports or an entry that used to work but suddenly stopped connecting
Test your existing VMess and VLESS entries separately
If your service provider supplied two separate configurations, keep both as separate entries under Home. Test them in turn using the same network, test destination, and Global Routing setting. If the server or path differs between the entries, the results only show which entry worked better at that time—not that one protocol is inherently better.
Best for: Users with two complete configurations who need to choose an entry for everyday use
Check whether the proxy is unreachable or app traffic isn't using it
If Connectivity Test under Home returns a result but the destination website won't load, first check whether Global Routing is set to Direct. If you're using Config, also check which rule matches the destination domain. A successful one-off test only confirms that the test request succeeded; it doesn't prove the website uses the same route.
Troubleshooting timeouts, certificate errors, and WebSocket failures
Error messages can vary by platform and connection stage. Note when the issue occurred, the network type, and the exact error text, then use the symptoms below to narrow it down. Change one setting at a time and record the result after retesting. If it doesn't help, restore the original value before checking the next setting.
It keeps timing out. Should I try a different UUID first?
First confirm that the expected entry is selected under Home, and check that Address and Port match the original configuration. Retry on the same network, then compare with another available network. If it times out only on one network, check that network's DNS resolution or connectivity first. A timeout can also occur during the handshake, so this message alone doesn't mean the UUID is wrong.
The TLS certificate doesn't match. Can I turn off verification?
Don't treat disabling certificate verification as a fix. Check SNI against the original configuration, especially if Address is an IP but the certificate was issued for a domain name. Also check the device's date and time. If the name mismatch or expiration warning persists with the original settings, send the exact error to your service provider for verification.
WebSocket returns 400 or 404. Does that mean I chose the wrong protocol?
These status codes mean an HTTP response was received, but they don't indicate that the upgrade succeeded. First confirm that Transport is set to WebSocket, then compare Path and Host character by character. An incorrect path or site routing can return 404; 400 can have more than one cause. If the settings match, ask your service provider whether that endpoint still accepts WebSocket upgrades.
An entry that used to work fails after a subscription update. What should I do?
Get the current subscription details from your service provider, update them, then confirm the selected entry again under Home. Don't rely on the display name alone: an entry with the same name may have a different address, port, Type, or transport settings. If only the VMess entry is affected, check whether automatic time is enabled on your device, then ask your service provider whether the settings have changed.
Shadowrocket download and setup
Get the iPhone / iPad version from the App Store for a one-time payment of $2.99. Check the App Store listing for system requirements. The Mac (Apple Silicon / Intel), Windows, Android, and Linux versions are free; download installers from this site's download page.