Shadowrocket Subscription Update Guide: Manual Refresh, Auto-Update on Launch & Troubleshooting

Learn how to refresh a Shadowrocket subscription manually, update it on launch, or set an interval—and troubleshoot failed updates caused by invalid links, network issues, or unsupported formats.

At a Glance

This guide is for users who already have a subscription from their own provider. Start by refreshing it manually in Home to confirm the link can be reached and parsed, then configure updates on launch or at an interval. If an update fails, check the request URL, network path, and response content in that order. The steps use the iPhone / iPad interface as an example. On Mac, Windows, Android, and Linux, check the settings available on your platform rather than assuming mobile background behavior applies to desktop.

What a Subscription Update Changes: Check the Server List and Config Separately

A Shadowrocket subscription update requests an existing subscription URL again and parses the response into server entries. When your provider changes a server address, port, credentials, or the list of entries, you need to update the subscription to get those changes. This does not repurchase the app or renew a service plan. This site does not provide, sell, or recommend servers or subscriptions.

First, distinguish server subscriptions in Home from rule configurations in Config. Updating the server list does not update the rules in the current Config file, nor does it guarantee that the selected server will connect again immediately. An update may help if the problem is an expired credential or invalid address. If the cause is a local rule, network restriction, or incorrect system time, continue troubleshooting.

Read the subscription URL Send a network request Receive the response Parse the servers Check the list

Before importing, confirm the URL comes from your own provider account and keep your existing working configuration. The example https://example.com/sub?token=xxxx illustrates a URL format only; it is not a working subscription. The token in the query string usually acts as an access credential. When troubleshooting, never include the full URL in a public screenshot or log.

Manual Pull-to-Refresh: Start with a Repeatable Check

Before enabling automatic updates, refresh the subscription manually once. This helps you distinguish an unusable link from an automatic trigger that did not run. Automatic updates use the same subscription URL and cannot work around an invalid URL, failed authentication, or malformed content.

  1. Find the right group in Home. Check the subscription name against the existing servers, and distinguish the subscription group from entries added manually. Note the current number of entries in the group. If you have multiple subscriptions, make sure you do not mistake changes to another group for the result of this update.
  2. Pull down to refresh the list. In Home, pull down from the top of the list and release, then wait for the refresh to finish. If there are multiple groups, check which ones were refreshed and their individual results. Avoid repeated pulls so you can tell requests apart.
  3. Check the result. Look for an error, then check whether the entries, addresses, or ports in the target group match changes announced by your provider. An unchanged list does not necessarily mean the update failed; the remote content may simply be unchanged.
  4. Test the connection separately. Select an existing server and run Connectivity Test, then try the destination you need to reach. A successful subscription refresh only confirms that the content was fetched and parsed; it does not mean every server is reachable from your current network.

Auto-Update on Launch and Scheduled Updates: Configure the Trigger

On platforms that offer the relevant options, go to Settings → Subscribe and check options such as updating on launch, the auto-update interval, and Update via Proxy. Options may be arranged differently across platforms and interface versions, so use the switches and interval choices shown on your device. Do not try to reproduce an unavailable option by adding configuration fields yourself.

Update Method Trigger and Purpose What to Check
Manual pull-to-refresh Refresh the list in Home yourself; useful for an initial check or retesting after a problem. Did the refresh finish? Was there an error? Did the target group change?
Auto-update on launch Attempts an update when you open the app, as configured; useful for picking up changes during everyday use. Is the option enabled? Is the device online when you open the app? Is the update interval limiting the attempt?
Scheduled update Attempts updates at an interval supported by the app; useful for reducing manual refreshes. Does your device offer an interval setting, and does the app get a chance to run?

After enabling updates on launch, leave the settings screen and check the result the next time you open the app normally. Switching briefly between the foreground and background does not guarantee an update, and an unchanged list alone does not mean the setting failed. A more reliable check is the update result shown in the app, along with entries your provider has actually changed.

A scheduled update is not a system alarm. On iPhone / iPad in particular, background activity depends on system scheduling, power-saving conditions, and network availability. An interval shown in the app does not guarantee an update at an exact time while the device is locked. Do not expect the app to keep running background tasks in the same way after you force-quit it. If you need changes right away, open Home and refresh manually to verify the result.

3 methods
This guide covers manual, on-launch, and scheduled updates
2 layers
Settings → Subscribe: subscription settings on mobile
443
Default port when no port is specified for HTTPS

Takeaway: Verify Automatic Updates After a Successful Manual Refresh

Keep the same subscription and network, complete one successful manual update, and then change only the automatic-update setting. If it fails afterward, you can check the trigger conditions first instead of questioning the link, network, and parsing format all at once.

