Shadowrocket Troubleshooting

Start with this site's purchase and setup guide, then open the product page using its App Store link rather than relying on search ranking alone. If the store says the app isn't available in your region, check the country or region of the account currently signed in to the App Store and whether content or purchase restrictions apply to your device. To check the account region, open Settings, tap your Apple Account, go to Media & Purchases, and view Country/Region; labels may vary by device. Before making changes, review any balance, subscription, and payment requirements listed by the system. Avoid switching regions repeatedly just to troubleshoot search results.

Open the product page and check three details: the app name is Shadowrocket, the developer is Shadow Launch Technology Limited, and the product page URL contains id932747118. Then compare its icon with the official icon in this site's header. A matching name or icon alone isn't enough; the developer and app ID must also match. Before buying, review the price, compatibility, and purchase eligibility shown on the page. The App Store listing is the source of truth. If any detail differs, return to the purchase and setup guide and reopen the product page.

A one-time app purchase is not a service subscription. The App Store purchase covers use of the Shadowrocket client. To connect, you also need your own subscription or server details, and the associated service must still be active. The client reads configurations, establishes connections, and applies rules; buying the app does not automatically add a working server. Before importing your details, check the protocol, address, and authentication fields. This is the official website and guide; it covers purchasing and using the client, but does not provide, sell, or recommend servers or subscriptions.

Sign in to the App Store with the account used for the original purchase. Find Shadowrocket in your account's apps or purchase history, then use the redownload option shown; section names may vary by system version. Don't assume a purchase is missing just because the app icon isn't on your Home Screen. If the product page still shows a price, check that the account used for Media & Purchases is the original purchasing account, and review your order history. App purchase records and server configurations in the client are separate: after redownloading, you'll still need to import your own configuration or backup. Purchase eligibility is determined by the App Store listing.

The price is the local-currency amount shown by the App Store at checkout. A one-time purchase describes how the client is paid for, not how a connection service is billed. To check Family Sharing eligibility, review the product page's support information and the family's purchase-sharing settings; don't assume access is included just because you belong to the same family. iPhone and iPad are the primary devices. Check the same listing for compatibility with Mac, Apple TV, and Apple Vision. System requirements, compatibility, and purchase eligibility are subject to the App Store listing.

Open Shadowrocket's product page in the App Store on your iPad and check compatibility, then confirm which account is signed in for purchases. If that account has an eligible purchase, use the redownload option shown in the store; eligibility for your device is determined by the App Store listing. The iPad layout may differ from the iPhone layout, so look for interface labels such as Home, Config, and Settings instead of matching button positions. Installing the app doesn't sync server details automatically. After opening it, check your existing subscriptions, selected options, and connection authorization.

When you connect for the first time, the system may ask you to allow a VPN configuration. This authorization lets the device handle network connections according to the client's current configuration. First, confirm the prompt was triggered by an action you just initiated in Shadowrocket, then read the system message and approve it as prompted. If you previously declined, return to the client and try connecting again; check whether the prompt reappears. You can also check the VPN configuration status in Settings. Managed devices may have additional restrictions, so follow your device's management requirements rather than repeatedly deleting configurations without checking the cause.

First check whether Home has a selectable server, and confirm the selected entry has a complete address, port, and authentication details. If the list is empty or any fields are missing, fill them in first. Then check whether system VPN authorization is complete and whether another VPN connection or device management restriction is active. If the switch immediately turns off, note the client message and check the required protocol fields and current configuration. Avoid tapping repeatedly. Stop the connection, reopen the client, and try again. If it still fails, keep the error message and follow its guidance; this preserves useful troubleshooting details better than immediately reinstalling.

Home is where you view available servers, select the current connection, and control it. Config is for managing configuration files and related rules. Data shows traffic or request records; available details depend on what the app displays. Settings contains client preferences. Global Routing selects how connections are handled; it isn't a server name. Keep these English labels when following a guide so you can find the matching screen. Layouts may vary by device. If a button isn't where expected, look for its function rather than assuming a different app was installed because the interface language differs.

Keep your current server details, configuration files, and error messages before troubleshooting. Then review the App Store update notes and the client's current settings. Check whether Global Routing, the selected server, DNS, and On Demand still match your previous setup, then retry on the same network. If only one configuration is affected, compare its contents instead of clearing all data. Reinstalling may require you to import your details again and repeat system authorization, so prepare a usable backup first. App updates are delivered through the App Store. System requirements and compatibility are listed on the App Store page.

