For v2rayN users who have imported subscriptions but often struggle to find a server in a mixed list. Group subscriptions by source first, then distinguish between on-the-fly search and filtering during updates. Check connection settings before removing duplicates, then test and sort servers within each group. Compare counts before and after cleanup so filtered results aren’t mistaken for a broken subscription.
Group Subscriptions by Source
Groups separate subscription sources and update scopes; they don’t change the system proxy, TUN, or routing rules. Even if two subscriptions both contain a server named “Hong Kong 01,” keep them in separate groups first. Use clear labels such as “Provider A · Primary” and “Provider B · Backup.” Avoid naming groups after the fastest server: performance changes, while the subscription source helps you troubleshoot updates.
Create a Group
In the v2rayN 7.x main window, open “Subscription Group” → “Subscription Group Settings” and add an entry. Give it a recognizable remark, paste the full subscription URL into the address field, leave the filter blank for now, and save.
Keep Subscriptions Separate
Create a separate entry for the second subscription rather than replacing the first URL. If your provider changes the URL for the same subscription, edit the existing entry. Keeping both the old and new URLs can make the same servers appear twice.
Update One Group
Select the new group above the server list, then open “Subscription Group” and choose the appropriate “Update Current Subscription” option, with or without proxy. Update one group first; don’t choose “Update All.” Menu labels may vary slightly between minor versions.
Record a Baseline
Clear the server-list search box, confirm the selected group, record the number of imported servers, and note two or three representative server names. Repeat for the second group. Group names are useful in troubleshooting notes, but subscription URLs may contain access tokens—never include them in public screenshots or logs.
Server Filtering: Search vs. Update Filters
To find servers in a specific region, enter a short keyword from a server alias in the current group's search box, such as Tokyo or Tokyo. Copy a keyword from an alias you can already see rather than assuming “Japan” will match JP, Japan, and Tokyo. Clear the search to show the full list again; there’s no need to update the subscription.
Search the Server List
RecommendedThis only narrows the current view. Start with a keyword you know will match, then try another naming variant that actually appears in the list. Clear the search when you’re done so the visible count isn’t mistaken for the group total.
Best for: quickly finding a region, checking server names, or selecting servers to test.
Subscription Group Filters
Go to “Subscription Group” → “Subscription Group Settings,” edit the relevant entry, change its filter, then update that group. The filter applies when servers are imported during an update. Use a pattern such as Tokyo|JP only if the current version explicitly says the field supports regular expressions. Test one keyword first; the server-list search box is not a regex field.
Best for: stable naming conventions when you want to keep the same kinds of servers after every update.
Some subscriptions include remaining data or expiration dates as list entries. Check the alias and entry contents before deciding whether to exclude them. Don’t filter broadly on words like “remaining” or “expires”: providers may add notices to otherwise valid server names. After setting an update filter, check examples that should remain and disappear; that’s more reliable than looking at the total alone.
Removing Duplicates: Same Name Doesn’t Mean Same Connection
Before deciding two entries are duplicates, check whether they belong to the same subscription and compare their configurations in the server details. Two entries can share a server address and port but use different credentials, transport settings, or security parameters. Conversely, different aliases may just be different display names for the same configuration. You can keep identical configurations from separate subscriptions for now to track whether each source still provides that endpoint after future updates. Don’t assume they offer independent failover if one connection fails.
| What You See | What to Check | What to Do |
|---|---|---|
| Same name and address | Port, protocol, transport, security, and authentication settings | If any connection setting differs, keep them as separate configurations for now |
| Different names in the same group | Whether the full connection settings match and which entry is currently in use | Once confirmed identical, keep the entry in use or the one that’s easier to recognize |
| Different names in different groups | Whether the settings match and whether each source needs to be updated independently | Keep both group assignments for now; don’t bulk-delete across groups |
Clean up entries only in the currently selected group. If the server still provides a duplicate configuration after the next update, a manually deleted entry may reappear. If the duplicate and the one you want to keep have consistently different aliases, test a filter on one group first. If the aliases don’t distinguish them, don’t broaden the filter just to avoid manual cleanup. Check credentials locally; there’s no need to paste a server share link into a comparison tool.
Sort Servers: Compare Results from the Same Test Run
This worked example shows how to track server counts; the numbers are not measured speeds. Suppose Provider A imports 12 entries. After checking them, you find that 4 aliases contain “Tokyo.” Of those four, only 3 have distinct connection settings. Separate these three counts before deciding which servers to test.
Takeaway: Exclude failures before sorting by latency
Choose candidates by sorting successful real-connection latency results from the same test run, lowest first. Blank, timed-out, and failed results aren’t lower latency; exclude them from the comparison and retest later.
- Keep test conditions consistent. Select candidate servers in the current group and run the real-connection latency test from the server list’s right-click menu. Use the same device, network, and test target, then review the latency column after the batch finishes.
- Compare results for your use case. For frequent, short requests, start with real-connection latency. For large file transfers, run download speed tests on a small shortlist. A single peak download speed doesn’t tell you how stable a connection is for everyday use.
- Recheck after updates. Sorting a column changes only how the list is displayed; it doesn’t change the active server or routing rule priority. If an update replaces servers in the group, don’t apply old results to the new entries. Run the same tests again if needed.
Subscription Group Updates and Filters: FAQ
Why did every server disappear after I added a filter?
First clear the main window’s search box and confirm that no servers are visible. Then return to “Subscription Group Settings,” clear the group’s filter, save, and update that group only. If servers return with no filter, copy a short keyword from an imported alias and try again. If the group is still empty, check the update log to tell a request failure from content that couldn’t be parsed.
Why doesn’t the same keyword find anything in another group?
Switch to the other group, clear the search, and check the actual aliases. One provider might use “Tokyo,” while another uses JP. Check keywords separately before saving each group’s filter; don’t apply the same filter to different sources in bulk.
The current group update timed out. Should I update all groups?
Don’t widen the update scope yet. Check that the group’s subscription URL is complete, then review the failure type in that group’s log. If a direct request times out and you already have a working server, enable it and retry with the current subscription’s “Update via proxy” option. If the response says the subscription has expired or access is denied, check its status instead of repeatedly switching update methods.
Why did my custom server name revert after an update?
Subscription updates may recreate entries using the content returned by the provider. Use the group remark to record the source and purpose; don’t store information you need to keep only in a server alias. After updating, clear the search, check the server count, and confirm that the active server still uses the intended configuration.