At a glance

For users who have imported their own configuration but have not connected yet. Check the server and Global Routing in Home, complete the system VPN authorization, then assess Connectivity Test results alongside real-world access. This guide focuses on the first authorization on iPhone and iPad, distinguishing between an imported configuration, an active tunnel, and working access to a destination—so you can avoid changing unrelated settings.

1. Get ready: make sure a server appears in the list before connecting

Shadowrocket is available for iPhone, iPad, Mac, Windows, Android, and Linux. On iPhone and iPad, it costs $2.99 as a one-time App Store purchase; check the App Store listing for system requirements. The Mac (Apple silicon and Intel), Windows, Android, and Linux versions are free. To install, choose your platform in the download guide. The system authorization steps below apply to iPhone and iPad; prompts may differ on other platforms.

This guide assumes you already have a provider and subscription. The app's purchase price is separate from any service plan. This site does not provide, sell, or recommend servers, subscriptions, or proxy services. A successful import only means the app has read the configuration; it does not confirm that the server credentials are valid, the service is available, or your current network can reach the server.

If you have not imported a list yet, tap “+” in the upper-right corner of Home to open the add screen. Choose Subscribe, enter your own subscription URL, and save it. Then check the updated server list. Subscription URLs may contain account tokens; do not post the full URL, QR code, or configuration file in a public forum. If your list is already available and you can select a server, there is no need to add the subscription again just to connect for the first time.

2. Choose a default server in Home and complete VPN authorization

The default server is the one used when a default proxy route is needed. Its selection is separate from whether the server is online, and it does not override every policy group in Config. Select a server in Home before turning on the connection, so you have a clear target for troubleshooting. Opening a server's edit screen does not select it as the default.

  1. Select a server

    Open Home and tap the server you want to use. Confirm that its selection indicator appears. Note the server name and use the same server for Connectivity Test later, so the test and your actual connection refer to the same server.

  2. Check routing

    Go to Home → Global Routing and check whether the current mode is Config, Proxy, Direct, or Scene. Use Config for an existing, complete ruleset. To temporarily isolate the effect of rules, switch to Proxy and note the original setting.

  3. Turn on the connection

    Return to Home and turn on the connection switch at the top. When the system first asks to add a VPN configuration, confirm that the request is from Shadowrocket, allow it, and complete device authentication as prompted.

  4. Check the status

    Return to Home and check whether the switch stays on and the connection remains stable. If authorization was canceled or denied, try connecting again and respond to the system prompt. Do not immediately change the server password, port, or DNS.

  5. Run a test

    Run Connectivity Test in Home to check the server, then visit a familiar HTTPS page. Record the test result, how the page loads, and the current Global Routing mode. Repeat under the same conditions when troubleshooting.

System authorization for a VPN configuration allows the app to establish a local traffic tunnel. It does not purchase a service plan or confirm that authentication with the remote server succeeded. If the switch stays on, the local connection process has reached the running stage; an incorrect server password, an unreachable server, or a problem with the destination can still cause subsequent requests to fail. Do not assume the entire route works based only on the system VPN status.

3. Global Routing: check where test traffic is routed

A common source of confusion during first-time setup is that a server is selected, but the test request does not follow the expected route. Global Routing controls the routing mode; selecting a default server in Home only handles one part of the setup. In Config, a request may match DIRECT, a policy group, or REJECT—it does not necessarily use the default server you just selected.

Config

Recommended

Routes requests according to the active Config rules. DOMAIN-SUFFIX matches domain suffixes, IP-CIDR matches address ranges, GEOIP matches by IP geolocation, and FINAL handles requests that did not match earlier rules. The result depends on rule order and policy settings.

Best for: users with a trusted configuration who want to use rules for everyday traffic routing.

Proxy

Routes requests normally controlled by routing rules through the proxy. This can help temporarily rule out the effects of Config rules. System traffic boundaries and app behavior still apply, so do not assume every packet on the device has passed through the remote server.

Best for: briefly testing the server and connection, then restoring your usual routing mode.

Direct

Uses a direct connection. If a page opens in this mode, that does not prove the default proxy server works. If it does not open, that alone does not prove the server is faulty.

Best for: comparing access over your local network to distinguish basic connectivity issues from proxy connection issues.

Scene

Applies behavior based on the configured scene. The result depends on the scene settings; when troubleshooting for the first time, check which conditions apply. Do not treat Scene as a fixed route equivalent to Proxy.

