Shadowrocket FAQ

Shadowrocket is primarily used on iPhone and iPad, and it's available for both from the same App Store product page. Before installing, check compatibility and system requirements for each device; refer to the App Store page for system requirements and purchase eligibility. If you've already bought the app, check your App Store account and purchase history first. Available space and screen layouts may differ between iPad and iPhone. Find controls by their interface labels, such as Home, Config, Data, and Settings, rather than expecting them in the same position on both devices. Check VPN permissions and local configurations on each device separately.

After confirming the app is from the specified App Store product page, allow it to add a VPN configuration when prompted during your first connection, then complete any device authentication required. This permission lets the system route the relevant network traffic through the app; it doesn't validate server details or guarantee that all traffic will use Proxy. If you dismissed the prompt, try connecting again from the app and check the VPN configuration status in the relevant section of Settings. Managed devices may have additional restrictions; check with your device administrator. Don't remove other VPN configurations unless you know what they're for, as this could disrupt an existing work connection.

Home is where you view existing server entries, choose a connection, and manage it. Config is for managing configuration files and rules. Data shows traffic and connection records. Settings contains app preferences. Global Routing is where you choose how traffic is handled; Config, Proxy, and Direct there refer to different handling modes, not the names of the bottom navigation tabs. This manual keeps interface labels in English so you can match them to the app without memorizing every menu. If you can't find a control, first check which screen you're on, then look for it by function. The layout may vary by app version.

First determine whether the switch won't stay on or whether it stays on but you can't access anything. If it won't stay on, check that system VPN permission is granted, that the device has no management restrictions, and that the selected server entry and configuration are usable. Also make sure another VPN connection isn't taking over the network. Turn off the connection, reopen the app, select an existing entry with complete settings, and try again. If it still switches off immediately, note any system prompt or app error and check the configuration for unsupported fields or missing values. Don't start by repeatedly reinstalling the app; doing so may erase local configurations and troubleshooting clues.

Config handles traffic according to the rules in the current configuration, making it suitable for everyday use after you've checked the rules and policies. Proxy sends traffic handled by the app through the proxy policy; use it briefly to check whether a destination is reachable through the current connection. Direct connects traffic handled by the app directly, which can help you compare against your original network. None of these modes fixes an incorrect password, expired subscription, or unreachable server. Before troubleshooting, note the original setting, change one thing at a time, and restore your intended mode after testing. DNS, system routing, and configuration exceptions may still affect results, so the mode name alone can't tell you the actual path of every request.

Connected usually means the system VPN tunnel is established; it doesn't mean the remote server or destination website is reachable. First disconnect and confirm that your original network can access ordinary websites. Then check the current server address, port, protocol, and authentication fields, and use Connectivity Test to gather clues about reachability. Next review Global Routing, the matching policy in the current Config, and DNS settings. Determine whether all websites fail or only certain domains. If needed, compare with another working connection you already have, changing one condition at a time. A test result isn't a substitute for checking actual access; a returned latency doesn't guarantee the request will succeed.

Note the failing domain, time, network, and Global Routing mode. Then check available records in Data to see which policy handled the request. In Config mode, check the order of DOMAIN, DOMAIN-SUFFIX, IP-CIDR, and other rules, and where FINAL sends traffic when no earlier rule matches. If the domain won't resolve, check DNS settings and whether the resolver is reachable. If it resolves but the connection fails, check the route to the destination and the server. Save a copy of the configuration before making changes. Don't change DNS, rules, and server settings all at once, or you won't know which change helped. Remove personal credentials before sharing logs.

Battery use depends on traffic, signal strength, connection retries, protocol, and background activity—not simply how long the app is on. Check usage for the relevant period in the system's battery settings, then review activity in Data for continuous transfers or frequent retries. On Demand controls when a connection starts under specified conditions; it doesn't replace rules in Config. If you use it, review the network conditions available in your current settings and test the behavior when switching between Wi-Fi and cellular. For a useful battery comparison, keep usage duration, signal strength, and activity similar. There's no need to run speed tests continuously.