Shadowrocket Subscription Import Failed or No Servers? Check the URL and Update Timing

If a subscription fails to parse or the list is empty, check the URL, provider status, update timing, and network, then re-import it correctly.

At a glance

This guide is for users who already have a provider and subscription URL. First, distinguish a download failure from content that cannot be parsed or a parsed list with no available entries. Then check the URL, account status, update timing, and network path. Keep the original subscription and existing connections while troubleshooting. Replace them only after confirming the new URL returns a valid list, so you don't lose your only working connection.

First, identify the issue: request failure, parse failure, or a hidden list

Updating a Shadowrocket subscription involves several steps. The app accesses the subscription URL, the server returns content, and the app parses it into entries shown in Home. A failure at any step can look like “no servers after import,” but each issue needs a different fix. An enabled connection alone does not prove that the subscription URL is reachable.

Read the URL Request the server Receive content Parse entries Show the list

Go to Home, clear any search filters, and expand the relevant subscription group. If the entries are there but a connection test fails, check the connection settings and server status instead of repeatedly deleting the subscription. If the list is truly empty, check the update message to see whether no content was received or the content could not be parsed.

Step 1: Check that the URL is complete and the right type

Get the subscription URL from your provider. Use an address the provider specifically identifies as a Shadowrocket subscription URL, not a URL for the account portal, plan details, or a webpage shown after signing in through a browser. The example below uses fictitious values to illustrate URL components; it is not a working subscription.

https://example.com/sub?token=xxxx

Here, https:// is the protocol, example.com is the domain, /sub is the path, and token=xxxx is a query parameter. Real URLs may use different paths and parameter names; don't edit yours to match this example. In particular, don't remove anything after the question mark or enter the subscription URL as a server's Address or Port.

  1. Copy the full subscription URL again from your provider's page. Check that there are no spaces, line breaks, quotation marks, or non-ASCII punctuation at either end.
  2. Check whether & was copied as the literal text &, which may change the meaning of the parameters. Copy the original URL again rather than replacing text blindly.
  3. If the link you received is a single server share URL starting with ss://, vmess://, or vless://, treat it as an individual server entry, not an HTTPS subscription URL.
  4. In Home, choose the subscription type under Add Server. The subscription type is usually shown as Subscribe. Paste the URL into the URL field, save it, then update that subscription.

Step 2: Confirm the provider returns subscription content

A subscription URL opening in a browser doesn't mean it returns content the app can parse. The browser may show a login page, verification page, or message; the app needs subscription content in a supported format. Even an HTTP 200 response can fail to parse if its body is an HTML page. Don't rule out a server-side issue just because the page opens.

200
A successful HTTP request doesn't guarantee a valid subscription in the response body
401 / 403
Check that your credentials are valid and review the server's access policy
429
If requests are rate-limited, stop retrying repeatedly

If an update message or diagnostic log includes one of the following HTTP status lines, use it to guide your troubleshooting. These are standard responses a server may return; not every platform displays the exact same error text.

HTTP 401 Unauthorized

Cause and fix: The server didn't accept the current credentials. Check your subscription access on your provider's page, then copy the currently valid URL again. Don't keep using a token that has been reset.

HTTP 403 Forbidden

Cause and fix: The server rejected the request, possibly because of an access policy or verification requirement. Note when it happened and which network you were using, then ask your provider about the restrictions. Repeated retries won't reveal the cause.

HTTP 429 Too Many Requests

Cause and fix: The request hit a rate limit. Stop triggering manual updates. If the response includes Retry-After, wait for the specified interval; otherwise, follow your provider's guidance for the next update.

An empty list can also mean that account permissions haven't taken effect, the provider removed all available entries, or you selected an incompatible subscription format. Check your account status and available entries on your provider's page, then confirm which format to copy. Shadowsocks, VMess, VLESS, Trojan, Hysteria2, and WireGuard use different fields. Changing Type to a different name won't convert the content to another protocol.

Bottom line: Check the response content before changing client settings

If the same URL returns a login page, an error message, or an empty list, address the server-side issue first. Changing Global Routing or the connection port can't turn that content into a valid subscription.

