Shadowrocket Troubleshooting

Yes. Open the same Shadowrocket product page in the iPad App Store and check its compatibility section. System requirements are as listed on the App Store page. If you already purchased the app, check your purchased items using the original purchasing account. The iPad layout varies with screen size and orientation, but subscriptions, server details, and Config files still need to be checked separately. Buying the app with the same account does not mean its configuration will sync in full automatically.

To connect, Shadowrocket needs system permission to add a VPN configuration. The system may ask for your device passcode or other authentication. First, confirm that the request was initiated by the Shadowrocket app you just installed, then follow the system prompts. This permission allows the app to establish the network connection; it does not validate your server details. After granting permission, return to Home, check the selected entry and Global Routing, turn on the connection, and test access.

Make sure you have a usable server entry selected, then check that you completed the VPN configuration authorization. In system Settings, review VPN management for configuration conflicts. Temporarily stop any other active VPN connections and try again. If Shadowrocket still disconnects immediately, check the in-app error message and note the time and current network. Avoid repeatedly deleting configurations; keep your existing settings so you can distinguish authorization, configuration, and server issues.

This manual keeps interface labels in English. Use Home, Config, Settings, and Global Routing to find the matching controls; you do not need to change the language before following the steps. To change the display language, check in system Settings whether Shadowrocket offers a preferred language option. Available options depend on your device and app. Protocol names and rule keywords remain in English; do not enter translated descriptions in server type or rule fields.

App updates are delivered through the App Store. Before updating, save your existing subscription sources, manually entered server details, and the Config file in use. Store any passwords or tokens securely. After the update, check your entries, Global Routing, and connection switch, then test commonly used destinations. Refer to the App Store release notes for app changes. Reinstalling should not be your first troubleshooting step, as it may remove local settings that have not been backed up.

Config applies the connection policy defined by the active Config, and is appropriate when you have checked its rules and fallback policy. Proxy tests the selected server using proxy routing. Direct checks the underlying network without proxy routing. Changing the routing mode will not fix incorrect server details. During troubleshooting, note the original mode, change only one setting at a time, and restore it after testing so you do not mistake a mode change for a fix to your rules or server.

Turn off the connection and confirm that the underlying network can access the internet. Reconnect, then check the selected server and Global Routing. Review the connection log to see whether requests use DIRECT, PROXY, or REJECT, and check whether the problem affects only one domain. Connectivity Test can help check an entry, but a successful test does not guarantee that every webpage will load. Finally, use the error details to check authentication, DNS, and rules, changing only one thing at a time.

First distinguish a DNS resolution failure from a connection failure. Check the relevant request log and error message, then review DNS settings and related overrides in the active Config. If you recently changed DNS behavior, note the original values and test by restoring settings one at a time. Do not change the server and DNS settings simultaneously. Resolution may vary between networks, so test on the network you are currently using. Access to an IP address alone does not prove that a TLS connection to its domain will work.

Confirm that Global Routing is set to Config and that the edited Config is the one currently active. In the connection log, check the actual request domain, matched rule, and final policy. Then review the Config in order to see whether an earlier rule matched first. DOMAIN-SUFFIX matches domain suffixes, IP-CIDR matches address ranges, and FINAL is the fallback when no earlier rule matches. Before changing a REJECT rule, verify its scope so you do not also block necessary requests to the same domain.

Check system battery usage over the same period, then look for heavy background transfers, frequent reconnects, or continuous testing. On Demand triggers connections based on conditions; check whether those conditions are causing repeated connections rather than treating it as a battery-saving switch. Battery use depends on several factors, including network signal, traffic, protocol, and server response, so the protocol name alone is not enough to identify the cause. Keep usage conditions similar, change one setting at a time, and compare results.