v2rayN Multiple Subscription Groups: Organize Providers and Filter Servers

1. Group by source, filter by purpose

The most common mistake when managing multiple subscriptions is mixing up their source and intended use. Subscription groups identify which subscription address a set of servers came from; use search terms to find regions, routes, or protocols. If one provider offers servers in multiple regions, there’s no need to add the same subscription repeatedly.

A subscription is an address used to retrieve server configurations. It isn’t a server itself, and it doesn’t provide routing rules. Moving a node into a “Work” group won’t make work apps use it automatically. Traffic routing still depends on the selected server, system proxy or TUN, and routing rules.

2. Create separate subscription groups

In the main window, open “Subscription Groups” → “Subscription Group Settings.” The menu location may vary by platform, and the add control may be labeled “Add” or “+.” Follow the labels in your current interface. The goal is to open the subscription group editor, not to add an individual VMess or VLESS server manually.

1. Review existing groups

   Go to “Subscription Groups” → “Subscription Group Settings” and review the existing names and addresses. Make sure the exact same subscription address hasn’t been added twice. Addresses for different accounts aren’t duplicates just because they share a domain.

2. Add a source

   Click “Add” or “+.” Set the label to “A-Primary” and enter the full link provided by your provider. Example format: https://example.com/sub?token=xxxx. This address is for illustration only and is not a working subscription.

3. Add the backup groups

   Create “B-Backup” and “C-Test.” Enter only the address associated with each source. Leave complex filters off for the initial import so that “no matches” isn’t mistaken for an expired subscription.

4. Update one group at a time

   After saving, return to the main window and open the “Subscription Groups” menu to find the option for updating the current subscription. Update group A by itself and check the log, then handle B and C. When first organizing subscriptions, don’t use a bulk update that could hide errors in individual groups.

5. Verify group assignments

   Switch between subscription groups in the main window and confirm each shows servers from the expected source. Check server labels, protocols, and addresses, then test an actual connection with one server. This distinguishes a successful import from a working connection.

3. Name groups and filter servers

Standardize group labels, but don’t rush to bulk-rename servers from a subscription. Providers may rebuild the server list on the next update, so manual label changes might not stick. Use “A-Primary” and “B-Backup” to identify sources, then search for region or route keywords in the original server names. This takes less effort to maintain.

A temporary search isn’t a subscription filter

Search in the main window usually narrows the list currently on screen; clear the search to show the other servers again. A filter in the subscription group editor may determine which servers remain after an update. Use the first for a quick search and the second to reduce the list over time. They aren’t the same operation.

• Try one keyword first: Switch to group A and search for HK. Note the results, then clear the search and try Hong Kong. Matching may depend on case, search scope, and where you enter the term. Don’t assume every search field works the same way.
• Check the filter syntax: Use 香港|HK to match either term only if the field documentation explicitly supports regular expressions. A plain-text search may treat the vertical bar as a literal character.
• Don’t guess how to exclude terms: !实验 and -倍率 aren’t universal syntax. Follow the instructions for the current field. If none are provided, stick to simple keyword filtering.
• Change one thing at a time: After changing a subscription filter, update only that group and check the results. If the entire group is empty, clear the filter and update again before considering deleting the subscription.

4. Set update intervals and update through a proxy

Automatic updates refresh configurations; they don’t extend your plan or switch to the fastest server. In the subscription group editor, find the automatic update interval and check its units and activation conditions. If the interface uses minutes, start with the examples below. If there’s no such field, update manually instead of looking for a setting that isn’t available.

These are configuration suggestions, not software defaults. Follow your provider’s guidance if it specifies an update frequency. Don’t set the interval to one minute and repeatedly make requests: server configurations rarely need refreshing that often, and the provider may impose rate limits. You can turn off automatic updates for the test group until you’ve verified the address and filter settings.

• Check when the app can run: Don’t assume the client’s built-in scheduler will run after shutdown. Updates may be delayed while the computer is asleep or the app is closed.
• Choose an update method based on connectivity: If the menu offers regular updates and updates through a proxy, first check whether the subscription domain is reachable directly. If it is, use a regular update.
• Connect through a working server first: Connect to a server you’ve verified works before updating through a proxy. A broken current server can’t retrieve its own replacement configuration.
• Check the specific error: For a timeout, check the network path. For a 401 or 403 response, verify your credentials and check your provider’s instructions. If the response can’t be parsed, make sure you haven’t entered an account webpage URL by mistake.

5. Remove duplicate servers and expired subscriptions

Servers with the same name aren’t necessarily duplicates. Two servers called “Hong Kong 01” may come from different providers and have different addresses, ports, or authentication settings. Conversely, a renamed server may look like a new one. Compare the group, protocol, server address, port, and transport settings. Don’t delete everything based on names alone.

1. Check for duplicate subscriptions first: In group settings, check whether the exact same subscription address was added twice. Before keeping one group, verify which group contains the servers in use and back up any configurations you need.
2. Check manual imports too: Servers imported from the clipboard may not be removed when a subscription refreshes. Verify their source and handle them separately; don’t mistake manually added entries for subscription leftovers.
3. Distinguish expiration from a temporary failure: One timeout doesn’t prove that a subscription has expired. Check your provider account, update logs, and response details before pausing updates or removing a group.
4. Choose a server again after cleanup: An update may replace server entries. Make sure the current selection still points to a valid configuration, test the connection again, and verify browser access.

6. Common questions about managing multiple subscriptions

7. Post-update checklist

A reliable workflow keeps sources organized, filters reversible, and updates easy to track. After configuring your subscriptions, follow the checklist below; it’s usually easier to spot problems this way than by piling on complex filter expressions. For more about how proxies and routing work together, see the user guide or the glossary.

• Each group matches its source and address, with no unintended duplicate subscriptions.
• Clearing the search restores the full list, and persistent filters have been tested for their effect and syntax.
• Automatic update units and intervals are correct, and the subscription can be fetched over an available network path.
• The current server is in the expected group, and its connection and real-world access have been checked after the update.
• The status of expired groups has been confirmed, and backups and screenshots don’t expose subscription credentials.