Save each provider’s subscription separately, then use groups and keywords to narrow the server list. This guide is for desktop users with two or more subscriptions. Follow the steps to create groups, distinguish quick searches from import filters, schedule updates, and troubleshoot missing or duplicate nodes and update timeouts. Example values are suggested management settings, not provider node counts or measured network results.
Know the difference between subscription sources, server lists, and routing rules
A subscription link provides access to node configurations and usually contains an account token. v2rayN reads the subscription and adds supported server configurations to your local list. Subscription groups keep track of each source, so you can fetch its configurations again during later updates. Importing several links together may work at first, but makes it harder to tell which source needs renewal, replacement, or removal.
Groups are not routing rules. Selecting a “Backup” group does not automatically send traffic for a particular website through a backup connection. Searching for “Japan” in the list does not block traffic to other regions. Traffic routing depends on the active server, whether the system proxy or TUN is handling traffic, and the core’s routing configuration.
| Action | What it changes | What it does not do |
|---|---|---|
| Select a subscription group | Narrows the configurations currently shown | Does not route traffic by website |
| Enter a keyword in the list | Temporarily filters visible servers | Does not delete remote subscription content |
| Set a subscription filter | Affects which configurations are kept after an update | Does not change your provider account permissions |
| Switch the active server | Changes the proxy exit configuration | Does not ensure every app is using the proxy |
Create a separate subscription group for each provider
Open the v2rayN main window, then go to “Subscription Group” → “Subscription Group Settings.” Menu locations may vary between desktop versions; the steps below use the subscription group settings window in the Chinese interface. If you don’t see a separate Add button, look for the add option in the window’s list. Don’t paste a subscription URL into a server address field.
-
Get the subscription URL
Copy the client subscription link from your provider’s account page. Make sure you have the full URL, not a purchase page or account dashboard address. Keep the link in your local settings; never include it in a public screenshot.
-
Add your primary group
Go to “Subscription Group” → “Subscription Group Settings” and add an entry. Set the alias to “Primary-A,” paste the first link into the subscription URL field, and leave the filter blank for now. Save your changes.
-
Add a backup group
Repeat the steps and use “Backup-B” as the alias, then enter the second provider’s link. Save each source separately; don’t combine two links into one URL.
-
Update each group separately
Return to the main window and select a group. From the “Subscription Group” menu, update the selected subscription. Confirm that the first group imports successfully before updating the second, so any errors are easier to trace to their source.
-
Confirm the active configuration
Check the import results, select a server you know works, and set it as active. Switching the group label alone does not change the proxy exit. Check the active configuration shown in the main window.
Choose a grouping strategy that’s easy to maintain
Separating subscriptions by source and then searching within each source by region is the easiest way to trace problems. Region, protocol, and billing multiplier are node attributes, so they’re usually best used as filters—not as reasons to import the same subscription repeatedly. “2x” in a node name often refers to the provider’s billing multiplier, but check the provider’s documentation rather than assuming how usage is charged.
Group by subscription source
RecommendedKeep one group per provider, with its own link, update interval, and filter rules. If a subscription expires or its URL changes, you only need to update the relevant group.
Best for: using multiple providers and needing to identify which source failed to update.
Create a separate group for manual configurations
Keep manually maintained single-node configurations separate from subscription nodes. If a manual group has no subscription source, “Update all subscriptions” will not refresh its address or credentials.
Best for: managing both subscription-based and self-hosted server configurations.
Split one source across groups by purpose
Using the same URL in multiple groups leads to duplicate downloads and configurations. Do this only when you genuinely need different import filters, and check the rules in each group.
Best for: isolating distinct subsets of nodes when you’re prepared to maintain multiple sets of filters.
Search by keyword first, then set an import filter
Select a subscription group, then enter part of a node name in the main window’s server list search or filter box. Try one term, such as “Japan,” then clear it and compare the results. Search behavior may vary by version. If searching for “VLESS” returns no results, check the protocol column before concluding that the subscription has no VLESS nodes.
- Search by region: Try “Japan,” “JP,” or “Tokyo.” Providers use different naming conventions, so no match for one keyword doesn’t mean the region is unavailable.
- Search by use case: Look for labels already present in node names, such as “Download” or “Streaming.” These are provider labels, not a substitute for testing access to the websites you need.
- Search by multiplier: Search for “1x” and check the full node name. “1x,” “1.0x,” and localized multiplier labels may not match each other.
- Show the full list again: Clear the search field and switch back to all groups. Rule out a display filter before updating the subscription again.
Searching the list usually changes only what’s currently displayed. To keep only matching nodes after each subscription update, go to “Subscription Group” → “Subscription Group Settings” and edit the relevant group. Check its filter field and instructions. Some versions support regular expression filters; use the expression below only if the field explicitly supports regular expressions. Don’t assume it works in every search box.
Japan|JP|TokyoThis regular expression matches any one of the name fragments, not all three at once. Case sensitivity depends on how the current field is implemented, and “JP” may match unrelated strings. Check node names with a temporary search before setting an import filter. After saving, update the group and review which nodes remain. To restore previously filtered configurations, clear the import filter and update the group again.
Set an automatic update interval and keep manual updates as a fallback
Go to “Subscription Group” → “Subscription Group Settings” and edit the group. Find the automatic update fields and check the displayed unit before entering a value. If the field is in minutes, 720 means 12 hours—entering 12 will not set a 12-hour interval. Also confirm that automatic updates are enabled; changing the interval alone may not enable them.
These intervals are starting points, not client defaults. Subscriptions usually don’t need to refresh every few minutes; follow your provider’s request limits. Scheduled tasks may not run on time while the client is closed, the computer is asleep, or the network is offline. Manually update the current group when needed after resuming use.
- Update manually once and confirm the subscription URL and parsed results are correct before enabling automatic updates.
- Use different intervals for primary and backup subscriptions to avoid sending requests to several subscriptions at the same time.
- If a direct update times out while your current proxy server is working, use the update command containing “through proxy” in the “Subscription Group” menu. Don’t keep retrying that route when the proxy itself is unavailable.
- After updating, check that the active server is still listed. If a node’s name, address, or identifier changes, the previous selection may no longer work.
Troubleshoot missing nodes and update failures by symptom
Start troubleshooting without changing the current setup. Note the group name, update time, and error message; don’t delete all configurations right away. A subscription can fail while requesting the URL, parsing its contents, or applying a local filter. Identify the stage first to avoid repeatedly changing routing settings for a dead link.
The update succeeded, so why is the list empty?
Clear the search filter in the main window and select the relevant group. If the list is still empty, go to “Subscription Group” → “Subscription Group Settings,” temporarily clear that group’s import filter, save, and update the group. If nodes return, the filter didn’t match. If the list is still empty, check whether the subscription returned configuration content supported by the client.
There are two nodes with the same name. Should I delete one?
Check which groups the configurations belong to, then compare their server addresses, ports, protocols, and transport settings. Two nodes with the same name aren’t necessarily the same endpoint. If the same subscription was added twice, keep one working group and remove the duplicate source. Deleting only a server row may not help; it can reappear during the next update.
Why does the backup subscription keep timing out when the primary one works?
Select the backup group on its own and update it manually. Check whether the error is a timeout, access denied, or a parsing failure. For a timeout, try both a direct update and an update through a working proxy. For access denied, check your account status and whether the subscription URL was reset. For parsing errors, make sure you copied the subscription URL, not a webpage address.
Why did my renamed node revert after an update?
Subscription node details may be overwritten by remote content during an update. Keep permanent notes in your own records instead of relying on local renaming. If you need a configuration you can maintain independently, save it to a manual group and note that it will no longer sync automatically with the original subscription.
Can I share a screenshot of my subscriptions to get help?
Show only the group alias, filter conditions, and error text. Hide the full subscription URL and node credentials. Tokens in subscription links may allow others to access your account configuration. If a link has already been exposed, reset it on your provider’s account page and replace the old URL in the corresponding local group.
Finish with a repeatable maintenance check
Once setup is complete, check every source in the same order: confirm the group is identifiable, updates complete, filters can be cleared, and the active server is clear. For routine maintenance, change only the affected group; there’s no need to clear other working subscriptions just because one source fails.
- Check sources: Each subscription has its own clear alias, and manual configurations are kept separate from subscription configurations.
- Check visibility: Know how to clear keywords so hidden nodes aren’t mistaken for deleted ones.
- Check updates: Automatic updates are enabled, the interval uses the correct unit, and a manual update produces the expected results.
- Check connectivity: Know which server is active. If apps need to use the proxy, separately confirm the system proxy or TUN settings.
- Check privacy: Keep management notes to aliases and actions taken; don’t copy subscription tokens or server credentials.