Nov 9, 2026 · Protocols · About 10 min read

Shadowrocket Protocols: Shadowsocks, VMess, VLESS, Trojan, HTTP/SOCKS5, WireGuard and Hysteria2

A quick guide to Shadowrocket protocols, their transports and key settings, plus how to choose the right Type when adding a server.

At a glance

Choose the Type in Shadowrocket according to the protocol specified by your provider. Renaming a server cannot turn it into a different protocol. For users who already have a provider and subscription, this guide covers transport characteristics, authentication fields, TLS checks and setup steps, and explains how to distinguish protocol connection issues from routing-rule issues. Use the parameters to check your setup instead of repeatedly changing Type and retrying.

First, distinguish Type, transport and routing policy

Type identifies the protocol used between the client and proxy server. TCP, UDP and WebSocket describe the connection or transport method, while TLS provides encryption and certificate identity verification for the relevant link. These are separate layers, not interchangeable options. For example, VLESS can use different transport settings, but selecting VLESS as the Type does not automatically supply the TLS, Server Name or WebSocket Path required by the server.

Routing rules solve a different problem: deciding which connection handles a request. PROXY, DIRECT and REJECT mean route through a proxy policy, connect directly or reject the request. Even with correct server settings, a request matching DIRECT will not go through the current proxy server.

2 layers
Confirm the protocol connects first, then check where the rules send requests
4 checks
Global Routing:Proxy / Direct / Config / Scene
443
Examples of commonly used TLS or QUIC server ports; there is no universal port

Troubleshooting order: check server settings first

Start by confirming the Type, address, port and authentication details, then check transport and TLS. Don’t infer the protocol from the port number or assume that a page failing to load means the routing rules are broken.

Transport methods and essential fields by protocol

This table is for checking settings, not ranking speed. A subscription may already include these fields; if you add a server manually, enter them one by one. English labels may vary slightly by platform and layout. Match fields to the provider’s instructions by meaning, and don’t guess missing values.

Type / Protocol Transport Common fields Check first
Shadowsocks An encrypted proxy that can carry TCP traffic; UDP forwarding also depends on the server and related settings. Address、Port、Method、Password The Method and password must match. For entries using a plugin, the plugin settings must match too.
VMess A proxy protocol that can use server-configured transports such as TCP or WebSocket. Address, Port, UUID, encryption options, transport settings Confirm that the UUID, transport type and TLS settings match the server.
VLESS A lightweight authentication protocol that does not encrypt content on its own; security depends on the accompanying security layer. Address, Port, UUID, transport settings, TLS or REALITY settings Check the security layer, Server Name and any other server-specified settings, such as Flow.
Trojan Usually runs over TLS and uses password authentication. Address、Port、Password、Server Name Check the password, certificate name and certificate validity—not just the port.
HTTP An HTTP proxy can establish a tunnel with CONNECT; confirm separately whether the proxy connection itself uses TLS. Address, Port, Username, Password, TLS settings Check whether authentication is required and whether the server is a standard HTTP proxy or a TLS proxy.
SOCKS5 Supports TCP proxying. UDP uses UDP ASSOCIATE and also requires support from the server and network. Address、Port、Username、Password Check the authentication method and UDP support. SOCKS5 does not encrypt transport by itself.
WireGuard An encrypted tunnel over UDP that does not use username-and-password authentication. Private Key, Public Key, Endpoint, tunnel address, Allowed IPs Confirm the roles of the local private key and peer public key, the tunnel address and the allowed routing range.
Hysteria2 Based on QUIC, runs over UDP and uses TLS for a secure connection. Address, Port, Password, Server Name, obfuscation settings Check UDP reachability and authentication details. If obfuscation is enabled, both sides must use matching settings.

Shadowsocks, VMess, VLESS and Trojan: key differences

For Shadowsocks, check the Method and Password first. Even with the correct password, a mismatched Method will prevent the connection from working. Don’t treat Method as a setting to tweak for speed; if it changes, the client and server must use the same value. If a subscription entry includes a plugin, copying only the address, port and password usually isn’t enough to recreate the connection.

VMess and VLESS may both use a UUID, but they are not interchangeable. A UUID identifies a user; it is not a server address or TLS certificate name. VMess encryption options and VLESS security-layer settings mean different things. Don’t copy the rest of one server’s settings and simply switch its Type.

Trojan typically uses a password with TLS. If you see a certificate error, first check the device date and time, Server Name and whether the server certificate is valid. Turning off certificate verification changes the security of the connection and isn’t a long-term fix. Ask your provider to confirm the correct name and certificate settings.

What to check for HTTP/SOCKS5, WireGuard and Hysteria2

Being able to access HTTPS websites through an HTTP proxy does not mean the connection from the client to the proxy server uses TLS. With standard HTTP CONNECT, the website’s HTTPS protects content between the client and website after the tunnel is established, but authentication and metadata protection on the proxy connection must be assessed separately. SOCKS5 is not an encryption protocol either, so confirm the connection setup and security requirements provided by your service provider.

WireGuard uses a key pair. Keep the Private Key secret; the Public Key identifies the peer, and the two must not be swapped. Endpoint is the peer’s address and port, while the tunnel address is used inside the tunnel. Don’t enter one in place of the other. If the configuration includes a Preshared Key, it must match the peer’s.

The protocol name alone doesn’t predict speed. Results depend on factors such as outbound bandwidth, server load, round-trip latency, packet loss and network restrictions. For a fair comparison, use the same device and destination at similar times. Record whether the connection establishes, how pages load and how transfers perform over time instead of comparing a single latency reading.

