Step 1: Add a Server and Import a Subscription
First, identify what information you have: a complete subscription link, a share containing details for one server, or server details made up of an address, port, and authentication parameters. Each requires a different import method. Do not enter a subscription link as a server address, and do not infer the protocol from the server name alone. Open Shadowrocket, go to Home, tap the plus sign in the upper-right corner to open Add Server, then follow one of the two paths below.
Have a subscription link? Choose Subscribe
In Add Server, open Type and choose Subscribe. Enter your complete subscription link in URL, add a recognizable name in the remarks field, and save. The link should include all query parameters. When copying it from a chat or note, check for leading or trailing spaces, line breaks, and accidentally included punctuation. A subscription link may contain access credentials. Do not paste it on a public page or show its full contents to others.
After saving, return to Home and check whether the subscription has fetched a server list. If you see the subscription name but no servers, check for an error message, then use the action menu for that subscription to update it. The subscription address must be reachable over your current network. If the client is not connected and the subscription address is unreachable, the first update may fail. This is a different stage from “the server was imported but the connection failed,” so handle each separately instead of repeatedly adding the same subscription.
When server entries appear, select one for the initial check. If there are multiple groups, note which subscription and server you selected and keep them unchanged during testing. Updating a subscription fetches its remote contents again and may change the number of servers or their parameters. There is no need to update repeatedly during the initial check, or to manually edit multiple server fields at once.
Have details for one server? Enter its actual protocol
From Home, tap the plus sign to open Add Server. In Type, choose the protocol that matches your information, such as Shadowsocks, VMess, VLESS, Trojan, or WireGuard. Then enter the address, port, and the authentication and transport parameters required by that protocol. Required fields vary by protocol; passwords, UUIDs, keys, TLS, and transport settings are not interchangeable. Use the complete details you have rather than filling in missing information based on assumptions.
Save when finished, then return to Home and confirm that the new entry appears. If you have a QR code, use Scan QR Code to read your existing share, then confirm the protocol and required fields after scanning. Importing information only adds it to the client; it does not prove that the server is currently available. This step is complete when the correct entry appears in the list and can be selected. Next, choose how that entry should handle traffic.
Step 2: Choose a Global Routing Mode
Tap Global Routing in Home, check the current selection, and decide whether to change it. The three modes are Config, Proxy, and Direct. They determine how connections are handled; they are not separate server lists and do not create a new subscription for your device. For an initial setup, first check whether the server works, then consider more detailed rule-based routing. This keeps server issues separate from configuration issues.
Proxy: Test the selected server first
Proxy is useful as a baseline for the initial connection: connections handled by the client use the currently selected proxy, making it easier to check whether the newly imported server can complete a real request. After choosing Proxy, return to Home and confirm that the server you intend to test is selected. Do not change DNS, transport parameters, or configuration rules at the same time. Keeping the conditions simple makes the results easier to interpret.
Config: Use the rules in the current configuration
Config handles connections according to the rules in the currently enabled configuration. Open Config, confirm that the intended configuration is selected, then return to Home and choose Config. Rules may direct different destinations to PROXY, DIRECT, or other defined policies, so “connected” does not mean every request uses the same server. Subscription import provides the server list; Config handles rules and policies. Keep these functions distinct.
For example, the rule below applies the PROXY policy to matching domains. It is only an example for understanding the syntax; you do not need to add it during initial setup. Copying a single line does not replace a complete configuration.
DOMAIN-SUFFIX,example.com,PROXY
Direct: Compare without proxy forwarding
Direct means connections are not forwarded through a proxy server. Use it to check whether the basic network works or to compare the same request with Proxy. It will not fix an invalid subscription or prove that a server is working. Choosing Direct in the app is different from turning off the connection switch entirely: the former is a traffic-handling mode in the client, while the latter stops the current connection. After choosing a mode for testing, continue to the next step and connect.
Step 3: Turn On the Switch and Confirm Connection Permissions
Return to Home. First confirm that the server entry is selected, then check that Global Routing is still set to the mode you chose. Finally, turn on the connection switch at the top. The order matters: if you connect without checking the server and mode, you may not know which entry or handling mode was actually used, even if access succeeds.
On the first connection, the system will ask to add a VPN configuration. Read the prompt, make sure it follows an action you just initiated in Shadowrocket, then allow it as required by the system and confirm with your device passcode or biometric authentication. This VPN configuration is a system network permission, not another subscription. If you cancel this step, the app may not be able to connect when you return. Turn on the switch again and complete the system confirmation.
After confirming permissions, return to Shadowrocket and check whether the switch and connection status remain active. Some devices show a VPN indicator in the status bar or Control Center, but the indicator only reflects the system connection status; it does not prove that a target page was reached by the expected route. If the switch turns off immediately, check the error displayed in the app and the system permissions first rather than changing rules. If another VPN connection is active on the device, stop any connection you do not need to make the test conditions clear.
You can leave On Demand unconfigured during this manual check. It triggers connections based on conditions and is separate from the manual switch. First complete the basic process: turn on the connection manually, keep it active, and access the target. Then learn about on-demand connections if needed. At this point, you have only connected; the next step is to verify the result with a test and a real request.
Step 4: Verify with Connectivity Test and Real-World Access
Start with Connectivity Test to check server connectivity, and note how the test works. The reported time reflects only the test destination and network conditions at that moment. It is not the same as web download speed and does not guarantee that every app request will succeed. A result for an entry can be a reason to continue testing; a timeout means more checks are needed, but one result alone cannot identify a specific incorrect parameter.
Next, open a browser and make a new request to a page you can normally access and know how it should behave. Do not rely only on an old page that has already loaded, because caching may keep it visible during a network issue. Refresh the page or reopen the target app if needed, then check whether text, images, and subsequent content continue to load. Keep the same server, mode, and network while making an initial stable observation.
Then return to Shadowrocket and check Data for traffic changes during the test. A change indicates connection activity, but background synchronization may also generate traffic, so it is supporting evidence rather than a substitute for checking actual access. Likewise, traffic under Config does not prove that a particular domain matched PROXY. Consider the active rules and the connection records visible in the app.
If the result is unclear, compare one variable at a time. Note the current server and mode, test the same destination with Proxy, then switch to Direct and make a new request while leaving all other settings unchanged. If Proxy works but Config fails, check the selected configuration and rules first. If Direct also fails to reach a page that normally works, check the Wi-Fi or cellular network itself. A network change alters the conditions, so test again after switching and do not combine results from different network conditions.
Once access is verified, choose the mode you need for everyday use. Use Config when you have a valid ruleset; choose Proxy when you want to use the current proxy consistently. The initial setup is complete not when an icon changes color, but when the selected server is clear, the mode is as expected, the connection remains active, and the target app can complete a real request.
Step 5: Troubleshoot by Stage; Change One Thing at a Time
When something goes wrong, first identify where you got stuck, then decide what to check. Keep the original working information and adjust only one condition before testing again. Deleting subscriptions, recreating servers, changing modes, and editing DNS all at once makes it impossible to compare results. Repeatedly importing the same information can also leave entries with similar names and increase the chance of selecting the wrong server.
Import fails or the server list is empty
Check that the link is complete and still valid, and that your basic network can reach the subscription address. A web address, a subscription address, and a single-server share are different types of data. Return to Add Server and check whether Type is set to Subscribe. If you see an authentication, expiration, or content-format message, check the original information with the provider of your existing service instead of guessing by repeatedly editing link parameters. See the subscription and node import section of the FAQ for details.
The entry appears, but the connection test or real request fails
For a manually added server, check the protocol, address, port, and authentication parameters one by one. Match TLS and other transport options against the original details as well. For an entry created from a subscription, first confirm the result of the subscription update instead of treating a temporary manual edit as a lasting fix. You can test another existing entry in your own list under the same conditions, changing only the server while keeping the mode and destination unchanged.
The connection switch will not stay on
Return to system settings and check that the VPN configuration is allowed. Also check for any pending permission prompt on the device. Managed devices may restrict VPN configurations; if you see a management notice, contact your device administrator. Do not treat a permissions issue as a rules issue. While the switch will not stay on, changing DOMAIN-SUFFIX or other rules will usually not resolve the connection permission itself.
Proxy works, but some destinations fail in Config
First, open Config and confirm which configuration is enabled. Then check whether the rules assign the affected destination to the expected policy. Rule order, the choice between DIRECT and PROXY, and the final fallback rule can all affect the result. If only some domains have issues, continue checking DNS and connection records, but avoid replacing the entire configuration and DNS settings at the same time during initial use. See the full manual for systematic guidance on rules, DNS, and Settings.
Tests sometimes succeed, then fail after a network change
Repeat the real request on the same network first to see whether the condition is reproducible, then record Wi-Fi and cellular results separately. A low test time does not guarantee stable transfers, and failure on one page does not mean all connections are unavailable. If you need help, provide the step you reached, the mode, the protocol type, and an error message with sensitive information removed. Do not send a complete subscription link, password, or key.
For everyday troubleshooting, follow this short sequence: check the basic network, then the selected server, then Global Routing, and finally the configuration and target request. After updating a subscription or changing settings, repeat the verification in Step 4. Leave more complex multi-subscription maintenance and diagnostics until the basic process is stable, so the initial connection has fewer variables.