Shadowrocket Subscription Not Importing or Showing No Nodes: Check the URL, Provider Status, and Update Timing

If a subscription fails to parse or shows no nodes, check the URL and encoding, confirm your provider account is active, then review update timing and network access.

At a Glance

This guide is for Shadowrocket users who already have a subscription from their own provider. First, identify whether the request failed, the response could not be parsed, or the response contained an empty list. Then check the URL, account status, and network used for the update. Change one condition at a time and keep any records that still work; don’t delete all your configurations before you know the cause.

Subscription Updates and Node Connections Are Separate

A subscription URL retrieves a server list; the nodes in that list are used to establish proxy connections. These involve two separate network requests. A node that temporarily won’t connect doesn’t mean the subscription URL has expired, and a failed subscription update doesn’t necessarily mean existing nodes are unusable. First identify which step is failing.

Read URL Request subscription Parse response Build list Test connection

Check the subscription group and whether it’s expanded on Home. If the group is already there but collapsed, expand it before checking for entries. If the update finishes but the group still has no entries, note the message shown. If entries are present but connections time out, troubleshoot node settings and network access separately—don’t conflate the two issues.

3 items
Troubleshooting order: URL, account, update network
443
Default destination port when HTTPS has no port specified
1 item
Change one troubleshooting condition at a time

The default HTTPS port is not the node’s port. If the subscription URL explicitly includes another port, keep the value provided by your service provider. Don’t change the port in the subscription URL just to match a port used by a node.

Step 1: Check the URL Type and Make Sure It Was Copied Correctly

The subscription field requires a subscription URL from your service provider—not an account login page, plan page, or explanatory text from a website. A page that opens in a browser may not be parseable as a subscription. Copy the URL from your provider account that’s specifically designated for use with Shadowrocket.

  1. Copy the Original URL

    Copy the subscription URL again from your own provider account. Don’t use text recognized from a chat screenshot or copy a whole block of text that includes instructions such as “tap to import.”

  2. Check the URL Boundaries

    Make sure the protocol at the beginning is intact and there’s no period, quotation mark, or line break at the end. There must be no spaces within the URL either. A long URL wrapping on screen doesn’t mean it contains an actual line break.

  3. Add It as a Subscription

    Go to Home → “+” in the upper-right corner → Type → Subscribe, paste the address into the URL field, then save. Don’t enter the entire subscription URL in a server field meant for a single-node protocol.

  4. Update and Note the Result

    Return to Home, pull down to refresh, and wait for the update to finish. Note the message and number of entries. Don’t add the same subscription repeatedly, or it may be unclear which group you’re checking.

The examples below use dummy values to show the URL structure; they are not usable subscriptions. Actual URLs may have different paths and parameter names. Don’t rewrite your own URL based on these examples.

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

Step 2: Check Your Provider’s Status and the Actual Response

Even a complete URL may fail to import. Your provider may revoke an old token, suspend your account, change its subscription API, or return an empty list when no nodes are available for your account. Repeatedly changing protocol settings in Shadowrocket won’t change what the server returns.

Sign in to your provider account and check whether the subscription is active, whether any nodes are available, and whether the URL was recently reset. If your provider offers multiple export formats, choose the one explicitly intended for Shadowrocket. The file extension isn’t what determines whether it can be parsed; the response content does.

What You See What It Means Next Step
A login or verification page is returned You received a web page, not a node list Check that you’re using the subscription-specific URL, and ask your provider whether the endpoint requires web-based verification
HTTP 200, but the response body is empty A successful request doesn’t mean there are entries to import Check whether your account has nodes available and whether the provider’s API is working
HTTP 200, but the response body contains an error message The server returned an application-level error with a success status Use the response body to check the token, account status, or export format
Some entries appear, but others are missing The format and supported parameters of the missing entries may need checking Ask your provider to check the specific entries; don’t assume the entire subscription is invalid

Bottom line: Make sure the response contains a list

If the response is a login page, an error message, or an empty body, resolve the subscription endpoint issue first. Switching node protocols, changing rules, or changing a node’s port won’t restore a missing list.

