Official Guide · Glossary

Shadowrocket Glossary

Look up interface terms, protocol names, and rule keywords. If you can't find a setting, start with the interface terms. To check how a request is routed, start with rule keywords and policies.

01 Interface

Interface and settings

First check when the connection starts, then how traffic is handled once it's on.

Global Routing

Choose whether traffic handled by the client follows the rules in the configuration or uses Proxy or Direct for all traffic. When troubleshooting routing, check this setting first. If Proxy or Direct is selected, changing rules alone won't show how traffic is routed in Config mode.

Config

Under Global Routing, Config routes traffic according to the rules in the active configuration file. Config is also the name of the page for managing configuration files; a file appearing in the list doesn't mean it's the configuration currently in use.

Proxy / Direct

These are the two modes under Global Routing: Proxy sends traffic handled by the client through the current proxy server, while Direct connects without that proxy server. Direct doesn't turn off the connection or remove a server from the list.

On Demand

Automatically starts a connection when the specified network conditions are met. It controls when to connect, not how requests are routed once connected. If the connection comes back soon after you disconnect manually, check whether the current network still meets the On Demand conditions.

Connectivity Test

Checks connectivity from a selected server to a test destination over the current network. The displayed latency is the time taken by this test, not download speed. A successful test doesn't mean every website is reachable through the same server.

Add Server

Manually add a connection when you have the server details. Select the protocol based on the information from your provider, then fill in the fields it requires. The same address and port don't mean different protocols can share authentication settings.

02 Protocols

Proxy protocols

A protocol describes how the client communicates with a server; it doesn't determine which requests use the proxy.

Shadowsocks

A proxy protocol that forwards traffic between the client and server over an encrypted connection. The encryption method and password must match on both ends. When copying connection details, verify the address and port rather than relying on the name shown in the list.

VMess

A proxy protocol that authenticates with a user ID; the connection also depends on the transport settings used by both ends. Check the user ID separately from transport fields. Correct authentication details don't compensate for mismatched transport parameters.

VLESS

A proxy protocol that uses a user ID to identify connections and doesn't encrypt traffic on its own. Whether a security layer such as TLS is used depends on the configuration. Seeing VLESS in the name doesn't mean a security layer is enabled.

Trojan

A proxy protocol that typically connects over TLS and authenticates with a password. TLS certificate validation and password authentication are separate steps. If you see a certificate or name mismatch, first check the server name provided by your provider rather than assuming the password is wrong.

Hysteria2

A proxy protocol based on QUIC that uses UDP at the transport layer. Even if websites load normally, the current network may block UDP traffic to the specified server port. Being able to browse the web doesn't prove this connection will work.

WireGuard

A network tunneling protocol that identifies the peer with a public key and uses UDP for transport. The peer endpoint specifies where the connection goes; AllowedIPs describes which addresses belong to that peer. Changing the endpoint and changing the address range are separate actions.

03 Rules

Rule keywords and policies

When reading a rule, identify the matching condition first, then check the policy applied when it matches.

DOMAIN

Matches an exact domain name. For example, DOMAIN,example.com,DIRECT matches example.com, but not www.example.com just because it ends the same way. To include subdomains, use DOMAIN-SUFFIX.

DOMAIN-SUFFIX

Matches a domain suffix, including the suffix itself and its subdomains. For example, DOMAIN-SUFFIX,example.com,PROXY matches example.com and www.example.com, but not the separate domain myexample.com.

DOMAIN-KEYWORD

Checks whether a domain name contains a specified keyword; it doesn't inspect the page path or content. Shorter keywords are more likely to match other domains unintentionally. For a single site, use the full domain or a specific domain suffix where possible.

IP-CIDR / IP-CIDR6

Matches destination addresses by IPv4 or IPv6 network range. The number after the slash is the network prefix length. For example, 192.168.0.0/16 covers IPv4 addresses beginning with 192.168. It isn't a port range and can't match domain suffixes.

GEOIP

Matches by the location assigned to the destination IP address in an IP database, not by the website's top-level domain. Domains served by a content delivery network may resolve to different IP addresses on different networks, so the same domain may match differently.

FINAL

Sets the policy for requests that don't match any preceding rules. For example, FINAL,DIRECT sends unmatched requests directly to their destinations. Requests matched by an earlier rule don't reach FINAL.

PROXY / DIRECT / REJECT

These are the three policies a rule can specify: PROXY routes traffic through a proxy, DIRECT connects to the destination directly, and REJECT blocks the request. Rule keywords identify matching requests; the policy determines what happens to them.

04 Configuration

Subscriptions and configuration files

Updating the server list and switching routing configurations are two separate actions.

Subscribe

Import a subscription link from your provider to load its server list and retrieve updates. A successful import only means the client read the list; you still need to select a server and test its connectivity.

Server (node)

In the connection list, a node usually means a selectable server connection entry, with its protocol, address, port, and required settings. The displayed name is just a label; entries with the same name may point to different endpoints.

Configuration file (.conf)

A text file that defines routing rules and related network settings. It can contain sections such as General, Rule, and Host. It controls how traffic is handled, unlike a subscription that provides server connection entries. After making changes, check which configuration the app is using.

URL Rewrite

Applies rewrites or redirects to requests based on URL matching conditions in a configuration. It changes request URLs or behavior; it isn't the same as using DOMAIN-SUFFIX to choose a routing policy for a domain. When troubleshooting, distinguish changes to a URL from changes to where traffic goes.

05 Network

DNS and networking

Receiving a DNS response, getting the destination address, and connecting to the destination are three separate steps to check.

DNS

A system that resolves domain names to IP addresses and other records. Getting an IP address means the DNS query succeeded, not that a connection to that address will work. Check name resolution and the subsequent connection separately.

DoH

DNS over HTTPS (DoH) sends queries to a DNS resolver over HTTPS. It protects query traffic between the client and the resolver; it doesn't replace the connection protocol used to reach a website or determine which routing rule handles a request.

IPv6

An IP addressing system that coexists with IPv4. A domain's AAAA record can return an IPv6 address. If a domain has both IPv4 and IPv6 addresses, connections over each may match different rules; IP-CIDR alone doesn't cover IPv6 ranges.