Shadowrocket FAQ and troubleshooting steps

Have your existing subscription or server details ready. On Home, use Add Server to enter them, or follow the subscription import steps. Return to the list, tap the dot beside a server to select it as the default, then check Global Routing. When ready, turn on the connection and allow the VPN configuration when prompted by the system. For your first test, confirm that one server connects before enabling rules or On Demand. Change one setting at a time.

Make sure a working server is selected, and check whether the system is still waiting for permission to add a VPN configuration. If you previously declined, turn the connection back on and follow the prompt. Complete any verification using your device's normal authentication method. Then check VPN status in system Settings and make sure no other connection is in use. Managed devices may restrict VPN configurations; check with your device administrator. Keep your existing configuration, note the error message, and don't start by reinstalling the app.

No. System permission allows Shadowrocket to create a VPN connection; it doesn't verify server credentials, subscription status, or whether a website is reachable. After granting permission, return to Home, confirm the default server and connection switch, then run Connectivity Test and visit the page you want to check. If the system says you're connected but webpages won't load, check Global Routing, DNS, and server status. The VPN status icon alone doesn't confirm that everything is working.

Look for the labels as they appear in the app: Home manages connections and servers, Config manages rule files, Data shows usage statistics, and Settings contains common options. Global Routing selects a routing mode, and Add Server is where you enter connection details. To check whether you can change the display language, look for language options in the app settings under system Settings. Available languages depend on what your device and app display.

Check the time range in your system battery statistics, then compare it with data use, signal strength, and usage duration over the same period. Continuous data transfer, weak signals, and repeated reconnects can all increase battery use, so a single percentage reading isn't enough to identify the cause. Pause repeated batch tests and check whether the server disconnects often or On Demand keeps triggering. Adjust one setting at a time and observe under similar network and usage conditions. Save error details if you need to investigate further.

Config routes traffic according to the rules in the active configuration file, making it suitable for everyday use once you've checked the rules. Proxy sends eligible traffic through the selected proxy route and can help narrow down rule issues. Direct connects without using the selected proxy server. First confirm the server works, then choose Config to check the rules. Changing modes changes where traffic goes; it won't fix incorrect credentials. If Proxy works, that doesn't mean every rule in Config is correct.

Disconnect first. Confirm that your Wi-Fi or cellular connection works on its own and complete any required network sign-in. Reconnect, check the default server, run Connectivity Test, then check Global Routing. If Proxy works but Config doesn't, focus on the active rules and DNS. If neither works, check the server status and credentials first. Change one thing at a time and note which sites fail; don't reset all settings at once.

Check that Global Routing is set to Config and that the active configuration file is the one you edited. Rules are matched in order, so a broader rule earlier in the list may match first. FINAL handles traffic not matched by earlier rules and should be at the end. Check the domain after DOMAIN-SUFFIX and the policy name. A webpage may request multiple domains. After saving, test with a new connection and review available request logs to see which rule matched. Don't infer the result from how the webpage looks alone.

Not directly. Connectivity Test checks whether a test target is reachable; its reported time isn't the same as download bandwidth or video playback quality. Check the selected test method and target, run a few tests on the same network for comparison, and try the service you actually need. One failed test doesn't mean every site is unreachable, and a low result doesn't guarantee a stable connection. Record the test target, routing mode, and actual access results to help distinguish server issues from problems with the target site.

On Demand triggers a system connection when its configured conditions are met; it doesn't check whether server credentials are valid. Check whether On Demand is enabled and whether the current Wi-Fi, cellular network, or other conditions match. If the connection returns after you disconnect manually, a condition may have triggered it again rather than the switch malfunctioning. To troubleshoot, turn off On Demand and connect manually to test the server. Once the basic connection works, restore conditions one at a time and observe what happens when you switch networks.