This guide is for iPhone and iPad users who have imported their own server or subscription into Shadowrocket and can see a server on Home. For your first connection, check three things separately: whether the dot marks the intended server, whether the connection switch stays on, and whether Connectivity Test returns a result. If the test succeeds but an app still won’t connect, check Global Routing rather than assuming the server is at fault.
Select a server, authorize, and connect on Home
Before connecting in Shadowrocket, make sure your device can access the internet on its current network. Open a site you normally access directly in a browser; if the Wi-Fi network requires a sign-in page, complete that first. Once the network is ready, follow the steps below. If the server list is empty, first check that the import completed—turning on the switch won’t populate the list.
Select the default server
Go to Home, tap the server you want to use, and make sure the dot appears next to it. If several entries have the same name, check the protocol, address, and port against the server details you saved, then confirm the selected entry in the list. The dot means the server is selected; it does not mean it’s connected.
Turn on the connection switch
Turn on the connection switch at the top of Home. The first time you connect, iOS or iPadOS may ask to add a VPN configuration. Confirm the request came from the Shadowrocket you just opened, then allow it. If the system asks you to authenticate, follow its instructions. If you’ve already granted permission, not seeing a prompt this time doesn’t mean anything went wrong.
Check the connection status
Return to Home and check that the switch stays on. If it immediately turns off or the app still asks for authorization, check the VPN configuration or device management restrictions first. Repeatedly testing the server won’t confirm the connection status on your device.
Run a connectivity test
On Home, tap Connectivity Test and wait for the current results. If results appear for multiple servers, find the one marked with the dot by its name. Don’t mistake another server’s latency for the selected server’s result. After noting the result, open the app or website you want to use.
Understand the dot, connection switch, and test result
The dot tells you which server is selected on Home. The switch tells you whether a connection has been started on this device. The test result tells you whether this test completed under the current conditions. These checks are not interchangeable. If the switch stays on but the test times out, don’t assume VPN authorization failed. Conversely, a test result doesn’t prove that an app is routing traffic as expected.
- A latency in milliseconds appears: The probe received a response. This value is response time, not download speed, and it doesn’t prove that other domains are reachable. A single reading can’t establish that the connection is consistently stable.
- A timeout or error appears: The probe didn’t receive the expected response. Retest the same server first, then check the network, server address, and connection settings. One timeout isn’t enough to conclude that the server is offline.
- No result yet: Wait for the test to finish, then check the server entry and its reading. If you’ve just changed networks or servers, run the test again rather than relying on the previous result.
Test succeeds but an app won’t connect: check Global Routing
Note the current selection under Home → Global Routing. If you normally want traffic routed by rules, reproduce the issue in Config mode first. To distinguish rule-based routing from the proxy path, you can switch modes briefly, then restore the original one. Keep the network, server, and destination the same; change only Global Routing when comparing.
Config
RecommendedRequests are matched against the rules in the current configuration. Requests matching DIRECT connect directly; requests matching a proxy policy use the path assigned to that policy. For requests that don’t match an earlier rule, check the policy specified by FINAL in the configuration—don’t assume it means direct connection.
Use when: You’ve selected a configuration and want to verify that everyday routing works as expected.
Proxy
Traffic handled by Shadowrocket uses the proxy path instead of following Config rules to determine whether it connects directly or through a proxy. If a destination opens in Proxy mode but fails in Config, first check which policy matches its domain.
Use when: You need to briefly rule out the effect of routing rules.
Direct
Traffic handled by Shadowrocket connects directly. If a destination is reachable in Direct mode, that only shows it can be reached directly on the current network; it doesn’t confirm that the selected server works.
Use when: You want to check direct access to the same destination.
Scene
Routing behavior is chosen according to the configured scene conditions. When switching between Wi-Fi and cellular data, the matched scene may also change along with the underlying network.
Use when: You’ve configured scenes and want to check routing behavior after switching networks.
If the issue occurs only in Config, open the Config page and check the active configuration and its [Rule] section. Check rules such as DOMAIN-SUFFIX against the domain used by the actual request, then review FINAL. If a browser can open a site’s homepage but an app still fails, they may be requesting different domains. Don’t change the entire configuration based only on the homepage test.
Connectivity Test times out: check Wi-Fi and cellular data separately
Keep the server selected on Home and the test conditions unchanged, then compare the two network connections. For a useful comparison, don’t switch networks while refreshing a subscription or changing servers. If you’re using Scene and the two networks may match different scenes, note that difference first; don’t attribute the result solely to the network.
Compare two networks using the same server
Wi‑Fi
- Disconnect Shadowrocket and use a browser to confirm that Wi-Fi has internet access. If a sign-in page is required, complete that first.
- Return to Home, confirm the dot is still on the same server, reconnect, and run Connectivity Test.
- Note whether the test returns a latency, times out, or the connection switch won’t stay on.
Cellular data
- If your device has cellular data and it’s available for use, turn off Wi-Fi and first confirm that a regular webpage opens.
- On Home, keep the same server and routing mode, reconnect, and run the same test again.
- If the test times out only on cellular data, first confirm that Shadowrocket can use cellular data, then note the difference for further investigation.
If only one network times out, check that network first. If both time out, check the server and settings shared by both tests; don’t infer a specific cause from the results alone.
Check the server settings against the details provided by your service provider, including the protocol, hostname, and port. For example, if the provider specifies 443 for a particular connection, check that entry’s port is 443—don’t change the port for every server. If the provider confirms that the settings have changed, update the existing subscription. After updating, return to Home and check the dot again, since entries before and after an update may have the same name.
Switch turns off or reconnects unexpectedly: check local connection settings
- The switch turns off as soon as you turn it on: Check whether the system is still waiting for VPN authorization, then see if the device is managed by your workplace or school. If management restrictions apply, ask the device administrator; don’t remove the management configuration as a test.
- It reconnects after you disconnect manually: In Shadowrocket, open Settings → On Demand and check whether On Demand is enabled and its conditions are being met. If you need to test manual connections and disconnections, you can temporarily turn off On Demand if you’re allowed to change it, then restore the original setting afterward.
- The switch stays on, but a destination won’t load: Keep the switch on, note the Connectivity Test result, then use the Global Routing comparison above to check the destination. There’s no need to repeatedly delete and recreate the VPN configuration.