Best for: users who understand and have configured scenes and need behavior to change with the network environment.

If a page works in Proxy but fails after switching back to Config, first check the matching rules, policy group selection, and FINAL destination in Config rather than reimporting the subscription. If both modes fail, check the local network, server settings, and service status. Change one condition at a time to make the results easier to compare.

4. Connectivity Test: a test result does not confirm full access

Connectivity Test helps you assess server reachability with the selected test method and current network conditions. It does not prove that every site, protocol, or service will work. Review the relevant test settings first: establishing a connection and sending an HTTP request test different layers, so results from different methods are not directly comparable.

3 steps
Select a server → connect → test; check selection, authorization, and connectivity separately
4 modes
Global Routing:Config / Proxy / Direct / Scene
443
The default destination port for HTTPS is not necessarily the port to enter for your server

After running the test, check whether a result appears or times out, then see whether repeated tests to the same server are consistent. The milliseconds shown measure the relevant test operation, not bandwidth or download speed. Enter the server port provided by your service provider. Do not change it to 443 just because browsers use HTTPS.

What you seeWhat it may indicateNext step
Test completes and the page opensThe test and that page request both succeeded at that timeKeep the settings and test the apps you actually use
Test completes but the page does not openA successful test does not cover every type of requestCheck Global Routing, DNS, destination rules, and remote authentication
Test times out but the page opensThe test target or method may use a different route from the pageCheck the test method and confirm whether the page actually used the proxy route
Test times out and the page does not openNeither check succeeded under the current conditionsCheck basic connectivity first, then review server and configuration settings

For a real-world check, use a familiar HTTPS address that is normally available. Reload it if needed to reduce the effect of caching. An HTTP request typically requires domain name resolution, a connection, and a TLS handshake. A reachable server port does not guarantee that all these steps will succeed. Do not attribute access denied by a single site to the Shadowrocket connection switch alone.

5. Connection problems: troubleshoot local status and the remote route separately

First determine whether the failure occurs before or after the connection switch is enabled. A switch that immediately turns off or incomplete system authorization is a different kind of issue from a stable connection with requests timing out. For the former, check local authorization and connection conflicts. For the latter, investigate the server, routing, and destination access.

Two troubleshooting paths: identify the issue first, then change settings

Local connection not established
  • Make sure you allowed the system request to add a VPN configuration; dismissing the prompt is not enough.
  • Disconnect any other active VPN, then return to Home and try again once.
  • Go to Settings → On Demand and check whether automatic connection rules are affecting the manual test. Note the original settings before making temporary changes.
  • If your device is managed by an organization that restricts VPN changes, contact the device administrator. Do not repeatedly delete configurations to try to bypass the restriction.
Connected, but requests fail
  • Turn off the connection and confirm that your Wi-Fi or cellular network can access the internet on its own.
  • Check the server address, port, credentials, TLS, and transport settings against your original details.
  • Temporarily compare Proxy and Config to distinguish a server connection issue from a rules or policy issue.
  • If the configuration came from a subscription, update it and check that the selected server is still listed and unchanged.

Keep the original configuration and change one variable at a time. Record the network type, server name, routing mode, and test results so you do not mix results from different conditions.

A subscription update refreshes the content provided by your service provider, but it cannot resolve an expired account or a remote service issue. If server names, order, or details change after an update, recheck your default selection; do not assume the server is unchanged just because it remains in the same list position. For UUID, password, or subscription token issues, share only the information your provider needs. Cover sensitive fields in public reports.

6. After your first successful connection: restore your usual settings and keep a record

A successful first test means more than seeing the switch turned on. You should be able to explain the route for a request: which server is selected, which Global Routing mode is active, what Connectivity Test reported, and whether the app you use can access what it needs. Restore temporary troubleshooting settings promptly. In particular, do not assume a brief test in Proxy has verified every Config rule.

If problems occur only after switching networks, test Wi-Fi and cellular with the same server and routing mode. If they occur only after a subscription update, check for changes to the server list and default selection first. Comparing conditions this way is more precise than describing every issue as “not connected,” and makes it easier to explain the problem to your own service provider.

Get Shadowrocket and complete the first setup

The iPhone and iPad version costs $2.99 as a one-time App Store purchase. The Mac (Apple silicon and Intel), Windows, Android, and Linux versions are free. Check the App Store listing for iPhone and iPad system requirements. The developer is Shadow Launch Technology Limited, and the app ID is 932747118. Buying the app does not include a service plan; use your own configuration.