Shadowrocket First Connection: Select a Default Server and Run a Connectivity Test

Just imported a subscription? Select a default server in Home, turn on the connection, allow the VPN configuration, then run Connectivity Test.

At a Glance

This guide uses Shadowrocket on iPhone / iPad and is for users who have obtained a subscription from their own service provider but have not completed their first connection. Check the subscription, choose a default server, confirm Global Routing, authorize the VPN configuration, then use Connectivity Test and real web requests to verify the result. A server appearing in the list does not mean it is selected, and an enabled connection does not guarantee access to every website.

1. Check Your Subscription and Network Before Connecting

Temporarily disconnect Shadowrocket and make sure your current Wi-Fi or cellular network can access websites that are normally reachable. If public Wi-Fi requires web-based sign-in, complete that first. Changing proxy protocols, repeatedly refreshing a subscription, or switching servers cannot replace network authentication when the underlying connection is not online.

This guide assumes you already have your own service provider and subscription. Get subscriptions from your provider; this site does not provide, sell, or recommend nodes or subscriptions. A subscription imports server settings, but availability also depends on your account status, server configuration, and current network. A one-time app purchase is not a service plan, and installing the app does not automatically provide a working connection.

If you have not imported a subscription yet, tap “+” in the top-right corner of Home, set Type to Subscribe, enter your own subscription URL, and save. Then return to Home to check the update. Subscription URLs often contain access credentials, so do not share screenshots or paste the full URL into support messages. If a group appears but contains no servers, check the URL, expiration, and update errors before proceeding.

2. Select a Default Server in Home and Connect

The default server is used for connections that need the default proxy route. Tapping a server name, opening its details, and selecting it as the default are separate actions. For your first connection, check that the selection indicator to the left of the server is on the intended entry. If the current Config uses a policy group, that group may determine the route for individual requests, so confirm the routing mode in the next section too.

  1. Choose a Server

    Go to Home, expand an existing subscription group, and choose a server that your provider confirms is still active. The name is only a label; it does not tell you the protocol, region, or availability.

  2. Tap the Circle on the Left

    Tap the circle to the left of the server and make sure the selection indicator appears beside the intended entry. Keep this server selected for now to make troubleshooting easier. Avoid changing multiple settings between tests.

  3. Check the Routing Mode

    Check Global Routing in Home. Use Config if you have a trusted, verified rule configuration. To temporarily rule out rule-related issues, use Proxy to test the proxy connection.

  4. Turn On the Connection

    Turn on the connection switch at the top of Home. When iOS first asks to add a VPN configuration, confirm that the request is from Shadowrocket, tap Allow as prompted, and complete any device verification.

  5. Check the Connection Status

    Return to Home and confirm the switch stays on, then check the system VPN status. Run Connectivity Test and try an actual page in your browser. Do not consider the connection verified based only on the VPN indicator.

3. Understand Config, Proxy, and Direct in Global Routing

Global Routing determines how traffic is routed; it is not a server protocol setting. Home offers Config, Proxy, Direct, and Scene modes. Scene applies settings based on configured scenarios, so do not use it as a baseline for initial troubleshooting until you understand how the scene is set up. Here are the three modes most relevant to an initial test.

Config: Follow the Configuration

Recommended

The active configuration’s rules and policies determine the route. Traffic may be proxied, connected directly, or rejected; it is not simply “some traffic through the proxy, everything else direct.” Check the specific rules and the final FINAL rule before using this mode.

Best for: Everyday use when you have clear routing requirements and have verified the active configuration.

Proxy: Test the Proxy Route

Connections handled by this routing mode are sent through the proxy route, making it easier to temporarily rule out the effects of Config rules. This does not bypass system restrictions or guarantee that every type of traffic on the device will use the proxy.

Best for: Checking whether the selected server can handle requests, or investigating differences caused by routing rules.

Direct: Connect Directly

Requests use a direct connection. If a webpage loads in this mode, your current network may simply be able to reach it directly; that does not prove the selected proxy server works.

