This guide is for users who have imported a provider configuration but have not completed their first connection. Using Shadowrocket on iPhone or iPad, check the default server, Global Routing, the Home switch, and system authorization in order, then verify with Connectivity Test and real-world browsing. You should be able to distinguish an imported configuration from an active VPN and a working request—not judge success by the switch alone.
Before connecting: distinguish setup, connection, and access
A server appearing in Shadowrocket’s list means the app has a configuration it can try; it does not guarantee that the remote server is reachable. A latency result in the list is not a substitute for testing access. For your first attempt, keep the current configuration and change one setting at a time. Changing the server, DNS, and routing behavior together makes it harder to identify the cause of a problem.
Use Home to select a server and connect, Config to manage configuration files, and Settings to adjust app preferences. Get subscription links from your provider; this guide assumes you already have a provider and subscription. Buying the app does not include a network service plan, and installing it does not automatically provide a usable server configuration.
Step 1: Select a default server on Home
The selected marker in the Home list identifies the default server. If you have imported several servers, their order or names alone do not tell you which one is active. Usually, tapping a server row selects it; the details or edit control on the right opens its settings and does not switch the default server.
-
Return to the list
Open Home, expand the imported subscription group, and find a server provided by your service provider. If the list is empty, import or update the configuration before turning on the connection switch.
-
Select a server
Tap the row for the server you want to use and check that the selection dot moves to it. Test one server at a time; do not cycle through several servers in quick succession.
-
Check the parameters
Open the details using the control on the right of the row and check the server address, Port, protocol, and authentication details. Use the values supplied by your provider; do not guess the port based on the protocol name.
-
Note the selected server
Note the server name so you can match the Connectivity Test result to the server you selected. Do not include passwords, UUIDs, or full subscription links in your notes.
Selecting a default server does not guarantee that every request will use it. With Global Routing set to Config, rules may direct requests to a specified policy or policy group, which may in turn select a different server. Check the default selection and the route used by the rules separately.
Step 2: Check Global Routing
Open Global Routing on Home and check the current mode. You do not need to rewrite rules for a first connection. If you already have a matching configuration, start with Config. To test the selected server on its own, switch briefly to Proxy for comparison. The modes below describe Shadowrocket’s routing behavior.
Config
RecommendedRequests are routed according to the rules in the current configuration. Rules can select DIRECT, a proxy policy, or a policy group; the result depends on the configuration in use. It is not safe to assume that unmatched requests always connect directly.
Best for: checking everyday rule-based routing with a working configuration.
Proxy
Requests handled by the app are sent through the selected proxy. This can help reduce differences caused by rules. Do not assume that system-routed traffic or traffic the app does not handle follows the same route.
Best for: briefly checking whether the default server can handle requests.
Direct
Requests handled by the app connect directly to their destinations without using a proxy server. A website opening in this mode does not prove that the server configuration works.
Best for: comparing direct access with the proxy route on your local network.
Scene
Applies routing behavior based on the configured scene conditions. Check the scene settings and current match results first; this is not a fixed proxy mode.
Best for: users who have configured behavior to change with network conditions.
If some sites work and others do not in Config, check which rules in the current configuration match those requests. For example, DOMAIN-SUFFIX,example.com,DIRECT sends example.com and its subdomains to DIRECT. FINAL,DIRECT sets the final policy for requests that do not match any earlier rules. Do not delete existing rules just to run your first test.
Step 3: Turn on the switch and authorize the VPN
Return to Home and turn on the connection switch at the top. The first time you connect on iPhone or iPad, the system asks for permission to add a VPN configuration. This permission creates a VPN interface on your device; it is not subscription sign-in and does not replace authentication details for the remote server.
-
Turn on the switch
After checking the selected server and Global Routing, turn on the switch at the top of Home and wait for the system authorization prompt or a change in connection status.
-
Allow the configuration
Make sure the system prompt was triggered by your current action, then tap Allow. If the system asks for your device passcode or local authentication, follow its instructions. Do not enter your device passcode in a subscription URL field.
-
Check the status
Return to Home and confirm that the connection switch stays on. You can also check the status in system Settings → General → VPN & Device Management → VPN; labels may vary with your system language and layout.
-
Continue testing
Once the VPN shows as connected, run Connectivity Test. The system status only confirms that a local tunnel has been established; it does not by itself verify remote authentication, DNS, or access to the destination.
Step 4: Run Connectivity Test
Find and run Connectivity Test on Home. Record the result alongside the selected server, Global Routing mode, and network in use. The test reflects only its target and method at that moment; it does not establish that every website is reachable or predict download speeds.
- First, check what is being tested. If results are listed by server, check the result for the default server. Do not treat a successful result for a different server as the result for your current connection.
- Next, check the test method. A TCP connection test mainly checks whether a connection can be made to the server’s port. Tests that include application-level requests involve more steps. Even if the result shows a time in milliseconds, check what was measured and how.
- Then test real-world access. Keep the switch on, open a destination you know should use the proxy, then open one that should connect directly. Check whether each page loads.
- Finally, test again for consistency. Run the test once more without changing the configuration. If successes alternate with repeated failures, investigate network instability instead of keeping only the successful result.
For example, “Connectivity Test succeeds, but a website still will not open” and “the test times out and no destinations are reachable” are different symptoms. In the first case, check the destination domain, DNS, and routing rules. In the second, start with the local network, selected server, and configuration parameters. This is a troubleshooting order, not a definitive diagnosis based on symptoms alone.
Test passes or fails: what to check
Test passes, but a page fails
- Confirm the browser opened the intended destination, not a cached page.
- Check that Config routes the domain to the intended policy.
- Switch briefly to Proxy for comparison, then restore the original mode.
- If only one destination fails, check whether that destination is available.
Test fails and connection has problems
- Disconnect and confirm that the local network can access the internet.
- Check that the selection dot is still next to the intended default server.
- Check the address, Port, and authentication details against your provider’s information.
- Switch only between Wi-Fi and cellular, then test the same server again.
Change only one condition per test. When you finish, restore your usual Global Routing and On Demand settings.
First connection failed: narrow down the cause by symptom
Do not replace the entire Config immediately after a failure. First identify whether the issue occurred during system authorization, server connection, or the destination request. The steps below are ordered to minimize disruption and preserve useful comparisons.
| Symptom | Check first | Next step |
|---|---|---|
| Home switch will not stay on | System VPN authorization, device management restrictions, and the status of other VPNs | Complete system authorization and stop any other active VPN. If the device is managed, check with the administrator about permissions. |
| VPN connected, but test times out | Local internet access, server address, and Port | First check direct access, then test the same server on another type of local network. Avoid changing protocol parameters at the same time. |
| Proxy works, but Config does not | Rule order, policy names, and policy group selection in Config | Check which rule matches the request and confirm that the server referenced by the policy is still available. |
| Wi-Fi fails, but cellular works | Wi-Fi authentication, DNS, and network access restrictions | Complete the network sign-in page and test again with the same configuration. Keep the results from both network types for your provider to investigate. |
| Server list changes after updating subscription | Whether the previous default server is still listed and whether the selection marker has moved | Select the intended server again, then run the test. Do not assume the same list position refers to the same server before and after an update. |
For configurations that use TLS, check TLS, Server Name, and transport parameters against your provider’s information, and confirm that the device clock is accurate. Do not hide configuration errors by casually disabling certificate verification. Shadowsocks, VMess, VLESS, Trojan, and other protocols use different authentication fields; changing only the protocol name will not make the original parameters valid.
After connecting: final checks
A first connection is not complete just because the switch is on. The configuration, routing, and actual access should all agree. Use this checklist to wrap up troubleshooting, then compare against these known-good conditions if a problem occurs later.
- The default server is correctly selected on Home, and its details match your provider’s information.
- Global Routing is back to your usual mode, and you have not left the temporary Proxy mode selected.
- The system VPN status is normal, and both Connectivity Test and real-world page access have been checked.
- If you need automatic connections, open Settings → On Demand to configure the conditions, then test when the connection starts and disconnects.
- Keep a record of the server name, network type, routing mode, and error message. Hide authentication details and subscription credentials when contacting your provider.
After changing servers, updating a subscription, or switching local networks, repeat the same sequence: check the selected server → connect → test → verify real-world access. Menus may differ on other platforms, but check each of these states. Do not apply iPhone or iPad system authorization steps directly to desktop systems.