Update via Proxy and Global Routing: Change One Network Condition at a Time

Being able to reach a subscription URL and being able to connect to a server are two separate things. Some URLs are accessible directly on your current network; others require an already working proxy route. Update via Proxy in Settings → Subscribe controls whether subscription updates use a proxy. Before enabling it, make sure an existing selected server can connect.

Proxy, Direct, Config, and Scene in Home → Global Routing are routing modes, not subscription update intervals. Direct connects without a proxy; Proxy routes traffic through a proxy; Config follows the selected configuration; Scene follows the scene settings. Before troubleshooting, note the current mode and selection. Do not leave the routing mode for all connections changed just to refresh a subscription.

  1. First, try a manual update on your current network. Note whether it times out, returns an unusual HTTP status, or fails to parse the content.
  2. If direct access fails but an existing proxy connection works, check Update via Proxy and retry the same subscription.
  3. If enabling the proxy makes the update fail, restore the previous setting, check whether the current server is working, or retry with another existing server you can connect to.
  4. Change only one network condition or setting at a time. If testing on Wi-Fi and cellular, record each result separately and keep the subscription URL unchanged.

Shadowrocket Subscription Update Failed: Distinguish Request Errors from Parsing Errors

Keep the exact error message before deciding what to try next. The examples below cover common network- and HTTP-level messages. The wording shown by Shadowrocket can vary by operating system and platform. An HTTP status code reports the server’s response; it does not identify a single cause. For example, a 403 alone does not prove that a link has expired.

Error: The request timed out.

Cause and fix: The request did not finish before the timeout. Your current network may not be able to reach the subscription server, or the server may be responding slowly. Try again on Wi-Fi or cellular, then check Update via Proxy if you have a working proxy connection.

Error: A server with the specified hostname could not be found.

Cause and fix: The subscription hostname could not be resolved. The URL may contain a typo, the domain may no longer work, or DNS resolution may be failing on your current network. Copy the full URL again from your own provider account, check the domain, and try another network. Do not replace the domain with an IP address, which can break HTTPS verification.

Error: HTTP 401 / HTTP 403

Cause and fix: The request was not authenticated or was denied; an access policy may also be restricting it. Check whether the token was reset, whether the full URL was copied, and whether your account has access. Use the current URL provided by your provider; do not try to fix the problem by guessing or changing the token.

Error: HTTP 404

Cause and fix: The resource at the requested path was not found. This can happen if an old endpoint has been disabled or the URL path was truncated. Check the full path and query parameters, make sure you copied the subscription URL rather than an account webpage, and try a manual update again.

The Response Arrives, but Cannot Be Parsed

Even a successful HTTP request can return the wrong content. For example, the subscription endpoint may redirect to a login page, a verification page, or an account notice. These pages may load normally, but they are not the server data Shadowrocket expects. Changing the update interval will not help. Check that the URL uses a subscription format supported by the app and that your provider is returning the expected content.

After an Update: Check the List, Data Usage, and Connection Separately

The refresh succeeded. Why is the server count unchanged?

The remote content may not have changed, or an existing entry may have changed address or parameters without affecting the count. First check whether your provider has actually made changes, then inspect the relevant entries. Do not judge success by the count alone or delete the subscription just to make the list look different.

Auto-update on launch is enabled. Why didn’t it refresh on time while the device was locked?

Updating on launch and scheduled background updates use different triggers. Go to Settings → Subscribe to check the auto-update options and interval available on your device, then open Home and test manually. Mobile background scheduling is not an exact alarm.

Does updating a subscription reset data usage or renew the service?

No. An update only fetches the content again. Your provider manages your service account’s data allowance and expiration date. If the list shows an allowance, check its actual status in your provider account; refreshing does not add data or renew the service.

The update succeeded. Why can’t I open a webpage?

Run Connectivity Test on the selected server in Home, then check Global Routing and the current Config. If the test succeeds but a particular destination does not, check the matching rules and whether the destination is reachable. Repeatedly updating the subscription is not a substitute for troubleshooting the connection.

Do I need to copy my phone’s auto-update settings when I switch to Mac?

Do not assume settings are identical across platforms. On Mac, check the imported subscription and complete a manual update first. Configure auto-update and background behavior using the options actually available in the Mac interface. Follow the same verification steps on other desktop and mobile platforms.

Keep a brief troubleshooting record: which redacted subscription you used, which network you updated on, whether the request went through a proxy, the exact error, and whether the list changed. First confirm whether the request succeeded, then whether the data could be parsed, and finally whether the servers connect. Working through these three layers is more likely to reveal the cause than changing DNS, Global Routing, and the auto-update interval all at once.

Download Shadowrocket