On Home, use the add option to open Add Server, choose the type for Subscribe, and enter your complete subscription link in the URL field. Save it with a recognizable name; button locations may vary by interface. Don't enter a subscription link as the address for a single server, or use the URL of a help page. After saving, check that the subscription group and its server entries appear, then select an entry to connect. Subscription URLs may contain access credentials. Check the link before and after pasting, and hide the full URL when sharing a screen or log.

Check that you copied the complete subscription link, including its beginning, ending, and query parameters, with no extra spaces or line breaks. Next, confirm that your current network can complete the subscription request, and check that the service and link are still active. A login page, help text, or error page doesn't mean the client can read a server list, even if the URL opens. Troubleshoot request failures and parsing errors separately based on the message shown by the client. Don't change the link and several network settings at once. If the list is still empty, ask your service provider to confirm the export format and access permissions, and keep any existing working entries.

Manual entry in Add Server is for entering your existing server details field by field, including the address, port, and authentication required by the protocol. Scan QR Code and clipboard import read pre-encoded server-sharing details or a subscription URL. Check what kind of information you have before importing; a subscription QR code isn't necessarily for a single server. After import, open the entry, verify the protocol and key fields, then save and test it. QR codes may contain credentials, so only process content you trust. If scanning fails, check image clarity and that the code is complete before changing a working configuration.

Find the relevant Subscribe group, use its update option, and check the server list and status message when the update finishes. An update fetches the remote content again, so subscription-managed entries may be added, removed, or changed based on the response. Don't assume manual edits to those entries will be preserved. If you need to keep separate details long term, organize them separately after confirming you have permission to use them, and back them up first. If an update fails, keep the existing group and check the network, link, and service status. A changed list doesn't necessarily mean the currently selected server is still suitable for connecting.

Give each Subscribe group a recognizable name based on its purpose, then check the server entries and current connection in each group. Before deleting anything, confirm whether the target is a single server or an entire subscription group, and make sure you have the original details or a backup to import again. A server managed by a subscription may reappear after an update if deleted individually, so distinguish remote list entries from standalone local entries. Backups and subscription links may contain authentication details; store them somewhere you control. Hide passwords, access parameters, and full addresses when sharing troubleshooting materials.

Config uses the rules in the current configuration file to decide how requests are handled. Choose it when you need rule-based routing and have checked the configuration. Proxy sends typical network requests through the selected proxy, which can help you compare the effect of routing rules. Direct connects typical requests directly and can help you test your local network. Actual behavior also depends on the system and current configuration, so the mode name alone doesn't tell you how all traffic is handled. When troubleshooting, change one setting at a time and retest the same destination. Before choosing Config, confirm that the intended configuration file is selected.

Stop the connection first and confirm that your local network can still reach pages that normally work. Then reconnect and check the selected server, Global Routing, and current configuration. If only some domains fail, check the relevant rules and DNS first. If all requests fail, check the server address, port, authentication, and service status. A latency test response only shows that a test received a response; it doesn't prove that web requests are completing successfully. Change one variable at a time, and look in Data or available logs for the failed destination and error details. Avoid changing rules and DNS together, or you won't know which change mattered.

Connectivity Test results don't measure the same thing as loading web pages or sustained data transfer, so don't treat the test value as available bandwidth. On the same device and with the same destination, compare your current Wi-Fi and cellular connections. Then check for changes in server load, network conditions, or protocol settings. If only one site is slow, check the routing rule and DNS result for that request instead of changing every server. Note the test time, network type, and symptoms to distinguish a brief fluctuation from an ongoing issue. Keep other settings unchanged when comparing results.

On Demand connects when its configured conditions are met, so the device may reconnect when those conditions apply again, even after you turn the connection off manually. To pause it, check and disable the relevant On Demand conditions, then stop the current connection and see whether it reconnects on your Wi-Fi or cellular network. Turning off the connection switch alone doesn't cancel its conditions. Also check whether device management policies affect the connection. When resuming use, enable and verify conditions one at a time so you can identify which one triggers the connection.

Check actual usage in Settings' battery statistics, taking screen time, signal strength, and data transfer into account. Don't assume battery drain is abnormal just because the app is running in the background. Heavy continuous traffic, retries on a weak signal, frequent disconnects and reconnects, and detailed logging left on for long periods can all increase processing load. Stop continuous tests you don't need, check whether On Demand is triggering repeatedly, and compare usage over the same period on the same network. Record the original settings before making changes. If connections are failing often, address the cause rather than turning off all rules for a superficial change.