Best for: Comparing against your underlying network to see whether an issue occurs only over the proxy route.

For example, DOMAIN-SUFFIX in Config matches domain suffixes, IP-CIDR matches IP address ranges, GEOIP matches against an IP geolocation database, and FINAL handles requests that did not match earlier rules. Rule order and the selected policy determine where traffic goes. Do not delete all rules just to address a single timeout. If Proxy works but Config fails, first check which rule and policy match the target domain rather than immediately re-entering the server password.

4. Run Connectivity Test, Then Check Real-World Access

Once connected, find Connectivity Test in Home and run it. Wait for the current test to finish. It provides evidence about connectivity to its specified test target, but does not prove that every website, protocol, or network condition will work. The test target may not represent the services you actually use, so consider its result alongside the routing mode and real requests.

1 server
Keep one default server selected for each test round to reduce variables
2 types
Evidence: Connectivity Test and real requests
3 items
Record the server, Global Routing mode, and current network
  1. Record the selected server, Global Routing mode, and network, then run Connectivity Test. If the result includes a response time, treat it as a measurement under those test conditions—not as a download speed.
  2. Open a browser and visit an HTTPS page you normally use and expect to access through the proxy. Start a fresh page load; do not count a page displayed from the offline cache as a successful test.
  3. Then visit a page known to be directly reachable. With Config, the two pages may take different routes. Check the matching rules and route shown in the request log rather than expecting both pages to behave identically.
  4. If the test and actual browsing results differ, keep the current settings and first check whether the test target and the site you need use the same route. Then consider adjusting DNS, rules, or the server.

5. Troubleshoot by Symptom; Change One Setting at a Time

Start troubleshooting with an observable symptom. Note whether the failure happens when turning on the connection, during the test, or while loading a specific page, then change just one condition and test again. The two sets of symptoms below call for different checks; do not assume they both mean the subscription has expired.

Choose Checks Based on Where the Failure Occurs

Connection Switch Will Not Stay On
  • Make sure you allowed the initial system VPN configuration request and completed device verification.
  • Check whether another active VPN is competing for the system network configuration.
  • Check whether your device is subject to organization management restrictions. Do not repeatedly remove managed configurations.
  • Check Settings → On Demand to rule out automatic rules affecting the manual connection state.
Connected, but Requests Fail
  • Check that the server selected with the circle on the left is the same one you intend to test.
  • Make sure Global Routing is not set to Direct by mistake or to a Scene that does not match your expectations.
  • Verify the address, port, and authentication settings against the original details provided by your service provider.
  • If Proxy works but Config does not, check the matching rules and routing policy in Config.

First confirm that the device can establish a connection, then test remote requests. After changing one setting, repeat the test with the same target.

The port must match the server. For example, if your provider specifies port 443, enter 443. But do not change every other port to 443 just because a protocol is often used with TLS. Similarly, do not change Type based only on the server name. Shadowsocks, VMess, VLESS, Trojan, Hysteria2, and WireGuard use different fields and handshake methods; retrying will not fix an incorrect Type.

If your provider manages the subscription, update the original subscription and check the service status before making manual edits that may be overwritten at the next update. For TLS errors, check the device time and the relationship between the server address, SNI, and certificate. Do not treat disabling certificate verification as a routine fix. After updating, check the default selection again and confirm the test target has not changed.

6. Save a Baseline After Testing and Recheck When Networks Change

Once the first test succeeds, keep a reproducible baseline: the network, server, Global Routing mode, Config, and two real-world destinations that load successfully. If a problem appears later, returning to these conditions makes it easier to identify what changed than resetting everything at once.

The system authorization steps in this guide are for iPhone / iPad; installation and system permission screens differ on other platforms. Shadowrocket is available across platforms: iPhone / iPad costs $2.99 as a one-time App Store purchase. The developer is Shadow Launch Technology Limited; check the App Store listing for system requirements. The Mac (Apple Silicon and Intel), Windows, Android, and Linux versions are free. Choose your platform on this site’s download page, then follow the instructions shown on your device.

Download Shadowrocket