To connect with Shadowrocket for the first time, add your provider’s configuration, select a server, check Global Routing, then start the connection and allow the system to add a VPN configuration. This permission lets the app handle network traffic; it does not provide a server. This guide uses the iPhone and iPad Home screen as its reference and explains connection status, routing modes, connectivity tests, and the server list. It also covers what to check if you deny permission, the connection fails, or it reconnects automatically.
Before connecting: understand the app, subscription, and VPN permission
Installing Shadowrocket, importing a provider configuration, and allowing a VPN configuration are three separate steps. The app reads the configuration and handles traffic; a subscription imports and updates server details supplied by your provider; system permission lets the app create a VPN configuration. Completing one step does not mean the others are complete.
The iPhone and iPad version 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. Find the download links on the all-platform download page. The one-time app purchase does not include a service plan; get subscriptions from your provider.
Use Home to select a server, choose a routing mode, and control the connection. Config is for managing rule configurations, while Settings controls app behavior such as On Demand. You do not need to change all three screens during initial setup. Establish a connection you can test first, then adjust settings one at a time to see what affects the result.
VPN permission: prompted when the first connection is created
The system usually prompts you to add a VPN configuration the first time you start a connection that requires one. Do not assume the prompt must appear as soon as you open the app. If a valid configuration is already saved on the device, the system may not ask again. When prompted, make sure Shadowrocket is the app requesting permission before allowing it.
-
Prepare a configuration
Get a subscription from your provider. To use one, go to Home → tap “+” in the upper-right corner → Add Server, set Type to Subscribe, enter your subscription URL, and save. Do not use a regular website URL as a subscription URL.
-
Select a server
Return to Home and check that a server entry appears under SERVER, then tap the one you want to use. Saving a subscription and selecting a server are separate steps. If the list is empty, first check whether the import succeeded.
-
Check routing
Go to Home → Global Routing and check the current selection. Use Config if you have a trusted rule configuration. To troubleshoot the proxy path, you can temporarily select Proxy, then restore your original setting when testing is done.
-
Allow permission
Return to Home and turn on the connection switch beside Not Connected. When prompted to add a VPN configuration, tap Allow and complete any device verification required by the system.
-
Check the result
Check the connection status on Home, then visit the website you actually need to use. If the system configuration was added but the connection does not stay active, check the server and network rather than repeatedly deleting the configuration.
VPN permission is not certificate trustAllowing the system to add a VPN configuration grants the permission needed to create a network tunnel. It does not install a root certificate or enable HTTPS decryption. You do not need to trust certificates from unknown sources to complete this first-connection setup or clear a connection error.
Once allowed, traffic handled by this VPN configuration is processed according to the app’s routing settings. Whether a request connects directly, goes through a proxy, or is rejected depends on Global Routing, the active configuration, and the matching rules. Permission alone does not guarantee that every request passes through a remote server.
Home screen sections: status, tests, and SERVER
The Home screen brings together information about several different things. When troubleshooting, read each separately: the switch shows whether the tunnel is running, Global Routing determines how traffic is routed, and SERVER shows which servers are available. A latency figure or a VPN indicator in the system status bar alone cannot confirm that all network traffic is working properly.
| Section | What it does | What to check the first time |
|---|---|---|
| Not Connected | Shows the disconnected status; use the adjacent switch to start or stop the connection. | Check whether turning on the switch prompts for system permission and whether the connection stays active. |
| Global Routing | Select a routing mode, such as Config, Proxy, Direct, or Scene. | Make sure the selected mode fits your test; selecting a server alone is not enough. |
| Connectivity Test | Checks server connectivity using the current test method, for initial screening and troubleshooting. | Check the test method and target, and whether the result timed out. |
| SERVER | Lists servers added manually or imported from a subscription. | Check that a server exists and is selected, and that its connection details came from your provider. |
Names shown in the SERVER list are mainly for identifying entries; they do not confirm that the protocol or settings are correct. When adding a server manually, Type, server address, port, and authentication details must match. For example, if your provider gives you port 443, that number alone does not tell you which protocol to use. Shadowsocks, VMess, VLESS, Trojan, Hysteria2, and WireGuard each have their own configuration requirements.
Updating a subscription fetches server details again; it does not automatically fix every connection issue. If your provider changes an address or authentication details, update the relevant subscription and check the selected entry again. Do not assume a server selected before the update will still be there afterward. Subscription URLs often contain access credentials, so hide the full URL in screenshots, support requests, and logs.
Choosing Global Routing: understand the mode, then check the rules
The key distinction for first-time users is that Config applies rules, Proxy routes traffic through a proxy, and Direct connects directly for comparison. Scene uses routing behavior defined by its configured conditions; it does not mean “automatically pick the fastest server.” If you have not set up a Scene, do not use it as the default troubleshooting option for your first connection.
Config
RecommendedMatches traffic against the active configuration’s rules. The result may be DIRECT, a proxy policy, or REJECT. If no specific rule matches, FINAL usually determines what happens next; unmatched traffic does not necessarily go direct.
Best for: everyday rule-based routing with a trusted configuration.
Proxy
Routes traffic handled by the app through a proxy instead of choosing a policy rule by rule as Config does. Server details must still be correct and the remote server reachable; this does not bypass authentication or network problems.
Best for: temporarily checking whether a problem is caused by Config rules.
Direct
Routes traffic handled by the app directly, so you can compare it with the proxy path. Selecting a server under SERVER does not make Direct use a proxy connection.
Best for: comparing with direct access on your current local network.
Scene
Uses routing behavior based on the configured Scene conditions. Check both the conditions and their corresponding settings; do not infer how a request is routed from the mode name alone.
Best for: users who need routing behavior to change based on network conditions.
When using Config, check the active file on the Config screen; do not just confirm that a configuration appears in the list. Rules affect results in matching order: DOMAIN-SUFFIX matches domain suffixes, IP-CIDR matches IP ranges, GEOIP matches based on IP geolocation, and FINAL provides the final fallback. You do not need to change these rules during initial setup.
Connectivity Test: evaluate test results separately from real-world access
Connectivity Test is a troubleshooting clue, not proof that everything is working. Results depend on the selected method, test target, local network, and how the server responds. A result only shows that the specific test returned a response. A website can still fail because of DNS, the destination site, routing rules, or the remote server’s exit connection. Conversely, a probe timing out does not by itself prove that the server’s entire forwarding capability is down.
Troubleshooting: compare test results with real requests
Test returns a result, but websites fail
- Make sure the connection is on from Home; a server test alone does not start it.
- Check Global Routing so you do not mistake Direct mode for a proxy test.
- Temporarily compare Proxy and Config. If only Config fails, check the rules.
- Try another website to distinguish a problem with one site from a general failure.
Test times out and connection fails
- Stop the connection first and confirm that basic websites load on your local network.
- Check the selected entry under SERVER and the details supplied by your provider.
- If you know the settings have changed, update your subscription and select the server again.
- Note the test method and error message, then check the details with your provider.
Change one condition at a time. Keep the same server and destination while comparing routing modes or network conditions to pinpoint what changed.
Switching from Wi-Fi to cellular changes the local network and may also affect DNS and remote reachability. For a useful comparison, note the original server, Global Routing mode, and destination that failed before switching networks and trying again. Do not change servers, DNS, subscriptions, and rules all at once; even if that fixes the problem, you will not know why.
If you denied permission, reconnect automatically, or see an empty list
Most first-time issues fall into four categories: permission, server details, routing, and automatic connection settings. Read the current prompt and follow the relevant steps instead of resetting everything straight away. These instructions cover configurations already on your device and do not require purchasing the app again.
I tapped Don’t Allow. Can I grant permission later?
Return to Home and turn on the connection switch again, then allow the system to add the VPN configuration when prompted. If no prompt appears, check the existing configuration and connection status under Settings → General → VPN & Device Management → VPN. Managed devices may also be subject to device management policies.
It still says Not Connected after I allowed permission. Did it fail?
Not necessarily. First check that a valid entry is selected under SERVER, then verify the provider’s settings and your local network. The VPN configuration may have been added successfully even though the tunnel could not be established because the server is unreachable or authentication failed. Check the error message to narrow it down.
The connection comes back after I turn it off. What should I check?
Go to Settings → On Demand and check whether On Demand is enabled and review its trigger conditions. To troubleshoot manually, turn off On Demand first, then return to Home and turn off the connection. Also check whether another automation on the device is triggering a connection.
SERVER is empty. Will allowing VPN permission again add servers?
No. Go to Home → tap “+” in the upper-right corner → Add Server and import a configuration from your provider. For a subscription, set Type to Subscribe. After saving, check whether the subscription content loaded successfully. System permission does not create server entries.
First-connection checklist
The setup is not complete just because you tapped a prompt. You should be able to explain how the current connection, server, and traffic routing relate to one another. Keep a set of verified working settings, then adjust On Demand or rules later to avoid repeating troubleshooting.
- Permission: Shadowrocket’s VPN configuration is present in system settings, and the connection switch on Home works.
- Server: A server supplied by your provider is selected under SERVER. You rechecked the selection after updating the subscription.
- Routing: You know whether the current mode is Config, Proxy, Direct, or Scene. When using Config, you know which configuration is active.
- Verification: You tested an actual destination as well as Connectivity Test, rather than treating one latency result as proof that all traffic works.
- Restore: You restored the original routing mode after troubleshooting. Whether to enable On Demand depends on your needs.