This guide is for users who have imported their own server configuration on an iPhone or iPad. For your first connection, check three things: the dot is next to the intended item in the Home list, the connection switch stays on, and Connectivity Test returns a result for that item. Then visit a website to check whether the current Global Routing setting behaves as expected. A millisecond reading does not mean every website will use this server.
Select a default server and connect from Home
Before you begin, make sure your device is online and check the server list on Home with the connection switch off. If the list is empty, import a configuration you already have. If you only see a subscription group heading, check whether it contains selectable items. This site does not provide, sell, or recommend servers or subscriptions.
Check the server entry
Open Home and find the entry you want to test in the server list. If names are similar, open an entry's details to check its address and port, then return to the list and select it. Don't assume two configurations are the same based only on their labels, and don't change the protocol or port just to run a test.
Check the selection dot
On Home, tap the target server entry and make sure the dot marking the current selection moves to that row. Opening an entry's details does not select it. If the dot is still on the previous row, return to the list and select the intended entry before continuing.
Check the routing mode
On Home, open Global Routing and note the current setting. To check whether the default server can handle actual requests, you can briefly select Proxy, then restore the original setting when you're done. If you keep Config selected, test with a request that matches the active configuration rules; don't assume every website will use the proxy.
Turn on the connection
Return to Home and turn on the connection switch at the top of the screen. The first time you connect, iOS or iPadOS may ask to add a VPN configuration. Check which app initiated the request, tap Allow as prompted, and authenticate if needed. If you cancel authorization, the dot in the server list alone does not confirm that a connection was established.
Run the test
On Home, tap Connectivity Test above the server list and wait for the results to refresh. Check the result on the row you selected, not whether any row in the list succeeded. Then visit a website you can normally access to test an actual request.
Understanding Connectivity Test results and connection status
Interpret Connectivity Test results in the context of the test being run. A millisecond reading means the probe returned a result that could be timed; it is not a download speed or a guarantee that the entire session will be stable. A failed test means the probe did not succeed under the current conditions. A single result cannot tell you whether the server is unavailable, the device has a network issue, or the test target cannot be reached.
- The switch is on, but the test fails: The switch indicates the local connection state; it does not prove that the remote server responded to the test. First, check that the failed result is on the row marked with the dot, then try again on the same network. Don't change the address, DNS, and rules all at once.
- The test returns a reading, but websites won't load: Make a fresh request instead of relying on an already-open page that may be cached. Check Global Routing and the active configuration. A response from the test target doesn't guarantee that the website's domain resolves or that the site is reachable.
- The list shows results for multiple servers: Read the result for the relevant row; don't mistake another server's reading for the currently selected one. To compare another entry, make sure the dot has moved before your next request. Restore the original selection when you're done.
Global Routing: Which mode should you use for testing?
Checking the default server and checking your everyday routing are two separate tasks. Temporarily reducing routing variables makes it easier to distinguish a server-path issue from a rules issue. After restoring your usual settings, visit the actual target again. Consider pausing other network activity during the test so unrelated requests don't affect the comparison.
Proxy
RecommendedFor this test, send requests handled by Shadowrocket through the proxy, rather than using the current routing rules to determine whether ordinary web traffic uses it.
Best for: A brief first check of the default server. Restore your original mode when finished.
Config
Requests are handled according to the rules and policies in the active configuration. Two domains on the same device may use different routes, such as proxy and direct. Also check the fallback policy for requests that don't match an earlier rule.
Best for: Checking whether specific destinations are routed as expected under your existing configuration.
Direct
Use direct mode. If a website opens, that only confirms it is reachable directly; it does not prove that the default server forwarded the request.
Best for: Comparing access to the same website without using a proxy.
If you were using Scene, note the original setting and whether its conditions might change with the network environment. When comparing two test results, change only one condition at a time if possible. Switching networks, scenes, and the default server all at once makes the results difficult to compare.
Compare results over Wi-Fi and cellular
A successful test on one network doesn't guarantee the same result after switching networks. For a useful comparison, keep the same server, routing mode, and destination, and make sure the device has actually switched to the other network. If cellular data isn't available, record the Wi-Fi result and leave other system settings unchanged.
Test the same server on two networks
Wi-Fi
- Complete any network sign-in or confirmation steps before connecting Shadowrocket.
- On Home, check the dot and note whether that row has a test result, then visit the same website.
Cellular
- Make sure the device is using cellular data, and keep the server and routing mode unchanged.
- Run Connectivity Test again, then make a fresh web request. Don't reuse the result from the previous network.
If the test fails on only one network, check basic connectivity and rerun the probe on that network first. Don't conclude that the configuration is invalid based on this alone.
Recovery steps if the first connection fails
- The switch won't turn on or turns off right away: First, check whether you authorized the system VPN configuration. If the system reports an error, note its wording and check the switch again on Home instead of repeatedly selecting servers. If the connection turns back on after you switch it off manually, check whether Settings → On Demand is enabled and whether the current network meets its connection conditions. Keep the original settings so you can restore them after testing.
- The same server fails on both networks: Open the entry details and check the existing configuration's protocol, address, port, and authentication details. Use the port specified in the original configuration. A website using HTTPS does not mean you should change the proxy server's port to 443. If the entry came from an existing subscription, check that it updated successfully and confirm that the dot is still next to the intended entry afterward.
- Proxy works, but Config doesn't: First check the active configuration and the policy matched by the target domain. For example,
DOMAIN-SUFFIXmatches domain suffixes, whileFINALhandles requests that don't match earlier rules. Don't change every rule to use the same policy just because the default server passes the test. Keep the original configuration and check only the rules relevant to your destination. - When testing is complete: Restore your original Global Routing mode and any On Demand settings you want to keep. If the connection was only for a temporary test, turn it off afterward and check its final state. To document an issue, note the network type, routing mode, selected entry label, test result, and what happened when you tried to access the site. Don't include subscription links or authentication details.