Look up terms by interface, connection mode, and configuration syntax. English names match the app interface, protocols, and rule keywords. First identify the term’s context, then determine whether to change server settings, routing mode, or the configuration file.
5 topics29 termsDirect links to each term
New to Shadowrocket? Start with the user guide. If you’re already having connection issues, troubleshoot by symptom using the troubleshooting guide.
01 / Identify where to make changes
Interface & Controls
Interface terms tell you where to make changes, not which route a request ultimately takes. The same English term may appear as both a page name and an option; use its location to determine its meaning.
Home
The screen for viewing server entries, the current selection, and the connection toggle. It’s also the place to check whether imported entries appear. Before connecting, confirm the selected entry is the one you expect. An enabled toggle only means the connection process has started; it does not mean every website is accessible.
Config
As a page name, Config opens configuration file management, where you can view and select a configuration. As a Global Routing option, Config means requests are handled according to the current configuration. Opening the Config page and enabling the Config routing mode are two separate actions.
Settings
The screen for managing client behavior and related options; available settings depend on the current app version. Before troubleshooting, note the original values. Change one option at a time and repeat the same test so you can identify the cause, rather than changing several settings at once.
Add Server
The entry point for manually adding existing server details. First select the correct protocol, then enter the address, port, and authentication details. Some protocols also require transport, path, TLS, or other settings; an address and password alone may not be enough.
Connectivity Test
A test for checking connectivity. Results depend on the test method, destination, current network, and server status. The displayed latency is not sustained download speed and cannot replace testing actual access. For a useful comparison, keep the destination and network conditions the same.
02 / Check how requests are handled
Routing Modes & On Demand
Check the overall routing mode before looking at individual rules. Automatic connections, domain resolution, and server authentication each handle different parts of the process; success at one stage does not prove the whole connection works.
Global Routing
An option that determines how requests are handled overall and whether rules in the current configuration are applied as expected. If a rule doesn’t seem to work, check Global Routing and then the rule order before changing server settings.
Config / Proxy / Direct
The three basic routing modes are Config, Proxy, and Direct: Config follows the current configuration, Proxy routes primarily through a proxy, and Direct connects primarily without one. These capitalized names are interface options, distinct from the all-caps policy names used on the right side of rules.
On Demand
Starts connections on demand based on configured network conditions, reducing the need for repeated manual actions. It does not fix unavailable servers, incorrect passwords, or mismatched TLS settings. First confirm that a manual connection works, then set the trigger conditions and check behavior after network changes.
DNS
The process of resolving a domain name to an IP address, an important step when accessing services by domain name. Resolution failures, caching, or changes in the resolution path can cause some domains to fail. Note the affected domain and current DNS settings; don’t assume every access failure is a server timeout.
03 / Check existing server settings
Protocols
Protocols define how the client exchanges data with the remote endpoint. These descriptions help identify settings, not rank speed. Availability depends on the server’s implementation, both sides’ configuration, and current network conditions.
Shadowsocks
An encrypted proxy protocol. The client and server must use matching encryption methods, passwords, and related settings. If a connection fails after import, check the protocol, port, and encryption method individually. Matching display names do not mean two entries are equivalent.
VMess
A proxy protocol that authenticates using a user ID and other information. Configuration may also include transport and TLS settings. An inaccurate system clock can affect authentication, so use automatic time settings. A mismatched transport path or name can also prevent connections.
VLESS
A lightweight proxy protocol that does not encrypt data by itself. Consider its security together with outer layers such as TLS. The user ID is only one part of the configuration; check the transport, path, name, and security options against your existing server details. Don’t reuse settings from a different protocol.
Trojan
A proxy protocol typically used with TLS and password authentication. Connection details include the server address, port, password, and TLS name. The certificate name may differ from the connection address; follow the settings for your existing service. If you see a certificate error, check the name and system clock first.
Hysteria2
A QUIC-based proxy protocol that relies on a working UDP path. Performance depends on packet loss, bandwidth, and congestion control settings. Network restrictions on UDP can prevent connections even when the address and authentication details are correct. It is not guaranteed to be faster than other protocols on every network.
WireGuard
A tunnel protocol that uses public-key and private-key authentication. Configuration includes the local private key, peer public key, tunnel address, Endpoint, and routing scope. Keep private keys confidential; don’t share them in screenshots or logs. A successful handshake does not confirm that DNS and routing scope are configured correctly.
HTTP / SOCKS5
Two proxy protocols: HTTP proxies can establish tunnels with CONNECT, while SOCKS5 TCP and UDP support depends on both implementations and their configuration. Don’t confuse the proxy protocol with the HTTP or HTTPS used by a destination website. Using a proxy alone does not tell you whether traffic is encrypted.
The left side of a rule defines what to match; the right side defines what to do when it matches. These examples illustrate syntax only. The domains are examples, not recommendations for replacing your existing configuration.
[Rule]
The section of a configuration file that organizes traffic-routing rules. Rules are checked from top to bottom, and the first match determines the policy. A broad rule near the top can prevent a more specific rule below from taking effect. Checking rule order is often more effective than repeatedly adding duplicates.
DOMAIN-SUFFIX
Matches domain suffixes. For example.com, this includes the domain itself and its subdomains, such as www.example.com. Matching respects domain boundaries; it does not match any arbitrary string containing the text. To match only one exact domain, learn how DOMAIN works.
DOMAIN-KEYWORD
Matches domains that contain a specified string, usually covering a broader range than a rule for a specific domain suffix. Common short strings may match unrelated domains, so check the actual request domain before using this condition. Don’t base a rule only on the website’s display name.
GEOIP
Matches a destination IP using an IP geolocation database. Results depend on the database records and do not directly indicate where the website operator, user, or server owner is located. For services using a content delivery network, the resolved address may also vary by network and over time.
IP-CIDR / IP-CIDR6
Used to match IPv4 and IPv6 address ranges; the prefix length after the slash determines the range size. An IPv4-only range won’t cover a service’s possible IPv6 addresses. If a rule doesn’t match, check which address family the connection actually uses.
FINAL
Handles requests that have not matched any earlier rules and serves as the fallback at the end of the rule list. FINAL,PROXY sends remaining requests through the proxy path. It does not override earlier DIRECT or REJECT matches, and it does not guarantee that the proxy server is available.
PROXY / DIRECT / REJECT
The three policies applied when a rule matches: PROXY routes through a proxy, DIRECT connects without one, and REJECT denies the request. These are actions, not protocol names. If access still fails despite a correct rule, check DNS, connectivity, and authentication for the selected route.
05 / Check what was imported and what to keep
Subscriptions & Configuration Files
Server entries, remote subscriptions, and configuration files serve different purposes. After importing, check separately that the entries are present, the correct entry is selected, and the current configuration is what you expect.
Subscription
A way to retrieve and update server entries from a URL. Its contents and validity depend on the service you already use. Subscription URLs often contain access credentials, so treat them like passwords. Refreshing only fetches the remote content again; it won’t restore an expired service.
Subscribe
The action used to subscribe to a remote resource. Before proceeding, check whether the link points to a server list or a configuration file. A link being accessible does not mean its format can be recognized. If import fails, check the resource type and response content instead of repeatedly pasting the same URL.
Server
Also commonly called a node, a server entry is a set of parameters needed to connect to a remote endpoint, usually including protocol, address, port, and authentication details. Its display name is for identification and is not used for authentication. Entries with different names may point to the same address, while entries with the same name may have different settings.
Configuration file
A document that organizes rules, DNS, and other handling options. It is not a server subscription. Keep the original file before replacing it and check what settings the new file contains. Importing a configuration does not provide a connectable server or automatically select that configuration.
iCloud Sync
Syncs app-supported data across eligible devices using iCloud; check the app for the specific sync scope. Syncing is separate from service validity and is not a substitute for backing up before making changes. Before editing or deleting data on another device, check the sync status and what the change will affect.
Purchased
The App Store section for finding existing purchases. When switching devices or reinstalling, check the Apple ID used for the original purchase. The iPhone / iPad version is a one-time $2.99 purchase on the App Store; Mac (Apple Silicon and Intel), Windows, Android, and Linux versions are free. Purchase records and server service validity are managed separately.
This is the official Shadowrocket website and manual, with guidance on obtaining, configuring, and troubleshooting the client. Connection instructions assume you already have your own subscription or server details.
Get the iPhone / iPad version from the App Store for a one-time $2.99 purchase; check the App Store listing for system requirements. The Mac (Apple Silicon and Intel), Windows, Android, and Linux versions are free. Installers for other platforms are provided through this site’s /dl/ path. Choose a platform on the all-platform downloads page, then follow that page’s instructions for allowing the app to open the first time.
For iPhone / iPad, verify the developer name Shadow Launch Technology Limited, the official icon, and app ID 932747118. For instructions on a specific task, see the Settings guide. If you understand the settings but still can’t connect, follow the symptom-based steps in the troubleshooting guide.