Add a server from Home: choosing a Type

A subscription link and an individual server configuration are different inputs. A subscription usually contains multiple servers and their protocol settings; an individual configuration describes one connection. If you already have a subscription, get the latest link from your provider and import it. Don’t paste a subscription URL into a server’s Address field or use a subscription access token as a protocol password.

  1. Check the details

    First identify whether you have a subscription link, a single-server share link or manual settings. Keep the original details and confirm the protocol, address, port and authentication method specified by your provider. Avoid missing characters when copying from a screenshot.

  2. Open the add-server screen

    To add a server manually, go to Home → tap “+” in the top-right corner → Type, then select the protocol that matches the original settings. Don’t switch to a different protocol just because its name is more familiar.

  3. Enter the connection settings

    Enter the address, port and password or UUID, then fill in TLS, Server Name, transport, Host, Path and other fields as specified. For WireGuard, use its key and tunnel fields instead of a standard password form.

  4. Import a subscription

    If you have a subscription, go to Home → “+” → Type → Subscribe, paste the link and save, then pull down on Home to refresh. Get the subscription link from your provider, and don’t show the full access token in public screenshots.

  5. Test the connection

    Return to Home, select the relevant server and connect. Run Connectivity Test first, then visit the destination you need to check. Note whether the error points to authentication, TLS or a timeout, and change only the relevant setting.

After the protocol connects, use Global Routing to check for routing issues

Home is where you select a server and control the connection; Config manages configurations, and Settings adjusts app preferences. Global Routing determines how requests are routed. The options below compare three common routing modes in Shadowrocket, not the merits of different protocols.

Config: route by configuration rules

Recommended

Requests are checked against the current configuration’s rules in order and may be proxied, connected directly or rejected. Requests that don’t match an earlier rule are handled by FINAL; this does not mean every unlisted destination will connect directly.

Best for: everyday rule-based routing after you’ve checked the configuration

Proxy: test proxy routing

Routes requests handled by the app through a proxy path. This can help determine whether routing rules are the problem, but it doesn’t mean all system traffic is necessarily routed through the app.

Best for: ruling out rule-related issues briefly while keeping the same server selected

Direct: test a direct connection

Uses a direct connection without the selected proxy server. Use it to check whether the local network and destination are reachable; it does not prove that a proxy protocol works.

Best for: distinguishing destination issues from local network or proxy issues

Scene applies routing settings for a particular situation. When troubleshooting, check which scene is actually active instead of only checking whether a server is selected. Settings → On Demand manages automatic connections triggered by conditions; it won’t fix a password, UUID or TLS setting. To observe a manual test, note the current settings and temporarily turn off automatic triggers, then restore them afterward.

[Rule]
DOMAIN-SUFFIX,example.com,PROXY
IP-CIDR,192.168.0.0/16,DIRECT,no-resolve
GEOIP,CN,DIRECT
FINAL,PROXY

This example shows that rules and protocols are independent: DOMAIN-SUFFIX matches a specified domain suffix, IP-CIDR matches an IP range, GEOIP matches based on an IP location database, and FINAL handles remaining requests. Rules are checked from top to bottom; the first match takes effect. no-resolve means not to actively resolve a domain just for that IP rule. This is a syntax example, not something to apply over an existing configuration without checking it first.

Test systematically: keep the server fixed and change only the routing mode

If the destination works in Proxy but not Config, first check the matching rule and its policy. If both fail, go back to the protocol settings, server status and current network path. Restore the original routing mode after testing.

Common questions about adding protocols and connection failures

Why won’t it connect when I switch to Trojan on the same port 443?

A port is just an entry point; it doesn’t define the protocol. Go back to the server’s edit screen in Home and compare its Type with the settings from your provider. If the original entry uses VLESS, restore VLESS along with its UUID, security layer and transport settings. Don’t guess the server configuration by switching Types.

Why does the handshake still fail when the UUID and address are correct?

Also check the Port, TLS, Server Name and, for WebSocket, the Host and Path. First check the device date and time, then see whether the error points to a certificate or authentication problem. Keep the original values and correct one mismatch at a time so you can tell what fixed it.

Hysteria2 works on cellular data but keeps timing out on Wi-Fi. What should I do?

Keep the server and settings unchanged, test each network and note the time. If it fails only on one network, first check UDP reachability, any network sign-in page and router restrictions. Tell your provider the network type, destination port and error details. Don’t switch to TCP and still treat the result as the original Hysteria2 connection.

Can I change every server to VLESS after importing a subscription?

No. Each entry’s protocol is determined by its server. Pull down on Home to refresh the subscription and check that the entries are complete. If you need a different protocol, get matching settings from your provider. A failed subscription refresh and a failed server connection are separate issues; record and troubleshoot them separately rather than changing both at once.

When contacting your provider, include the protocol, network environment, stage at which the error occurred and the error details with sensitive information removed. Don’t include a Password, full UUID, subscription token or WireGuard Private Key in public screenshots. This site does not provide, sell or recommend servers or subscriptions. Get existing subscriptions and connection settings from your provider.

Get Shadowrocket and learn how to configure it

The iPhone and iPad version is a one-time $2.99 purchase on the App Store, from Shadow Launch Technology Limited. Check the App Store listing for system requirements. The Mac (Apple silicon and Intel), Windows, Android and Linux versions are free. Choose your platform on the download page, then follow the guide to import your existing subscription and test the connection.

Download Shadowrocket