Shadowrocket FAQ

Note the full error message from the App Store and determine whether the issue is an incomplete payment, a pending download, or device compatibility. Check available storage, your network, and whether your App Store account needs payment verification or acceptance of updated terms. If the download is pending, pause it and try again on a stable network. If the purchase status is unclear, check your purchase history before confirming payment again. Check the App Store listing for system requirements. If other apps won’t download either, troubleshoot your App Store account or network first. If only Shadowrocket is affected, check the product page for availability and compatibility.

Open the Shadowrocket App Store product page on your iPad and check compatibility and system requirements; refer to the listing for current details. If you’ve already purchased the app, check your purchase history using the original account and download it through the App Store. Any universal purchase eligibility is also determined by the listing. The iPad layout may differ from the iPhone layout, but look for the same interface labels, such as Home, Config, and Settings. After installation, check your subscriptions, server settings, and active configuration separately. Restoring the app download doesn’t mean your in-app data has migrated.

This is a system authorization prompt for setting up the app’s network connection. It is not a purchase confirmation and won’t fill in server details automatically. Confirm that you installed the genuine Shadowrocket app and checked the imported details, then start a connection and follow the system prompts to grant permission and verify your device. If you previously canceled, return to the app and try again. If the prompt persists, check the VPN configuration status in system settings. Organization-managed devices may restrict new configurations; contact your device administrator if so. Authorization only permits a connection to be established. Whether it works depends on the server, configuration, and current network.

First, confirm that you’ve imported and selected a valid server. When you turn on the switch, note whether a system authorization prompt or error appears, or whether the connection briefly starts and then stops. If system authorization is incomplete, resolve the VPN configuration permission first. If another VPN configuration is active, disconnect it before testing. Don’t delete all system configurations just to troubleshoot, especially on an organization-managed device. Then check required server settings, service status, and your current network. Keep the error message, then restart the app or device if needed. Change one thing at a time so you can identify what resolves the issue.

This guide uses the interface’s original English labels. Find features by name rather than relying on their exact position in a screenshot. Home shows connection controls and the server list; Add Server adds connection details; Config contains configuration files; and Settings contains other options. Global Routing controls how traffic is routed. To check whether you can change the app’s language, open Shadowrocket’s settings in system Settings and look for a Language option; available choices depend on your device. If there isn’t one, use the English labels. Layouts may vary by device, so confirm which page you’re on before looking for a feature by name.

Config applies routing policies according to the rules in the active configuration, so use it after checking those rules. Proxy sends app-handled connections through the selected proxy route, which is useful for testing the server. Direct sends app-handled connections directly, which lets you compare how your local network performs. These options change routing; they don’t fix incorrect server settings or guarantee that a destination is reachable. For everyday routing, make sure Config is using the intended file. To troubleshoot, keep the destination the same, change only the routing option, and retry the connection. Don’t change the server and rules at the same time, or you’ll lose a useful comparison.

A connected status usually means the system connection configuration has started; it doesn’t mean the destination is reachable. Disconnect and check whether your local network can access pages that normally work. Reconnect, use Connectivity Test to check the selected server, and verify authentication, port, and service status. The test only covers its specified destination, so also try opening the page you need. If Proxy works but Config doesn’t, check the active configuration’s rules, final policy, and DNS. If neither works, compare Wi-Fi and cellular. Retry the request after each change and note what happens; don’t change several settings at once.

Check these in order: Global Routing is set to Config, the edited file is saved and enabled, and the rules are ordered as intended. Rules generally match from top to bottom, so a broad rule near the top can take precedence over a more specific rule below it. FINAL handles connections that don’t match earlier rules. Check that each rule matches the right type of target: DOMAIN-SUFFIX matches domain suffixes, while IP-CIDR matches address ranges; they aren’t interchangeable. Re-establish the target connection after making changes, as existing connections may keep their previous route. If the result is still unexpected, check the app’s connection records for the actual domain, address, and matching policy, then investigate the specific rule.

On Demand starts a connection when its configured conditions are met; it doesn’t check whether a server works and fix problems automatically. If the connection comes back after you turn it off manually, check whether On Demand is enabled and review its conditions for the current network. To troubleshoot manually, temporarily disable On Demand, keep the server and routing option fixed, and test again. Restore On Demand afterward if needed. Note the existing conditions before changing them so you can restore them, and avoid changing multiple settings at once. Automatic connection doesn’t mean traffic is routed through a proxy; the route depends on Global Routing and the active configuration. Check the actual route after confirming the switch status.

Compare under similar network conditions, usage times, and browsing activity. Video streaming, cloud syncing, or a weak cellular signal can increase battery use independently of the app. Check system battery usage and look for repeated reconnects, continuous testing, or detailed logs left on for long periods. For speed issues, check your local network first, then the selected server and service status. Verify protocol settings against the information from your source rather than changing them at random. Change only one factor at a time—network, server, or configuration—and stop any tests or detailed logging you no longer need. A single battery percentage or speed test can’t pinpoint which layer is causing a problem.