Shadowrocket Supported Protocols: Shadowsocks, VMess, VLESS, Trojan, and Hysteria2

A quick guide to Shadowrocket protocols, including the fields to enter in Add Server for each type.

In this guide

If you already have server parameters or an import link, use the table below to confirm the Type, then check the authentication, transport, and TLS settings. Common mix-ups include treating a port number as a protocol identifier, using a UUID as a generic password, and entering the same value for the connection address and the TLS server name. The steps below follow the iPhone and iPad interface for saving and testing an entry.

Protocol and Add Server field reference

The Type must match the protocol actually running on the server; similar names are not interchangeable. Different services can use the same port: seeing 443 does not tell you whether it is Trojan, VLESS with TLS, or Hysteria2 over UDP. The table lists details to verify against the server configuration, not universal field labels across platforms. Additional fields vary depending on the selected Type, transport, and security settings.

Common protocols in Add Server and what to check
TypeProtocol overviewDetails to verify
ShadowsocksA proxy protocol that uses a specified encryption method and shared credentials.Server address, port, encryption method, and password or key. The encryption method must match the server configuration; do not substitute an option with a similar name.
VMessIdentifies users with a UUID and can use different transports.Address, port, UUID, transport, and security settings. If the original configuration specifies an Alter ID, verify it against that value rather than copying one from an outdated guide.
VLESSAlso uses a UUID, but the protocol itself does not provide payload encryption.Address, port, UUID, transport, and security settings. Enter a Flow only if the server specifies one. Do not reuse a VMess Alter ID.
TrojanTypically uses password authentication over TLS.Address, port, password, and the applicable TLS server name. If the server address is an IP, the certificate may still be issued to a domain name.
HTTP / SOCKS5HTTP proxies can establish a tunnel with CONNECT; SOCKS5 UDP forwarding requires support at both ends.Select HTTP or SOCKS5 to match the service, then enter the address and port. Add a username and password only if required. Visiting an HTTPS site does not mean the connection between the client and an HTTP proxy uses TLS.
WireGuardA UDP-based Layer 3 tunnel that identifies peers with keys.Local private key and tunnel address, peer public key, Endpoint (address and port), and AllowedIPs. Add a preshared key only if the configuration provides one.
Hysteria2Based on QUIC and relies on a UDP path between the client and server.Address, port, authentication credentials, and TLS server name. If the service uses obfuscation, enter the corresponding parameters from the original configuration. Do not use an old Hysteria entry in place of Hysteria2.

How to fill in Add Server manually

Before you start, keep a copy of the original parameters. If you have an import link, you can inspect the imported entry first and compare it against the same parameters. Avoid editing an existing entry while filling in a new one; otherwise, it can be hard to tell which field caused a problem.

  1. Confirm the protocol first

    In Home, tap the “+” in the upper-right corner to open Add Server, then select the protocol specified by the server under Type. If you only have an address and port, first confirm the protocol and authentication method. Do not choose a different Type just to save the entry.

  2. Enter the address and port separately

    For example, if the parameter is example.com:443, enter example.com as the address and 443 as the port. Do not paste the full link into the address field or append the WebSocket Path to the server address.

  3. Check the authentication fields

    Enter the UUID, password, or key required by the selected Type. Check capitalization and remove any spaces copied along with the value. The local private key and peer public key in WireGuard serve different purposes and cannot be swapped. Do not post private keys, passwords, or full import links publicly when troubleshooting.

  4. Match the transport settings

    If the original configuration specifies WebSocket, check the Path and Host. For example, keep the leading slash in a Path such as /gateway. For entries with TLS enabled, check the SNI as well. The WebSocket Host, SNI, and connection address may be the same or different; follow the original configuration.

  5. Save and test

    After saving, return to Home and make sure the new entry is selected, then run an initial check with Connectivity Test. Next, connect and visit the same destination in a browser. A successful test reading only confirms that the probe worked; it does not replace an actual visit or prove that all traffic is following the expected policy.

Separate protocol connectivity from rule-based routing

The Type in a server entry determines how the client communicates with the server. Home → Global Routing determines how traffic is routed. If a website will not load, Add Server may not be the problem. Keep the network and destination the same during testing, and change only one setting at a time to isolate the cause.

Config

Recommended

Routes traffic according to the current rules and policies. To check whether a destination uses the new entry, confirm that the policy it matches points to that entry; the entry selected on Home alone is not enough.

Best for: Keeping your usual routing rules in place and checking real-world behavior

Proxy

Sends connections through the proxy without applying Config rules. Briefly test the same destination to see whether the issue occurs only when rules are enabled. Note the original setting first, then switch back when finished.

Best for: Checking the effects of rules or policy groups

Direct

Connects directly without using the selected server. Choose a test destination that should already be reachable directly. If it also fails under Direct, check the local network or destination site before changing authentication details.

Best for: Establishing a baseline for your local network

First identify where the problem occurs

If the same destination loads under Proxy but fails after switching back to Config, first check the hostname actually used, the first matching rule, and the selected policy group. Do not switch protocols yet. If it fails in both modes, check the entry's address, port, transport, and authentication.

Common field and connection issues

VMess and VLESS both use a UUID. Can I switch the Type directly?

No. Confirm the protocol in the server details first, then check the UUID and transport. A correctly formatted UUID only meets the format requirements; it does not mean another protocol will accept it. If you need to keep both configurations, create separate entries so you do not overwrite one that already works.

Trojan reports a certificate name mismatch. What should I check first?

Check the connection address and SNI in the entry, and make sure the name used for TLS matches the server certificate. If the certificate is reported as expired or not yet valid, check the device's date and time and the certificate's validity period. Do not disable certificate verification to hide a name mismatch.

Hysteria2 works on mobile data but times out on Wi-Fi. What should I check?

Leave the entry unchanged and retry the same destination on both networks. If the timeout occurs only on Wi-Fi, first make sure you have completed any network sign-in, then check UDP connectivity to the specified server port. Reachability over 443/TCP does not prove that 443/UDP is reachable.

WireGuard has a handshake, but why can't I access an internal IP address?

If the status shows a recent successful handshake, check whether the destination IP falls within the peer's AllowedIPs and whether the server has a return route to the client's tunnel address. Test an authorized internal IP before its domain name. If the IP works but the domain does not, check DNS before generating new keys.

Download Shadowrocket