v2rayN Subscription Groups and Server Filtering: Manage Multiple Subscriptions

Create one group per subscription URL. Verify that each group updates on its own, then set filters and update intervals based on node remarks. This keeps fetch failures, unmatched rules, and unavailable nodes easier to troubleshoot.

At a glance

This guide is for v2rayN desktop users with two or more subscription URLs who want to manage each source separately. Groups let you refresh, adjust update intervals, or disable sources independently. The examples use primary and backup groups to verify imports, filter node remarks with regular expressions, and explain why deleted entries may reappear.

Create a Group for Each Subscription

Group names identify the source; they don't filter nodes. For example, name your groups “Primary” and “Backup.” Even if both publish a node named “Hong Kong 01,” you can check each source separately. These steps use the Chinese interface in v2rayN 7.x desktop; some builds may show buttons as icons.

  1. Open Group Settings

    In the main window, select “Subscription Group” → “Subscription Group Settings,” then click “Add” or the plus sign in the group list. Add just one source to start, so you can confirm that its URL and update results match.

  2. Add the First Source

    Enter a recognizable group remark, paste the full subscription URL into the address field, and make sure “Enable updates” is on. Leave the filter field blank for the first update. Subscription URLs may contain access tokens, so hide the full URL before sharing screenshots or logs.

  3. Update the Current Group

    Return to the main window, select the new group, then choose “Subscription Group” → “Update current subscription (without proxy).” Use this option when the subscription URL is directly accessible. Check the update output, then confirm the current group contains the expected node remarks.

  4. Add a Backup Group

    Use the same steps to add the backup source; don't replace the URL in your primary group. Switch to the backup group and update it separately. Once both groups have updated successfully, you can use “Update all subscriptions” for routine refreshes.

Filter Servers by Node Remark

Search in the main window to find entries temporarily. The filter field in group settings filters imported results when a subscription updates. It matches node remarks, not the nodes’ actual exit locations. Check the source’s unfiltered naming first, then write your rule. For example, if you’ve confirmed that the source uses “Hong Kong 01” and “HK-02,” start with this rule to keep those entries:

^(Hong Kong|HK)[ _-]

Filter by a Fixed Prefix

Recommended

Once you’ve confirmed the naming is consistent, anchor the match to the beginning and require a separator. This reduces accidental matches on announcements or other remarks that happen to contain the same keyword.

Best for: Consistently named nodes when you want updates to keep the same set of entries.

Keep Everything and Search Temporarily

Leave the group filter blank and search remarks in the main window. Clear the search to see the full list. There’s no need to change subscription rules or update again just to find a node.

Best for: Newly imported sources, frequently changing names, or finding a specific node temporarily.

If the List Suddenly Goes Empty, Clear the Filter

If the group is empty after an update, first clear the search in the main window. If it’s still empty, clear the group’s filter and update again. If the URL imports entries without a rule, adjust the rule to match the new remarks; you don't need to recreate the group.

Set an Automatic Update Interval for Each Group

After verifying a manual update for a group, go to “Subscription Group” → “Subscription Group Settings” and set that group’s automatic update interval. Enter the interval in minutes. These examples are conversions, not client defaults. Check the source’s refresh recommendations before choosing an interval.

720 minutes
12 hours, example for the primary group
1440 minutes
24 hours, example for the backup group
0 minutes
No scheduled updates

Remove Outdated Entries: First Check Their Source

Manually deleting an entry only removes it from the current list. If the source still publishes the node and it matches the group filter, it may return on the next update. Likewise, a node with the same name in two groups isn't necessarily a duplicate. Before cleanup, select a group and confirm the source and the node you currently use to avoid deleting a backup configuration by mistake.

Common Questions About Updating Multiple Subscriptions

Why does one group keep timing out when another updates successfully?

Select the group with the error, run “Update current subscription (without proxy)” on its own, and check the output. If the URL requires a proxy, select a verified working node first, then run “Update current subscription (through proxy).” If the output says authorization is required or the URL is no longer valid, use a valid URL instead of repeatedly switching update methods.

Both groups have a “Hong Kong 01.” Should I delete one?

Open each entry’s edit window and compare its server address, port, protocol, and other settings. Matching remarks don't mean the configurations are identical. To see which one works better, test both the same way; don't compare results from different test methods directly.

Can I edit a group if its source has changed the subscription URL?

If the new URL replaces the old one for the same source, edit the existing group, save, and update only that group. Check that the filter still matches the new remarks. If the old and new URLs are separate subscriptions you want to keep, create another group so the existing settings aren't overwritten.

Should I filter a node out after one failed test?

Retest the node on the same network and compare it with another node in the same group. If the whole group fails, check your network and core logs first. If only one node keeps failing, decide whether to exclude it. Filters work best for managing consistently named entries, not tracking temporary connectivity issues.

v2rayN clientFind downloads by platform