Shadowrocket FAQ

Check eligibility for both iPhone and iPad on the same Shadowrocket App Store product page. Review the compatibility section, then confirm which purchase account is signed in on the device. Check the App Store page for device compatibility, system requirements, and whether the purchase is universal. If you bought the app on iPhone, first look for it in Purchased on your iPad. Check the active server, selected configuration, and connection status on each device separately; don't assume settings are identical after installation.

First, confirm you're using the verified genuine Shadowrocket app and have selected your own server in Home. When you connect for the first time, the system may ask permission to add a VPN configuration. Read the prompt and complete authorization and authentication as required by your device. This permission creates a system connection configuration; it does not confirm that the server settings are correct or that the network is working. If your device is managed by an organization and adding configurations is restricted, check its management policies rather than repeatedly toggling the connection.

First, make sure Home has a usable server entry and that the one you want is selected. Then check that you completed the initial VPN authorization. If the system says configuration is restricted, check the VPN and device management settings for management policies or another active VPN configuration. Disconnect and try once more, noting the exact error message. Don't delete all your data as a first step. If you need to rebuild the system connection configuration, save your server details and configuration files first.

This manual uses the app's original interface labels: Home shows servers and connection status, Config manages configuration files, Settings contains app settings, and Global Routing selects a routing mode. Navigate by these page names, then check the relevant controls instead of relying on button positions alone. To change the display language, check whether the app offers a language option in system settings; available options depend on your device. The interface language is separate from server names in a subscription.

Your App Store purchase history restores your eligibility to get the app; it does not restore all your connection data. On the old device, check your existing subscription, manually added servers, and currently enabled Config file, then save or transfer them using options available in the app. After importing on the new device, select a server in Home again, check Global Routing, and verify system authorization. Subscription URLs and configuration files may contain private information; don't post their full contents in public discussions.

Config mode routes requests according to the rules in the active configuration file. Proxy mode sends applicable traffic through the selected proxy route, while Direct uses a direct route. For rule-based routing, check the Config file first, then select Config. For troubleshooting, you can temporarily switch to Proxy or Direct and compare the same destination, but note the original setting and restore it after testing. Global Routing selects a route; it cannot fix incorrect server settings or guarantee that a remote service is available.

First, disconnect and confirm your current Wi-Fi or cellular network can load ordinary webpages. Then check the server selected in Home and its authentication details. Next, check Global Routing and compare the same destination in different modes to narrow down whether the issue is with the server route or a rule. If domain names fail, check DNS settings in Config and use any visible connection records to see whether resolution failed. Change one setting at a time and test again. An illuminated switch only means the connection is enabled; it doesn't mean every request succeeded.

First, confirm you're editing the currently enabled file in Config. After saving, check that Global Routing is set to Config. Then review the Rule section from top to bottom: a broad DOMAIN-SUFFIX or IP-CIDR rule may match first, preventing a more specific rule below it from taking effect. FINAL should be the last fallback. Also distinguish the Proxy option in the interface from the PROXY rule policy; they are different fields. Make a new test request and check the visible app records to confirm which rule matched. Don't rely on the rule text being present alone.

Check app activity for the relevant period on your system's Battery screen, then consider network changes, data transfer, and usage time. Don't infer the cause of battery drain from the VPN icon in the status bar alone. Weak signal, sustained transfers, repeated reconnects, and frequent tests or updates can all increase activity. Stop unnecessary repeated tests, check whether On Demand is triggering unexpected reconnects, and observe usage under similar conditions. Note the original settings before making changes; avoid turning off several features at once just to compare battery use.

Check On Demand and its related conditions in Settings, then see whether the corresponding on-demand connection is enabled in the system's VPN settings. The system may reconnect when the network changes or a specified condition is met, so disconnecting manually doesn't necessarily change the on-demand rules. Note the current conditions, temporarily disable the relevant on-demand settings, and see whether automatic connections continue. Once you identify the cause, restore settings as needed. On Demand controls when a connection starts; it doesn't replace request routing rules in Config.