Shadowrocket: How to Manage Multiple Subscriptions, Organize, Reorder, Delete, and Resolve Duplicate Nodes

Understand Subscriptions, Groups, and the Selected Node

Subscription groups in Home organize the nodes returned by each subscription; they are not rule policy groups. One subscription URL can return multiple nodes, and adding the same URL more than once can create multiple groups from the same source. When managing several subscriptions, check each group’s source before deleting anything by name.

Use Home to view nodes, choose a connection, and manage subscriptions; Config is for rule configurations, and Settings is for app preferences. Moving a group to the top of the list only changes how the list is organized. It does not automatically change the group used by rules in Config or mean that all requests will use it.

Individually imported nodes need to be identified separately. Importing a node’s share link again does not update the subscription it may belong to. A subscription URL and a single-node share link are different items; check the entry details rather than relying on its display name.

Create Clear Groups for Multiple Subscriptions in Home

Before organizing subscriptions, make sure you can retrieve their URLs again from your existing provider. A URL token often acts as an access credential, so don’t include the full URL in public screenshots, group chats, or support requests. The https://example.com/sub?token=xxxx shown here is a format example, not a working subscription.

1. Open Home and review the subscription groups one by one. Expand each group you want to check and confirm that its nodes match the expected source.
2. Open the subscription’s edit details from the group’s action menu. Long-press the group title to see the available actions; the edit option and its label may vary with the current app interface.
3. Check the subscription URL and its remarks. Note each subscription’s purpose, such as “Primary” or “Backup,” without putting tokens, passwords, or full URLs in the remarks.
4. If two groups appear to come from the same source, compare their full URLs and then check the node details. The same group name alone does not prove that they are duplicates.
5. After saving the remarks, return to Home and confirm that you edited the intended group, not another subscription.

Reorder the List Without Assuming Automatic Switching

The order of groups and the order of nodes within a group are separate. Reordering groups makes them easier to find; reordering nodes helps you choose one from the same source. Decide which level you want to move, then use the edit, sort, or drag controls available in the current interface. Drag only when a drag handle is shown; don’t mistake a regular long-press for a sorting action.

• Group level: Keep frequently used subscriptions somewhere easy to find. Collapse groups you aren’t using for now instead of deleting them right away.
• Node level: If you sort by name or latency, check whether the change applies to the current group or a wider scope.
• After an update: Check the order again. The order returned by a subscription and your local sorting are separate; don’t assume a manual order will always be preserved.
• Connection selection: After moving an item, check which one is marked as selected. The first item in the list is not necessarily the active connection.

A regular subscription group does not become a failover group just because it is at the top of the list. If your configuration uses policy groups and their selection behavior, check them separately in Config. When Global Routing is set to Config, also check which policy the rules actually match. A selected node in Home alone does not prove that every request goes through it.

Update Existing Subscriptions Instead of Adding the Same Source Again

Update the subscription that already exists in Home rather than importing the same URL again through the add flow. To refresh its nodes, use the target group’s action menu and check the result shown by the app. Update one group at a time: confirm that its contents look right before moving on, so you can tell whether an issue is specific to a source or your current network.

1. Before updating, note the group name, current node count, and selected node. These are reference points for this update, not fixed values to keep indefinitely.
2. Update that group once. If an error appears, keep the error details; don’t try to work around it by adding the same URL again.
3. After a successful update, expand the group and check whether its entries changed. A higher node count may reflect changes in the subscription, so count alone doesn’t prove there are duplicates.
4. Check whether the previously selected node is still there. If the source removed it, select an available node and test the connection again.

Settings → Subscribe is where you can review subscription-related settings. Before changing an update option, read the description in the current interface and confirm its scope. Automatic updates retrieve the source content again; they don’t determine whether two different URLs belong to the same account or automatically remove duplicates across subscriptions.

Identify Duplicate Nodes by Source and Connection Details

The same name doesn’t always mean a duplicate, and different names don’t always mean different nodes. Two nodes can share a server domain but use different ports, protocols, authentication, or transport settings. Conversely, their names may include different purpose notes even though all connection fields match. First determine whether the duplication is at the group level or the node level.

For example, edge.example.com:443 and edge.example.com:8443 use different ports, so don’t delete one just because the Address matches. Even when the address and port are the same, check authentication and related fields such as TLS and transport. Compare authentication details locally; don’t send full credentials to someone else to review.

An update reads the source again, so deleting a node locally isn’t a reliable way to keep it gone if the subscription continues to return it. If the current subscription settings provide filters, first confirm what they match and how they work. If you’re unsure, keep the original URL and any necessary notes, then test on a small scale.

Confirm the Cleanup Scope Before Deleting an Expired Subscription

Deleting a single node and deleting an entire subscription have different effects. Read the confirmation prompt carefully to see whether it applies to one entry or to a group and its associated nodes. A brief update failure doesn’t mean a subscription has expired. Check the URL, account status, and current network before deciding what to remove.

1. In Home, confirm the source and purpose of the group you plan to delete, and check whether it duplicates a subscription you intend to keep.
2. If the currently selected node belongs to that group, select a node from a group you plan to keep first. Disconnect before organizing if needed.
3. Delete the subscription from the target group’s action menu, and check the scope in the confirmation prompt. When deleting an individual node, make sure it doesn’t belong to a group you need to keep.
4. Return to Home to check the list, then review Config for any selections or configuration that depend on the deleted node’s name.
5. Reconnect and test access. Deleting a local subscription record does not cancel service with your provider or change your app purchase in the App Store.

Common Questions About Managing Multiple Subscriptions

After organizing, check in this order: identify each source, confirm duplicate groups, make sure the selected node is still available, verify that Global Routing and the configuration match your expectations, then test the connection. Keep subscription management separate from rule changes so you can pinpoint the cause if something goes wrong.