Shadowrocket Glossary
glossaryLook up terms by where they appear, from interface labels and protocol types to rule keywords. English terms retain the wording used in the app; explanations cover their purpose, scope, and common points of confusion. Exact locations and available options vary by platform and are shown in the app.
Interface & Toggles
interface · 06First, identify which level of settings you are changing. Switching the global mode, selecting a profile, and turning on the connection are three separate actions.
- Home
- The main control screen for viewing added server entries, choosing a connection target, and checking the connection toggle. Selecting an entry only sets the connection target; it does not establish a connection. Even a successful connection does not mean every request uses a proxy—the actual route also depends on Global Routing and the profile rules.
- Global Routing
- Global routing settings with three modes: Config, Proxy, and Direct. The selected mode determines how connections are handled overall, while the corresponding settings determine their specific routes. If you edit rules without switching to Config, the results may not match the rule text. Check this setting first when reviewing rule behavior.
- Config
- In Global Routing, Config is a mode that matches connections against the currently enabled profile. As a page name, Config refers to the place where profiles are managed, selected, and edited. Use the context to tell them apart: the mode determines whether rules are used, while the page manages the file containing those rules.
- Proxy / Direct
- In Global Routing, Proxy means proxy mode and Direct means direct-connection mode. These are overall routing choices, not individual domain conditions. Proxy cannot fix incorrect server settings, and Direct does not remove an existing subscription. The capitalized interface labels are different from the all-caps PROXY and DIRECT policy names in rules.
- On Demand
- On Demand connects when specified conditions are met, reducing the need for repeated manual actions. It determines when to establish a connection, not which rule a domain follows; routing mode and profile rules determine that. When troubleshooting automatic reconnection or behavior after a network change, check both On Demand conditions and system VPN settings.
- Add Server
- The entry point for manually adding server details when you already have a server address and authentication settings. Select the correct protocol type, then enter the address, port, and required fields as specified by your service information. Saving only adds the entry locally; select it and test the connection separately.
Protocols
protocols · 07The protocol type must match the server you already have. Changing a label in the client cannot make a server support a different protocol, and protocol names alone do not determine speed or battery usage.
- Shadowsocks
- A proxy protocol that uses a pre-shared password and a specified encryption method. Key settings usually include the server address, port, password, and encryption method. The encryption method must match the server; similar names are not interchangeable. Check any additional transport settings in your service information rather than copying only the address and password.
- VMess
- A proxy protocol with user authentication and protocol-level encryption. UUID is a commonly used identity field. Check transport, path, Host, and TLS settings separately; entering a UUID does not configure them automatically. Some authentication mechanisms are sensitive to device time, so check that the system clock is accurate if connections fail.
- VLESS
- A proxy protocol with streamlined authentication and forwarding, commonly using UUID to identify users. Data confidentiality is generally provided by an outer secure transport. VLESS and VMess use different fields and mechanisms; do not reuse the same settings simply by changing the protocol type. Preserve all transport and security settings specified by your service information.
- Trojan
- A proxy protocol typically used with TLS and password authentication. Enter the address, port, password, and server name as a matching set. The server address and TLS verification name may differ; use your existing configuration to determine their roles. If certificate verification fails, check the name, device time, and server certificate rather than disabling verification.
- HTTP / SOCKS5
- Two distinct proxy protocols: HTTP proxies commonly use CONNECT to establish a tunnel, while SOCKS5 defines negotiation for connection-oriented and datagram forwarding. Username, password, DNS resolution, and UDP support depend on the client and server implementation. The protocol name alone does not guarantee encryption; check whether a separate secure transport is used.
- WireGuard
- A network tunneling protocol based on UDP and public-key authentication. Settings commonly include tunnel addresses, the peer public key, endpoint, and routing scope. Unlike a proxy entry that only requires a host and password, the address and allowed routes also affect reachability. Private keys are sensitive; remove them before sharing or troubleshooting a configuration.
- Hysteria2
- A QUIC-based proxy protocol that relies on the network allowing the required UDP traffic and on correctly configured authentication and TLS settings. Performance depends on packet loss, congestion, server capabilities, and bandwidth settings; it is not inherently faster. If other protocol types work but this one fails, check UDP connectivity separately.
For help understanding settings and choosing a protocol, read the Protocol Reference.
Rule Keywords
rule-set · 08Rules generally consist of a match type, match value, and action. They are checked from top to bottom, and matching stops at the first rule that applies, so order matters.
- Rule
- Rules identify connections by characteristics such as domain names or IP ranges, then specify an action. Put more specific rules first and broader rules later, so broad matches do not take precedence. Rules determine routing; they cannot correct server authentication details or restore an unavailable server.
- DOMAIN
- Matches the exact specified domain. For example, a rule for example.com does not automatically match api.example.com. Use it when you want to change handling for a single host. To cover a group of subdomains, consider DOMAIN-SUFFIX instead of adding multiple similar exact-match rules.
- DOMAIN-SUFFIX
- Matches a specified domain and its subdomains. For example, one suffix rule can cover both example.com and api.example.com. Matching follows domain boundaries, not arbitrary string inclusion. If a site's main domain works but some resources fail, check whether those resources use different domains.
- DOMAIN-KEYWORD
- Matches domains containing a specified string, generally covering more than exact-domain or suffix rules. Short or common strings may also match unrelated domains, so assess the scope before using them. When you know the full service domain, prefer a more specific condition to make future troubleshooting easier.
- IP-CIDR / IP-CIDR6
- Match destination addresses by IPv4 or IPv6 network range, respectively. The number after the slash indicates the network prefix length. These rules match address ranges, not domain-name spelling; domain connections may be evaluated against their resolved IP addresses. An IPv4-only rule does not also match the corresponding IPv6 connection.
- GEOIP
- Matches destination addresses based on the region assigned in an IP geolocation database. For example, GEOIP,CN,DIRECT sends addresses assigned to that region to DIRECT. Database assignments are not real-time measurements of a server's physical location and say nothing about the language or region a service targets. If results differ from expectations, check the actual destination IP.
- FINAL
- A fallback rule for connections that match no earlier conditions, usually placed at the end of the list. FINAL,PROXY sends remaining connections to PROXY; it does not disable earlier DIRECT rules. If FINAL appears too early, later specific rules usually will not be checked.
- PROXY / DIRECT / REJECT
- Three common rule actions: send traffic through a proxy, connect directly, or reject the connection. These are actions, not match conditions or server protocols. To see which connection target PROXY uses, check the current selection. REJECT may affect pages that depend on the blocked request, so confirm the match scope before adding it.
Subscriptions & Profiles
profiles · 06The following explanations assume you already have your own subscription or server details. A server entry specifies where to connect; a profile specifies how to handle connections; purchase history belongs to getting the app.
- Subscribe
- A subscription type for retrieving and updating a set of server entries. Your subscription URL comes from your own service provider. An update usually fetches the remote content again; it does not renew an account or guarantee that usable entries will be returned. Subscription URLs may contain access credentials, so do not include them in public screenshots, posts, or shared diagnostic records.
- SERVER
- The server host field, usually a domain name or IP address. A server entry may also be called a node. The port typically has its own field; do not enter a full webpage URL or subscription URL as the host. Check each field against your existing service information, and watch for spaces or line breaks when pasting.
- Profile
- A file that stores rules, DNS, and related handling settings. It has a different purpose from a subscription that provides a list of servers. After importing a file, check which profile is enabled and whether Global Routing is set to Config. Replacing a profile can change the route for many requests; keep the original file so you can compare or restore it.
- Scan QR Code
- An entry point for importing content from a QR code, which may contain a single server entry or a subscription URL. Scanning reads the content but does not verify its source or fields; check the protocol, address, and authentication settings afterward. QR codes may contain access credentials, so treat them as sensitive when saving or forwarding.
- iCloud Sync
- A feature that syncs supported data through iCloud; the items synced depend on the app's current settings. This is separate from App Store purchase history, system VPN authorization, and connection status. After moving to a new device, check the selected profile and connection target, and grant any required system permissions even if your data has synced.
- Purchased
- The App Store section for viewing purchases associated with an Apple ID and redownloading apps. When switching devices, make sure you use the original purchasing account. The iPhone / iPad app is a one-time $2.99 purchase from the App Store; Mac / Windows / Android / Linux versions are free. Purchase history confirms the app purchase and does not include service-provider access.
For import steps, read the User Guide. For purchase history issues, see Restore Purchases on a New Device.
Networking & Diagnostics
diagnostics · 06Separating DNS resolution, data transport, security handshakes, and app requests can help narrow down a problem. A test result only describes the conditions under which that test was run.
- DNS
- DNS resolves domain names to IP addresses and is often needed before a connection can be established. Successful resolution does not mean the destination port is reachable, and a failed connection is not necessarily caused by DNS; check routing, handshakes, and service status too. DNS changes may be affected by caching, so keep other conditions as consistent as possible when comparing results.
- Connectivity Test
- A connectivity test checks whether a server or specified target is reachable under current network conditions. Passing does not mean all websites, protocols, or sustained transfers will work; a failure may apply only to the test target. Record the test method and compare it with requests from the app where the problem occurs.
- Latency / Throughput
- Latency measures how long a response takes; throughput measures how much data can be transferred per unit of time. They are not interchangeable. Low latency often helps interactive tasks but does not guarantee faster large-file transfers; sustained speeds also depend on bandwidth, packet loss, and congestion. Compare results using the same local network, target, and test method.
- TLS / SNI
- TLS is a security protocol for authentication and protecting data in transit. SNI is an extension that specifies the target server name during the handshake. SNI, the server connection address, and the name on the certificate are related but do not always use the same value. For handshake errors, check the name against your service information, certificate validity, and device time instead of repeatedly changing the port.
- TCP / UDP
- TCP provides a reliable, ordered byte stream; UDP sends datagrams without guaranteeing delivery or order. Applications can implement reliable transport over UDP, so UDP is not inherently unreliable. A successful TCP test on a network does not prove that protocols relying on UDP will work there.
- URL Rewrite
- A mechanism that rewrites request URLs or applies redirects when conditions match. It operates separately from routing rules that determine the connection path. Whether it works depends on the rule type, whether the request can be processed, and related settings; do not assume all encrypted requests can be rewritten directly. To troubleshoot unexpected redirects, temporarily disable the relevant rewrite rules for comparison, then narrow down the cause.
Next steps after the glossary
nextTo add your existing service details to the app, start with the User Guide. To check protocol fields, read the Protocol Reference. For a specific error message, see FAQs.
Back to glossary categories ↑