Shadowrocket FAQ

First, search for Shadowrocket by name, then open the specific App Store product page from this site's download page. If the App Store says it isn't available in your storefront, check the country or region for the Apple ID used with Media & Purchases—not just your device's language. If you need to change your region, go to Apple Account, Media & Purchases, View Account, then Country/Region in Settings. Review any requirements shown by the App Store for your balance, subscriptions, and payment method before making changes. Availability is determined by the current App Store page.

Check these three details on the product page: the name Shadowrocket, the developer Shadow Launch Technology Limited, and app ID 932747118 in the product link. The app icon should match the official icon in this site's header. A similar name in search results isn't enough to verify an app; open its product page and check each detail before purchasing. Refer to that App Store page for the current price, compatibility, and update history, rather than relying on outdated search snippets.

In most cases, you can use the Apple ID that made the original purchase to find and redownload the app from your App Store account without paying again. Check the account used for Media & Purchases, then look for Shadowrocket in your purchased apps; the list name may vary by system version. If a price still appears, check your purchase history, whether the app is hidden, and your storefront region. Restoring the app does not restore its configuration; you'll need to transfer your existing server details and Config separately.

Shadowrocket is a paid App Store app with a one-time purchase. The amount is shown in your current storefront's currency; confirm it on the purchase screen. Buying the app once is not the same as paying for a service plan: the app does not create server details or grant access to a service you already use. Before connecting, you'll need your own subscription or server details. This site does not provide, sell, or recommend servers or subscriptions; it explains how to import, use, and troubleshoot configurations you already have.

First, check the current Shadowrocket App Store page for its Family Sharing details, then review purchase sharing settings for your family group and any account region requirements. If eligible, find the app under a family member's purchases from the App Store account page; availability depends on what the store currently shows. Being able to download the app does not sync server details, subscription links, or Config with the purchase. Each device must be configured separately according to its user's access rights.

When you first start a connection, iOS may ask to allow adding a VPN configuration. This permission is needed to establish a system network connection. Confirm that the prompt was triggered by the Shadowrocket you just opened, then follow the system instructions and enter your device passcode if requested. Granting permission doesn't mean the server is available or that the network is connected. Return to Home, select your own server, and start the connection. If the device is managed by an organization, its management policies may restrict this permission.

You can get Shadowrocket on iPad from the same App Store product page. Check that page for the current iPadOS requirements. If you used the same Apple ID to make the original purchase, look in your purchased apps before paying again. The iPad layout may differ in landscape or split-screen mode, but use interface labels such as Home, Config, and Settings to find features. The purchase record and the configuration on your device are separate; check your subscription and rule files separately.

Start with the main functions: Home shows servers and connection status; Add Server adds your own server details; Config manages configuration files; and Settings contains app settings. Global Routing determines whether requests use Config, Proxy, or Direct, while On Demand relates to system-triggered connections. This guide keeps the original English labels so you can match them to the interface. If a feature appears elsewhere, check which page you're on and what is selected instead of guessing from an icon.

First, make sure you've selected a working server, then check whether the system VPN configuration permission is still pending. If permission was denied, try connecting again and follow the prompt. Next, check the VPN status in Settings to make sure another connection isn't interfering, and review any device management restrictions. If the switch still turns off immediately, note the error message and time, restart the device, and test again. Don't delete all configurations as a first step. If you need to recreate the system VPN configuration, back up your existing in-app information first.

Save your existing subscription URL, any required server details, and the Config you're using. Note important settings for Global Routing, DNS, and On Demand. Keep subscription URLs and credentials somewhere secure that you control; don't share them in public notes or screenshots when asking for help. Update the app through the App Store. Redownloading it does not guarantee that all local data will be restored. If only one feature is affected, document the issue and investigate it directly rather than using a reinstall as a substitute for troubleshooting.