Step 3: Choose when to update based on the account status

After a subscription URL is reset, account permissions change, or a provider updates its list, the old URL or content may no longer work. Before updating, make sure the provider's page shows the expected status, then copy the new URL. Don't assume a purchase, renewal, or reset requires reinstalling the app while waiting for the change to take effect.

  1. First import: After saving the entry, update the subscription once and check whether a server list appears. The subscription name appearing is not enough.
  2. After resetting the URL: Edit the original subscription's URL or add a clearly labeled test subscription, using the complete new URL. Refreshing won't restore an old token.
  3. After a permissions change: Check whether the change has taken effect on your provider's page. If the list is still empty, follow the provider's guidance on how long to wait; there is no universal activation time.
  4. Automatic update didn't run: Go to Home and update manually once, then note the result. Background activity depends on system scheduling and network conditions, so automatic updates aren't guaranteed to run at a fixed time.

Change one condition at a time and record which URL and network you used, whether the connection was enabled, and what message appeared. This helps separate changes caused by replacing the URL from those caused by switching networks. Repeatedly tapping Update makes troubleshooting harder and may trigger rate limits.

Step 4: Test subscription requests separately from proxy connections

The subscription server and proxy servers may use different domains, ports, and access paths. An existing entry connecting successfully doesn't prove the subscription domain is reachable. Likewise, a successful subscription update doesn't mean every returned entry works. First establish whether the list downloads, then test connections.

Proxy, Direct, Config, and Scene under Home → Global Routing are routing modes, not subscription formats. Config relies on the current configuration rules, while Scene relies on the behavior set for that scene. Settings → On Demand manages condition-based connections; it won't fix an incorrect URL, expired token, or empty response. Note the original settings while troubleshooting and restore the required state afterward.

Re-import: Verify the new entry before removing the old one

Re-importing can help rule out an old URL, a mistakenly selected type, or an entry that wasn't saved correctly. It isn't a universal fix for subscription issues. Deleting a subscription may also remove its server entries. If they're still used for your current connection, keep them until troubleshooting is complete so you don't lose access.

  1. Note the original subscription name and any essential settings, and keep your valid URL somewhere safe. Don't store backups containing credentials in a public location.
  2. Get the correct URL from your provider. In Home → Add Server, select Subscribe and enter the full address in URL.
  3. Use a label that differs from the old entry, such as “Subscription check.” Save it, then update the subscription.
  4. Expand the new group and confirm that the expected server entries appear. Then check their protocol types and the ports provided by your provider. Don't assume that port 443, often used for HTTPS subscriptions, applies to every proxy server.
  5. Test the connection using one entry and confirm that access works as expected. Only then remove duplicate or inactive subscriptions, keeping any Config and policy references you still need.

If the old and new subscriptions use the same URL and both return an empty list on the same network, adding another copy usually won't help. Note the response message, test time, network type, and whether you reset the URL, then contact your provider. Hide tokens, UUIDs, passwords, and other credentials before sharing screenshots.

Common questions about empty subscriptions and update failures

Why does the subscription open in a browser but still fail to import?

Check whether the page shows subscription content or a login, verification, or error page. The app may not be able to reuse the browser's existing login session. Copy the Shadowrocket subscription URL from your provider's page, not the account portal URL.

The update succeeded, but there are no servers. Should I delete the app and reinstall it?

First clear the search filter in Home, expand the subscription group, and check whether your provider account has any entries available. Verify the URL and response before adding a test subscription. Reinstalling won't change an empty response from the server and may erase local configuration.

My servers are still there, but subscription updates keep failing. Can I keep using the old servers?

Whether existing entries still work depends on whether the server and authentication details remain valid. A failed update doesn't mean they stop working immediately. Keep the old entries and test the connection while troubleshooting the subscription URL separately; don't clear the list yet.

Will changing Global Routing to Proxy guarantee that the subscription updates?

Not necessarily. It also depends on whether you have a working connection and which path subscription updates use. Compare the results with the same URL and the connection on and off. Changing the routing mode won't fix an invalid token, incorrect response content, or an empty list from the server.

Download Shadowrocket