v2rayN Subscription Groups and Server Filters: Manage Multiple Proxy Subscriptions

First, know the difference: subscription groups aren't Routing

A subscription URL typically returns a set of server configurations. v2rayN reads their protocol, address, port, and authentication details, then organizes them into a server list. When you mix multiple sources, region names and traffic multipliers can appear more than once. If an update fails, it can also be hard to tell which source caused the problem.

Groups track where each configuration comes from—that is, which subscription maintains a server. They don't automatically send browser traffic through one group and download traffic through another, nor do they enable automatic failover just because a group is named “Backup.” Traffic routing still depends on the system proxy, TUN, routing rules, and the outbound configuration currently in use.

VMess and VLESS are protocols used in server configurations, not group types. Filtering subscription names with regex won't convert a protocol. Even if a name contains “VLESS,” open the server configuration to verify its actual protocol and transport settings.

Create subscription groups: one record per source

These steps use the common Chinese-language interface in the desktop version of v2rayN. Button locations and punctuation may vary slightly across versions. Look for fields such as subscription group settings, subscription URL, and alias filter; don't confuse the server editor with subscription settings.

1. Open group settings

   From the main window, select “Subscription Groups” → “Subscription Group Settings,” then choose “Add” or “+” to create a subscription record. When organizing subscriptions for the first time, add one source and verify it works before adding the next.

2. Name the source

   Use a label such as “Primary-A” or “Backup-B.” Enter the full subscription URL provided by the service in the address field. Don't paste an account login page or use a single-server share link as the subscription URL.

3. Leave the filter blank initially

   For the first import, leave “Alias Regex Filter” blank and save the record. This lets you confirm that the URL works and its contents can be parsed, without subscription errors and filter mistakes happening at the same time.

4. Update the current group

   Return to the main window and select the new group. From the “Subscription Groups” menu, choose the option corresponding to “Update Current Subscription (without proxy).” If the source isn't directly reachable on your current network, use the corresponding update-through-proxy option instead.

5. Check it, then add another group

   Check the logs for a successful update and confirm that server configurations appear in the group. Then create “Backup-B” and update it separately. This makes errors easier to pinpoint than updating every source at once.

If the interface offers an automatic update interval, first confirm that manual updates work reliably, then set a reasonable frequency for each source. Don't repeatedly fetch subscriptions just to “stay up to date.” An update only retrieves configurations; it won't fix a remote server outage or change your account's traffic allowance or expiration date.

Write a filter regex: keep locations, then exclude notices

The “Alias Regex Filter” in subscription settings usually matches server aliases—the names shown in the list—and keeps entries that match. It doesn't determine a server's actual location or identify connection quality. If a name doesn't contain the target keyword, the server may be filtered out even if it's physically in the target region.

Start with a simple “or” expression, then add exclusions. “Hong Kong,” “Japan,” and “expiry” below are example name terms only; they don't refer to any real provider or indicate availability.

| means “or,” ^ marks the beginning, $ marks the end, and .* matches any number of characters. A negative lookahead, (?!...), defines an exclusion. These patterns are for v2rayN alias-filter fields that support the corresponding regex syntax; they won't work as-is in search boxes that accept only plain keywords.

• Enter the expression as-is: Don't wrap it in JavaScript-style slashes. Enter Hong Kong|Japan, not /Hong Kong|Japan/.
• Escape special characters: To match the literal text [A], enter \[A\]; to match a period, enter \..
• Check the actual naming format: \bHK\b matches “HK-01” but may not match “HK01.” Check how the provider formats names before adding more complex conditions.
• Avoid filtering out valid entries: Some legitimate server names may contain terms such as “expiry.” Check sample names before adding exclusions; don't assume the same list of terms applies to every source.

Test against fixed samples before updating a live subscription

A regex that doesn't produce an error isn't necessarily filtering as intended. Write down a few names that should be kept and excluded, then test them one by one. If you only know what you want to keep, but not what must never be removed by mistake, filter rules tend to grow more complicated over time.

Expression: ^(?!.*(remaining traffic|expiry|official website)).*(Hong Kong|Japan).*$

Hong Kong-01          → Keep
Japan-02          → Keep
Japan-backup        → Keep
Singapore-03        → Exclude: not a target region
Hong Kong-expiry notice    → Exclude: contains “expiry”
official website address         → Exclude: contains “official website”

These counts are the expected results for this manually created sample set, not provider server counts or connection test data. Enter the expression in the target subscription's “Alias Regex Filter,” save, then update the current subscription. Saving the setting alone may not reprocess entries already imported.

1. Clear any temporary search in the main window, then select the target subscription group to avoid combining two filters.
2. After updating the current subscription, check that at least one expected server is still present and one expected name has been excluded.
3. If the group unexpectedly becomes empty, first simplify the regex to Hong Kong|Japan. If that still returns no results, clear the filter and update again.
4. Once you've confirmed the filter results, select a server and test its connection. A successful update doesn't confirm that a server is reachable.

Tell a failed subscription update from a failed server connection

Updating a subscription connects to the subscription server; connecting to a node reaches the proxy server. They may use different domains and ports. If the subscription downloads successfully but the node times out, check the node configuration, service status, and local network. If the node works but the subscription update fails, check the subscription URL and the network path used for the update.

Keep groups tidy: track each source and avoid duplicate maintenance

For day-to-day management, aim for clear sources, simple filters, and changes you can undo. Primary and backup groups can follow the same naming convention, but identical names don't mean two configurations are duplicates: a difference in domain, port, protocol, transport settings, or authentication details may indicate a separate endpoint.

• When a subscription URL changes, edit the existing group: If the source is the same and only the token or URL has changed, update the existing subscription record. Note the old label and filter expression first, then organize the old record after confirming the new URL works.
• Manage manual servers separately: Don't rely on editing a subscribed server to preserve custom settings; a later update may recreate or overwrite it. If you need to keep a custom configuration, maintain it separately from the subscription and protect its authentication details.
• Verify each group before updating them all: Use “Update Current Subscription” when setting up or troubleshooting. Once every source is stable, use “Update All Subscriptions” for routine updates. Follow up on log errors with the specific source that failed.
• Sorting isn't a speed test: Sorting by name only makes the list easier to browse. Connection tests, download performance, and access to a target website are different measures; a name containing “high speed” or “dedicated line” proves nothing on its own.
• Check settings again on other devices: This guide covers subscription groups in desktop v2rayN. Android v2rayNG uses the Xray core, while v2flyNG uses the V2Fly core. Don't assume their menus, filter fields, or exported configuration formats exactly match the desktop version.

Keep the workflow simple: create a group for each source, leave the filter blank for the first import, test regex against real names, update the current group, then check the connection. This reduces list clutter and makes it easier to tell whether an update problem comes from the URL, the filter, or the server itself.