Shadowrocket Glossary
Look up a term by where it appears in the interface, then distinguish protocols, matching conditions, and actions. English names are kept as shown in the app. Use the link beside any heading to jump directly to its entry.
Interface and Toggles
Start with where the term appears. A Global Routing mode, the Config page, and a policy in a configuration profile are settings at different levels.
- Home
- The main screen displays the server list, current selection, and connection toggle. An entry in the list means its details have been added, not that a connection succeeded. When setting up for the first time, check the selected server, Global Routing mode, and connection status in that order. Importing successfully does not confirm that access works.
- Global Routing
- Global Routing determines the overall way traffic is handled. Its three modes are Config, Proxy, and Direct. Select Config to apply routing rules from the configuration profile. When troubleshooting, note the current mode first; otherwise, you might edit rules under Proxy and mistakenly think they were not saved.
- Config
- In Global Routing, Config means handling traffic according to the current configuration profile. As a page entry, Config opens configuration management, where you can view and select profiles. Use the context to tell which meaning applies: opening the Config page and setting the routing mode to Config are related but different actions.
- Proxy
- The proxy mode in Global Routing sends eligible traffic through the selected proxy route. It can help you check temporarily whether the route works, but it does not replace checking rule order. Here, Proxy is the overall mode; it differs in scope from the uppercase PROXY policy at the end of a rule.
- Direct
- The direct mode in Global Routing sends traffic straight to its destination. It can serve as a comparison when troubleshooting, but a successful direct connection does not confirm that the proxy server address, authentication, or transport settings are correct. After comparing, restore the mode you need and test the configuration rules.
- On Demand
- On-demand connection settings trigger connection behavior based on conditions provided by the app and system. They determine when to connect, not whether a domain should use PROXY or DIRECT. Verify the settings when network conditions change, and assess manual disconnection behavior against the active on-demand conditions.
- Connectivity Test
- A connectivity test checks whether a server responds on the current network using the selected test method. Results may show a latency value or a failure. Latency is the response time for one test, not file transfer speed, and does not guarantee access to every destination. If tests repeatedly fail, check the test scope, server settings, and system time.
Protocols
Protocols determine how the client communicates with the server. Choose a type based on the server details you already have; don't guess settings from a name, port, or latency.
- Shadowsocks
- A proxy protocol. Common settings include the server address, port, password, and encryption method. The encryption method must match the server; don't substitute a similarly named option. If the server details include a plugin or other options, check each one. An address and password alone may not be enough to complete the configuration.
- VMess
- A proxy protocol. Configuration usually involves a user ID, server address, and port. The connection may also depend on transport, path, Host, and TLS settings. Refer to your server details. After importing, check that these fields were retained, but don't replace your settings with values from public examples.
- VLESS
- A proxy protocol whose name is similar to VMess, but it is a different type and cannot be selected interchangeably. Check authentication, transport, and security settings against the server details; copying only the address and port is not enough. Check which transport options are actually available in the app.
- Trojan
- A proxy protocol that uses TLS. Along with the address, port, and password, check the hostname used for certificate validation. The connection address and certificate hostname can serve different purposes; don't change them to match just because they differ. For a certificate error, check the hostname, certificate validity, and device time first.
- Hysteria2
- A QUIC-based proxy protocol that depends on the current network's actual UDP support. A timeout can occur even when the address and authentication details are correct. Check the current network, server status, and protocol settings separately; a single timeout does not prove the password is wrong.
- WireGuard
- A key-based tunneling protocol. Configuration includes the local key, peer public key, peer address, and tunnel address, among other details. Each field has a specific purpose; a server address alone cannot provide a complete configuration. A private key is sensitive information. Hide it before sharing screenshots or troubleshooting details, and don't include it in public configuration examples.
- HTTP / SOCKS5
- Two different proxy protocols. Select the type actually provided by the server. The same port does not mean the protocols are the same; check separately whether a username or password is required and what traffic is supported. The name HTTP proxy does not by itself mean that the connection between the client and proxy server uses TLS encryption.
Rule Keywords and Policies
A rule typically consists of a match type, a value to match, and a policy. First check whether it matches, then check what happens when it does. Don't mistake a protocol name for a rule type.
Rule examples
[Rule]
DOMAIN-SUFFIX,example.com,PROXY
IP-CIDR,192.168.0.0/16,DIRECT
FINAL,PROXY
The first line matches a specified domain suffix, the second matches an IPv4 private range, and the last catches traffic not matched by the preceding rules. This illustrates syntax; it is not a complete configuration for every device.
- [Rule]
- The section of a configuration profile that contains routing rules. Square brackets mark the section name; they are not domain matching conditions. Rules are generally checked from top to bottom, and the policy on the first matching rule is applied. Place specific rules before broader rules that could override them. For rules to take effect, Global Routing must be set to Config and the corresponding profile must be selected.
- DOMAIN
- A rule type that matches an exact domain, for example
DOMAIN,example.com,PROXY. It applies to the specified domain and does not automatically include all subdomains. To cover subdomains such aswww.example.com, add exact domain rules as needed or use DOMAIN-SUFFIX.
- DOMAIN-SUFFIX
- A rule type that matches a domain suffix.
DOMAIN-SUFFIX,example.com,PROXYcan cover that domain and its subdomains. Enter a domain, not a full webpage URL, protocol prefix, or page path. Matching respects domain boundaries; it does not search for a string anywhere in the address.
- DOMAIN-KEYWORD
- Matches a keyword appearing in a domain, for example
DOMAIN-KEYWORD,example,PROXY. Shorter keywords may match more unrelated domains, so don't use them as a shortcut for precise rules. If traffic is routed unexpectedly, check the keyword's scope and whether the rule appears too early in the list.
- GEOIP
- Matches using an IP geolocation database, for example
GEOIP,CN,DIRECT. The match is based on address geolocation data, not webpage language, operator name, or domain suffix. For destinations using distributed services, the resolved address and database records may both affect the result. Check the connection log to investigate.
- IP-CIDR / IP-CIDR6
- Used to match IPv4 and IPv6 ranges, respectively. The number after the slash is the prefix length, not a port. For example,
192.168.0.0/16represents a network range, not a single server. An IPv4-only range does not cover IPv6 destinations; check which address type the connection actually uses.
- FINAL
- A fallback rule used when none of the preceding rules match, usually placed at the end of the rule list.
FINAL,PROXYsends remaining traffic through the proxy route; it does not automatically switch to a direct connection if the proxy fails. If FINAL appears too early, later rules may never be checked.
- PROXY
- The proxy policy in a rule sends matching traffic through the proxy route. It specifies how traffic is handled; it does not fill in the server address, password, or protocol settings for you. Uppercase PROXY is a rule policy; Proxy with an initial capital can refer to the overall mode in Global Routing.
- DIRECT
- The direct policy in a rule sends matching traffic straight to its destination without relaying it through that proxy server. It does not guarantee that the destination is reachable; the result still depends on the current network, DNS, and destination service. To send specific local addresses directly, identify the correct range first and place the rule appropriately.
- REJECT
- The reject policy in a rule blocks matching requests. It is not a fix for an unavailable proxy; using it incorrectly can block destinations that would otherwise work. If some content is missing in an app, check whether a REJECT rule with an overly broad match or high priority applies to the relevant domain.
Subscriptions and Configuration Profiles
The server list determines where to connect; the configuration profile determines how traffic is handled. The two can be related, but updating one does not update the other.
- Subscribe
- Terms related to importing and updating subscriptions, which read server entries from a subscription URL you already have. An update may change the number, names, or settings of entries, but it does not update the rules configuration profile. A subscription URL may contain credentials; don't share it publicly. If an update fails, check that the URL is complete and still valid.
- Server / Add Server
- Server refers to a server configuration; Add Server opens the form for adding one. A server name is just a label for identification. The protocol, address, port, and authentication settings determine how it connects. When adding one manually, use your existing server details. After saving, test the entry and verify access.
- Configuration File
- A configuration profile organizes general settings, routing rules, host mappings, and rewrite content into sections. Common section names include [General], [Rule], [Host], and [URL Rewrite]. It is separate from the server list. Keep a copy of the original before editing. After making changes, confirm that you have selected the profile you edited, not an inactive copy.
- [Host]
- The section of a configuration profile for specifying hostname mappings, which can assign resolution results to specific domains. A manual mapping may keep a domain pointed at an old address, so don't check only the DNS server when a domain is inaccessible. Don't copy another person's mappings wholesale; if you need one, note its purpose and how to remove it.
- [URL Rewrite]
- The section of a configuration profile for URL rewrite rules, which change or process matching request URLs. This differs from the routing mechanism in [Rule], which selects PROXY, DIRECT, or REJECT; the two are not interchangeable. What can be seen in encrypted requests also depends on the connection method and related settings. Don't assume any URL can be rewritten directly.
System and Installation
Distinguish DNS resolution, system authorization, and app installation. A system message confirming that a tunnel is established does not mean every server and destination has been verified.
- DNS
- The Domain Name System (DNS) resolves domain names such as
example.comto IP addresses. A resolution failure is different from a failed connection to a proxy server; troubleshoot them separately. In a configuration,dns-server = systemmeans to use system DNS. After changing DNS, consider the effects of caching and [Host] mappings.
- VPN Configuration
- System authorization for setting up a network tunnel. You may need to confirm a system prompt the first time you connect. Allowing the configuration only grants the app the relevant permission; it does not confirm that authentication with the remote server succeeded. If access still fails, check the server settings, Global Routing mode, and connection logs one by one.
- Purchased
- App Store purchase history, where you can find apps bought with the original account and redownload them subject to App Store rules. When moving to a new iPhone or iPad or reinstalling the app, first confirm that you are using the original purchasing account and check that the app is still available. If it isn't listed, check the purchase history and account region before assuming you need to buy it again.
- Allow Installation
- Confirm the system prompt shown when launching an installer for the first time, after verifying that the package came from this site's /dl/ path. On Windows, follow the prompt to select “More info → Run anyway.” On Mac, check “Open Anyway” under “Privacy & Security.” On Android, allow the browser you're using to install unknown apps. For other prompts and Linux execution permissions, see the installation approval guide. Don't disable system-wide protections as a routine step.