Shadowrocket Subscription Import Failed or Empty: Check the URL and Update Timing

First, distinguish an import failure from an empty list or connection failure

Subscribe retrieves content from a specified URL and adds recognized server configurations to the list. Saving a subscription entry doesn’t mean valid content was retrieved, and seeing a server in the list doesn’t guarantee it can connect. Identify which step failed before changing settings; this is more likely to preserve useful clues than repeatedly deleting the whole list.

• Can’t proceed when saving: Check that Type is set to Subscribe, the URL is complete, and you haven’t pasted a webpage title into the URL field.
• Update reports a failure: Check the network, DNS resolution, HTTPS certificate, and server response. Don’t start by changing the server’s port or protocol.
• Update finishes but the list is empty: Confirm that the response actually contains usable server configurations, and check whether the subscription group is collapsed or a list filter is enabled.
• Servers appear, but connections fail: Subscription parsing has already succeeded. Check the server parameters, availability, and connection logs instead.

Home shows servers and connection status, Config manages configuration files, and Settings contains app preferences. Don’t clear Config to fix a failed Subscribe request; they handle different things. This guide also doesn’t recommend changing Global Routing as a general fix, since the route used for subscription updates depends on relevant settings and the current network.

Check the Subscribe URL and preserve its original characters

A subscription URL usually contains a domain, path, and query parameters. A token in the query string acts as an access credential; even one missing character can result in a different request. Copy the URL directly from your provider’s subscription page. Don’t reconstruct it from a chat preview, a screenshot, or a truncated address bar.

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

The values above are fictitious and cannot be used to connect; they are shown only to illustrate the format. https:// is the access scheme, example.com is a sample domain, /sub is a sample path, and token=xxxx is a sample parameter. The path and parameter names in a real URL may differ. Use the exact URL provided by your provider; don’t adapt the example to construct a real link.

• Check for spaces, line breaks, Chinese quotation marks, or explanatory text at the beginning or end. Preserve the original capitalization and encoding within the URL.
• Don’t drop & from query parameters or manually decode percent-encoded values such as %2F; these characters may be part of credential validation.
• A regular sign-in page, account management page, and subscription endpoint are different URLs. Being able to open a webpage only confirms that the webpage is accessible.
• A single-server URI is also different from a Subscribe URL. Make sure you copied the subscription endpoint, not a share link for an individual server.

Use the request result to distinguish network issues from server issues

An HTTP error status and no response at all require different troubleshooting. The cards below list standard HTTP status phrases to help match diagnostic details with response records from your provider. Shadowrocket may use different wording; the exact English phrases don’t need to appear on screen. If there’s no status code, record the message the app actually shows rather than assuming the credentials have expired.

If the request times out, the domain can’t be resolved, or TLS validation fails, first confirm that your iPhone or iPad can access ordinary HTTPS sites on the current network. Then compare Wi-Fi and cellular data separately. Change only the network each time and note the result. For certificate errors, also check that the system date and time are correct; don’t bypass the issue by disabling certificate validation.

If the request succeeds but returns nothing, check the content—not just the status

HTTP 200 means the request succeeded at the HTTP level; it doesn’t guarantee that the response contains subscription data Shadowrocket can recognize. A sign-in page, expiration notice, or security verification page may also return 200. These are webpage contents, not server lists ready for import. A page opening in a browser isn’t enough to confirm that the subscription is working.

An expired account, changed permissions, server maintenance, or an unfinished subscription generation process could all affect the response, but an empty list alone can’t tell you which one applies. Check your account page and ask your provider how many valid configurations this URL should return right now. A plan name shown on the account page isn’t proof that a valid subscription has been generated.

Keep protocol names and subscription formats distinct. Shadowsocks, VMess, VLESS, Trojan, Hysteria2, and WireGuard are protocols or tunnel types used in connection configurations. Their names appearing in a text file doesn’t mean Subscribe can parse that file directly. Don’t rewrite encoded content or assemble protocol fields yourself. If you need to enter parameters manually, use the appropriate entry method and provide all required values.

Keep your existing configuration and re-import once, step by step

Re-importing can help verify whether the URL was copied incorrectly or the URL saved in an old entry has stopped working. It shouldn’t be the first thing you do after every failure. Before you begin, note the original subscription name and number of entries. Keep any working configuration, and don’t delete the entire Home list. Interface layouts can vary slightly; look for the same English labels to identify each action.

1. Record the current state

   In Home, check the original subscription group and note the visible server count and the result of its last update. Keep the original entry, and don’t change Config or server parameters while troubleshooting.

2. Copy the URL

   Copy the complete subscription URL again from your provider’s account page. If you’ve just reset the credentials, use the new URL and check whether the old one has expired.

3. Choose the type

   Go to Home → + in the top-right corner → Type → Subscribe. Return to the add screen, paste the link into the URL field, and use a recognizable note to distinguish this test from the original entry.

4. Save and update

   After saving, return to Home and pull down to update. Wait for the request to finish and note the actual message. Don’t pull down repeatedly while the request is still running. If you have multiple subscriptions, make a note of which one failed.

5. Check the list

   Expand the new subscription group and check whether servers appear and how many. Once the new entry works, you can clean up duplicates. If both old and new entries fail, keep the error record and investigate the network or server.

If the new URL imports successfully but the old one still fails, compare the saved URLs and credential status first. If both entries show servers but connections fail, stop troubleshooting the import and check the selected server separately. Don’t report a failed latency test as a Subscribe parsing failure.

Update timing and recording results

Updating a subscription requests fresh content from the server; it won’t restore expired account access or immediately lift a rate limit. After credentials are reset, permissions restored, or content changed, confirm that the update has taken effect on the server before running one manual update. Whether automatic updates are enabled and when they run depends on settings and system conditions. Don’t assume an update succeeded just because the app is open.

• Account status just changed: Ask your provider to confirm that the subscription content has been generated, then update once. Don’t assume that waiting a fixed number of minutes will always be enough.
• Just switched networks: Wait for the connection to come up before trying again. Record the results on Wi-Fi and cellular separately. Avoid changing both the URL and network at once, so you can compare results.
• Rate limit reached: Stop retrying frequently. Follow Retry-After or the waiting instructions from your provider.
• Fewer entries after an update: First check whether the server changed the returned entries before deciding whether to keep the old records. Don’t immediately assume the app lost data.

What to include when reporting an issue

A useful report should make the steps reproducible while protecting your access credentials. Tell your provider when the issue occurred, which network you used, which import path you followed, how many entries there were before and after the update, and the exact error message. If a record includes the full URL, redact the token, account identifier, and other authorization parameters. Don’t send subscription content, server passwords, or QR codes.

Path: Home → + → Type → Subscribe
Action: Save, return to Home, and pull down once to update
Result: The original entry is still there, but the new subscription group has no servers
Compare: Record the update result on Wi-Fi and cellular separately
Error: Copy the actual message shown; don’t guess the status code from what happened
Privacy: Redact URL credentials and account details from your report

Wrap up by checking the three stages: if the request didn’t complete, investigate the network and endpoint; if it completed but returned no valid entries, check the response content and account status; if entries appeared but can’t connect, check the server configuration and connection process. Work on one stage at a time to avoid deleting useful configurations and make any follow-up report more specific.