First, make sure you're using your own complete subscription URL, with no spaces, line breaks, or explanatory text added when copying it. Check whether your current network can reach the URL, and whether it returns subscription data rather than a login page, expiration notice, or error page. Then verify that the format works with Shadowrocket and that the credentials are still valid. Keep the exact error message so you can tell whether retrieval or parsing failed. Subscription URLs can contain sensitive information; when asking for help, share only the error details with the URL and credentials hidden.

A failed update only means that new content wasn't retrieved and applied this time; it doesn't prove that your existing servers have stopped working. First, check whether the old entries are still listed, then test the selected server. To troubleshoot the update, check the subscription's validity, whether its URL has changed, your network, and the error message. Once retrieval works again, try the update. After a successful update, check whether the previously selected entry was removed or renamed. Avoid repeatedly deleting and re-adding the subscription, which can remove groups, selection state, or local notes.

Use your own server details as the source of truth. Select the correct protocol, then check the address, port, and authentication details one by one. The encryption method for Shadowsocks, identity parameters for VMess or VLESS, authentication for Trojan, and fields such as TLS, server name, and transport path are not interchangeable. Not every protocol uses every field; don't fill in details from guesswork if they weren't provided. After saving, check connectivity and then test an actual request. If the test fails, compare each parameter against your source details.

First, check that Shadowrocket is allowed to use the camera and that the entire QR code is clear and unobstructed. Confirm that it contains recognizable server details or a subscription URL—not a webpage link, payment instructions, or plain text. After scanning, check that the protocol and required fields are complete; a clear QR code doesn't guarantee valid content. If the contents can't be parsed, use Add Server with your original details instead. Don't share a QR code containing credentials publicly.

No. A subscription retrieves and updates a set of server details; a server entry stores specific connection parameters; and Config can contain settings such as rules, DNS, and policies. Importing a subscription doesn't mean the right Config is selected, and downloading a rule file doesn't give you a working server. After importing, check the server list, selected entry, Config selection, and Global Routing in that order. Before updating remote content, understand what may be overwritten so you don't assume local changes will be kept permanently.

Config uses the rules in the current configuration to determine how requests are handled. Proxy generally sends requests through the proxy, while Direct connects to the destination directly. For everyday rule-based routing, make sure Config is valid, then select Config. Temporarily switching to Proxy or Direct can help with comparison during troubleshooting, but neither can fix incorrect server details. Restore your original setting after testing, and check request logs to confirm how traffic was handled rather than relying on the mode name alone.

A connected status only confirms that a connection was established; it doesn't prove that a particular request will work. Disconnect first to make sure the underlying network works, then check the selected server, Global Routing, and Config. Test different destinations and determine whether all requests fail or only one domain. If all requests fail, check the server and DNS first; if only one domain is affected, check rule matching and the destination's status. Change one variable at a time and note the result. Changing the server, DNS, and rules all at once makes it difficult to identify the cause.

Connectivity Test results depend on the test method and destination. A timeout doesn't necessarily identify a specific parameter, and a successful test doesn't mean every website is reachable. Check the server address, port, authentication, TLS, and transport settings, then verify that the device's date and time are correct. Testing the same server on different networks can help distinguish a local network issue from a remote connection issue. Finally, verify with an actual request and keep the error message; don't treat a single test as a complete measure of availability.

First, make sure Global Routing is set to Config and that you're using the configuration you just edited. Rules are usually checked in order. If an earlier DOMAIN, DOMAIN-SUFFIX, IP-CIDR, or GEOIP rule already matches, changing a later FINAL rule won't change the decision for that request. Check the actual domain, address, and matched policy in the request log, then review rule order and spelling. FINAL is the fallback when no earlier rule applies. An overly broad REJECT or domain match may also cause some page content to fail.

Compare similar periods in your system's battery usage statistics, taking screen time, network signal, and background traffic into account. Don't draw conclusions from a brief battery change alone. Weak signal, frequent reconnects, heavy request traffic, or continuous diagnostic logging can all increase power use. On Demand controls when the system starts a connection; it isn't the same as rule-based routing. Check its trigger conditions when reconnecting after a manual disconnect. For comparison, temporarily turn off On Demand without changing other settings, then observe battery use and connection status.