Shadowrocket Subscription Update Failed or No Nodes: Troubleshooting Guide

1. Tell an Update Failure from an Empty Node List

A subscription update has three steps: reaching the subscription URL, receiving a response, and parsing that response into nodes. A failure at any step can leave the expected nodes missing from Home, but each calls for a different fix. If old nodes are still listed and a refresh returns an error, first check whether the request succeeded. If no nodes appear after the first import, also verify that the response actually contains a node subscription.

An “update successful” message does not mean the nodes can connect. It means the subscription request and parsing completed; connectivity also depends on the node address, port, authentication parameters, and current network. This guide focuses on restoring the list. Once it is back, test the connection separately.

2. Check the URL and Subscription Type

A subscription URL retrieves a node list; it is not an account login page or the provider's homepage. Copy it using the subscription option in your own provider account, then check the scheme, domain, path, and query parameters after the question mark. Line breaks, trailing periods, quotation marks, or truncated links in chat apps can turn a URL that looks right into a different address.

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

The example above illustrates a format only; it is not a working subscription. Actual URLs may use different paths or parameter names, so don't edit yours to match the example. In particular, don't remove anything after ? or manually replace &, =, or percent-encoded characters. Subscription credentials may be part of the path and may not be named token.

1. Copy the URL again

   Copy the Shadowrocket subscription URL from your own provider account. If there are multiple format options, choose the one the provider recommends for Shadowrocket. Don't copy the account management page URL.

2. Check the subscription type

   Tap “+” in the upper-right corner of Home to open the add screen, then set Type to Subscribe. A single node's share link is different from a subscription URL containing multiple nodes. Don't enter a webpage address as a server address for a protocol.

3. Check the URL field

   Paste the full URL into URL and check for spaces, line breaks, or extra punctuation at either end. You can set a name that's easy to recognize, but don't put the full credentials in it.

4. Save and refresh

   After saving, return to Home and update the subscription. If you pull to refresh, check the result for the intended subscription, then look for nodes in its group. While troubleshooting, change only this subscription to avoid affecting other sources.

3. Check Provider Status Based on the Response

If the error message includes an HTTP status code, use it to narrow down the cause. The codes below describe standard server responses; not every version displays the same full error text. If the app shows only a generic failure, note the exact message and ask your provider what happened with the request.

Also check whether your account is active, your data allowance is exhausted, or your current plan includes any available nodes. Providers may respond with an error code, a message, or an empty list; don't assume they'll all report problems the same way. If opening the URL in a browser shows a login page, security check, or account notice, an HTTP 200 response still doesn't mean the content can be parsed as nodes. And what you see in a browser isn't necessarily the same response the app receives.

• Empty response body: Check whether the subscription endpoint is temporarily unavailable and whether nodes are assigned to your account.
• HTML page returned: Make sure you copied the subscription endpoint, not a webpage that requires an interactive login.
• Readable text returned, but parsing fails: Ask your provider to confirm the output format is compatible with Shadowrocket. Don't mix incompatible configuration formats.

4. For Timeouts, Check the Request Route Before the Timing

A timeout means the request did not finish within the allotted time; it does not prove the URL has expired. First check that your current Wi-Fi or mobile network can access other websites. If you're on public Wi-Fi, complete its network sign-in first. Trying the same subscription once on another network can help distinguish a local network restriction from a subscription server issue.

Subscription requests don't necessarily follow the same route as node tests. In Settings → Subscribe, Update via Proxy determines whether subscription updates are sent through a proxy. This may help with direct-access restrictions only if a working node already exists, a connection is established, and the request can reach the subscription endpoint. If this is your first import and the list is completely empty, you can't rely on a node that doesn't exist yet to update the subscription.

If the connection toggle turns itself back on soon after you switch it off, check Settings → On Demand for automatic connection conditions. It controls when a connection starts; it cannot turn an incorrect URL into a valid subscription. Note the original settings and temporarily turn this off only if you need fixed test conditions. Restore it afterward. Don't keep switching Global Routing at random, either: Proxy, Direct, Config, and Scene control how traffic is handled; they don't convert subscription formats.

5. If the Node List Is Empty, Check the Group and Response

After refreshing, return to Home and make sure you're viewing the group for the subscription you just updated. Expand collapsed groups and clear any search filters. A collapsed group or uncleared search can hide nodes without the subscription actually returning zero. If other subscriptions work and only one group is empty, focus on that source rather than resetting every subscription.

• Group exists but is empty: Ask your provider to confirm the response actually includes nodes, not just data usage details, an expiration notice, or an empty body.
• Some nodes appear, others are missing: Check the subscription's filters, the provider's output, and whether the missing entries use a supported format.
• Nodes appear but won't connect: The list retrieval issue is separate from the connection problem. Next, check the address, port, and authentication parameters for the relevant protocol.
• Fewer nodes appear after a refresh: Check whether the provider changed the node list. A smaller list does not automatically mean the client failed to parse it.

6. What to Keep Before Importing Again

Importing again can replace an outdated URL or fix an incorrect local entry, but it won't fix a provider endpoint issue. Before deleting an old subscription, make sure you can retrieve the full URL again and note any manually added nodes, existing group names, and the currently selected node. If the subscription still has working nodes, keep the original entry if possible so you don't remove a connection that still works.

1. Save the error details: Note the exact message, when it occurred, which network you used, and whether the update went through a proxy. “It doesn't work” isn't enough detail.
2. Confirm the current URL: Copy it again from your provider account. Don't reuse an old link saved in a chat history.
3. Check the account output: Confirm the account is active, the endpoint is working, and the URL should return at least one usable node.
4. Test the new entry separately: If you need to add it again, go to Home → “+” → Type → Subscribe, use a distinct name, and test the update once.
5. Clean up after testing: Delete an old subscription only after the new entry shows nodes and the connection test works as expected. Don't delete entries in bulk just because they have the same name.

If the issue persists, share these details with your provider and clarify whether the problem is a “request timeout,” an “HTTP error,” or a “successful request with an empty list.” These details are more useful for initial diagnosis than a screenshot containing the full URL. If credentials need to be changed, use your provider's secure support channel.

7. Frequently Asked Questions