Home
Shadowrocket’s main screen shows the server list, current selection, and connection status. Before troubleshooting, confirm that the selected server is the one you intend to use, then check the connection switch.
Terminology / Glossary
Find interface terms by category, then compare them with your existing subscription or server details. Protocol names and rule keywords remain in English so you can match them in the app.
This glossary explains field names; it does not replace the configuration details for a specific service. A one-time app purchase is not a service plan; buying the app and obtaining the information needed to connect are separate things.
01 / Interface
First, confirm which screen or control you’re using. Global Routing sets the overall handling mode; check the active configuration to see how individual requests are handled.
Shadowrocket’s main screen shows the server list, current selection, and connection status. Before troubleshooting, confirm that the selected server is the one you intend to use, then check the connection switch.
This term identifies configuration-related screens and also appears as a mode in Global Routing. When using Config mode, check the rules in the active configuration. The mode name alone does not tell you how each request will be handled.
The overall routing mode for connections. Common modes are Config, Proxy, and Direct. Before switching, consider what you need; to handle requests by domain, check which rules are active in Config.
A feature that starts a connection when specified conditions are met. This works differently from manually controlling the connection switch. If connections keep starting or stopping, check whether the On Demand conditions match your current network environment.
The entry point for manually entering details for a server you already have. Select the Type, then check Address, Port, and authentication fields against your information. Options vary by protocol, so don’t reuse fields from one protocol for another.
The entry point for viewing and changing app settings. When troubleshooting connection or resolution issues, note the current options and check settings such as DNS one at a time. Changing several settings at once can make the cause harder to identify.
02 / Protocols
Choose a Type that matches your existing server information. Similar protocol names do not mean their authentication details or transport settings are interchangeable.
A server connection protocol. You’ll typically need to check the address, port, authentication details, and relevant options. Use your existing server information when entering them manually; mismatched authentication fields can prevent a connection even when the address is correct.
A protocol that uses parameters such as a UUID to identify connections. In addition to Address and Port, check the transport method and related security options. Matching field names do not guarantee matching server settings.
A protocol that uses a UUID to identify connections. It is a different Type from VMess. After selecting it, enter the transport and TLS settings from your existing information; copying only the address and port is not enough.
A protocol commonly used with TLS. Check Address, Port, Password, and options such as SNI if required by your server information. These values must correspond; don’t infer them from the protocol name alone.
A protocol that uses keys and peer details to establish a connection. Its fields differ from connection details based on Password or UUID. Before importing, confirm that your information is for a WireGuard configuration.
A QUIC-based protocol. It requires authentication and transport parameters that match the server. In Add Server, select the Type, then check each displayed field against your information.
03 / Rules
Rules typically combine a matching condition with an action. Check the match scope first, then see what happens when a request matches.
A rule keyword that matches by domain suffix. It can apply the same action to a domain and its matching subdomains. When checking a rule, look at the domain in the actual request rather than relying on the page title.
Matches when a domain contains a specified string. Its scope differs from DOMAIN-SUFFIX, and a short string may match more domains. Be clear about what you want to match before writing a rule.
A rule keyword that matches based on geographic information associated with an IP address. Results depend on the resolved address and the data in use; distinguish this from domain-based rules when troubleshooting.
Matches requests by IPv4 address range, written in CIDR notation. It applies to address ranges, not domain text. Check whether the address involved in the request falls within the range.
Matches requests by IPv6 address range, so it applies differently from IP-CIDR. If a destination may resolve to different address types, check the corresponding rules separately; the two formats are not interchangeable.
Handles requests that did not match any earlier rules. It is usually placed at the end of the rule list. When reviewing a configuration, check the specific conditions first, then the default action set by FINAL.
These are common rule actions: PROXY sends traffic through the selected server, DIRECT connects directly, and REJECT denies the request. They describe what happens when a rule matches, not a protocol Type. A configuration can use different actions for different match conditions.
04 / Configuration
These terms distinguish the import method, the information being imported, and settings stored in the app. Before proceeding, identify whether you have a link, individual server details, or a QR code.
An interface term for adding or managing a subscription link you already have. After adding it, check that the returned list is as expected. Whether the link opens and whether its contents are parsed correctly are separate things to verify.
A configuration URL provided by a service you already use, which can retrieve a server list or related configuration. Copy the entire URL, including any trailing parameters. Update results depend on the content returned by that URL.
A set of details needed to connect, typically including the protocol Type, Address, Port, and authentication parameters. Some protocols also require transport or TLS fields. A list label is just for identification and does not replace checking the actual parameters.
Configuration content that stores rules and related settings. The server list and rule configuration serve different purposes. Before changing how traffic is routed, confirm which configuration is active and whether it contains the rule you want to change.
The entry point for scanning a QR code to import connection details. After scanning, check that the Type and key fields match the information you already have. The QR code’s content format determines what can be imported.
See detailed steps for Subscribe, Add Server, and organizing configurations →
05 / Diagnostics
Test results reflect conditions at the time of testing. When checking connection status, DNS settings, and traffic data, record each observation separately.
The process of resolving a domain name to an address; DNS is also an interface term in related settings. Resolution results can affect subsequent connections and some rule matches. After changing DNS, check how the target domain behaves.
An in-app tool for checking a connection. One test does not reflect how every website or request will perform. If results differ, check the current server, rules, and network conditions one at a time.
The time between sending a test request and receiving a response. Results vary with the test target and current network conditions; compare results using the same test method.
An interface term you may see when viewing traffic-related data in the app. Interpret the reading according to the statistics currently shown in the app; it cannot, by itself, explain why a rule matched.
A rule feature that rewrites request URLs according to configuration conditions. When troubleshooting request behavior, first check whether the relevant rule is enabled and whether its match conditions cover the request. Keep a copy of the original configuration for comparison before making changes.
A concept related to managing data through sync features associated with your Apple Account. Check the app for the specific items that can sync. After switching devices, verify which configurations and server lists actually appear.
The App Store entry point for viewing apps associated with your current Apple ID. If you’re looking for Shadowrocket after switching devices, start by checking your purchase history here. Check the App Store page for device compatibility and system requirements.
First, verify Shadowrocket in the App Store, then follow the quick-start guide to import information you already have.