Only inspect the response on a trusted device if you need to tell a web page from subscription content. Browsers may retain history and downloads, and browser login cookies differ from requests made by the app. So, “it opens in my browser” is a clue, not proof that the app can retrieve the same content.

Narrow Down the Issue by HTTP Status Code

These are standard HTTP status codes you may encounter when requesting a subscription; Shadowrocket may not display this exact wording on every platform. If the app only says the update failed, give your provider the time it happened and ask them to check their request logs. A status code can help guide troubleshooting, but it isn’t conclusive proof of an account issue.

HTTP 401 Unauthorized

Cause and fix: The server rejected the credentials sent with the request. Copy the currently valid subscription URL from your account, and ask your provider whether the token has been revoked.

HTTP 403 Forbidden

Cause and fix: The server rejected the request, possibly due to account permissions, source restrictions, or security rules. Check your account status and ask your provider why the request was denied; don’t assume it’s a client parsing issue.

HTTP 404 Not Found

Cause and fix: The requested path doesn’t exist, or the server uses this status to hide an invalid resource. Check that you copied the full path and ask your provider whether the subscription URL has changed.

HTTP 429 Too Many Requests

Cause and fix: The request rate triggered a limit. Stop refreshing repeatedly; if the response includes a Retry-After value, wait for the specified time before trying again.

HTTP 5xx errors usually point to a server-side or upstream issue. DNS lookup failures, connection timeouts, and TLS certificate errors can occur before an HTTP response is received, so they’re different from the status codes above. If you encounter a certificate error, check your device’s date and time first, then ask your provider to verify the certificate. Don’t hide the error by disabling certificate validation.

Step 3: Check Update Timing and Network Access

Your device needs to reach the subscription domain to update a subscription. If the current proxy node is no longer working and the request goes through that proxy, you can end up needing to update the nodes but being unable to complete the update. Conversely, some subscription domains aren’t reachable over your current direct connection, so turning off the proxy may not help. Change one condition at a time to find out what’s happening.

  1. Keep a Record of the Current Settings

    Note the current network, connection toggle, and Global Routing setting. Record only your own node names and counts; don’t show the full URL in public screenshots.

  2. Make Sure the Network Is Working

    Check whether Wi-Fi requires web-based sign-in or whether mobile data is working. A device connected to Wi-Fi isn’t necessarily connected to the internet.

  3. Check Automatic Connection

    Go to Settings → On Demand, note the current settings, then temporarily turn off the relevant On Demand options. Disconnect the current proxy and try updating once to prevent an automatic reconnection during the test.

  4. Try a Different Network

    If possible, switch from Wi-Fi to mobile data only, keep the subscription URL unchanged, and try updating again. If it fails on just one network, check that network’s DNS, sign-in requirements, or access restrictions first.

  5. Restore the Original Settings

    After recording the results, restore any On Demand settings and routing state you need. If only a working proxy path you already have can reach the subscription domain, tell your provider.

Config, Proxy, Direct, and Scene under Global Routing are routing choices, not subscription format converters. The actual path used for the app’s update request may also depend on related settings; a routing mode’s name alone doesn’t tell you which route the request will take.

Still No Entries After Updating? Keep the Details Before Troubleshooting Further

If a newly copied URL returns no entries on either of two networks, check the endpoint and your account with your provider next, rather than repeatedly deleting the app. Removing the group or reinstalling adds work to restore existing records and won’t fix an empty server response, an invalid token, or access restrictions.

If the update succeeds and nodes appear, but a node connection then fails, the subscription import is complete. Check that node’s address, port, protocol, and transport settings instead. Don’t keep using the “empty subscription” troubleshooting steps for a connection problem.

Bottom Line: Let One-Variable Tests Guide Your Next Step

If a new URL works, check the old token. If switching networks fixes the issue, check the network path. If both networks return empty content, ask your provider to check your account and subscription endpoint. Once entries appear, move on to troubleshooting node connections.

This guide assumes you already have your own provider and subscription. This site doesn’t provide, sell, or recommend nodes or subscriptions. The app and your provider’s service are billed separately; getting Shadowrocket doesn’t include a service plan.

Download Shadowrocket