This practical guide is for beginners who have installed v2rayN on a Windows desktop but are not sure what to do with a provider subscription. It explains how subscription groups work, where to paste a subscription URL, how to update and verify imported nodes, how to choose the active profile, and how to manage several providers without mixing their settings. Menu names can vary slightly between v2rayN 7.x releases, but the workflow remains the same.
Understand What a Subscription Group Does
A v2rayN subscription group is a container for nodes downloaded from one subscription source. The group usually represents one provider, account, region, or service plan. After v2rayN reads the subscription URL, it parses the returned content into server profiles such as VMess, VLESS, Shadowsocks, Trojan, SOCKS, or other supported formats. The group itself is not a proxy protocol and it does not establish a connection; it only helps v2rayN organize and update the profiles.
This distinction matters when several providers are used at the same time. A subscription URL may return dozens of nodes, while a manually imported share link usually creates one individual profile. Updating a group replaces or refreshes the profiles associated with that source. It does not normally update manually created nodes from another group. Keeping each provider in its own group makes it easier to identify which URL produced a node and to remove an expired service without affecting unrelated profiles.
- Subscription group: Stores a provider URL, remark, update behavior, and the nodes downloaded from that URL.
- Node profile: A single imported server configuration containing an address, port, user ID or password, protocol, transport, and security parameters.
- Active server: The node currently selected for the v2rayN core to use when the proxy starts.
- Core: Xray or another supported core that actually handles the inbound local proxy and remote outbound connection.
Prepare the Subscription URL Before Importing
Obtain the subscription URL from the provider’s account page or delivery message. Copy the complete address, including the scheme at the beginning and every character after it. A valid URL may be long and may contain encoded characters, an access token, or query parameters. Do not copy only the visible provider name, a shortened display label, or the URL from a browser address bar after a failed login page has loaded.
Before opening v2rayN, confirm that the subscription is still active and that the provider allows desktop access. Some providers issue different links for different clients, while others provide one universal link. If the provider documents a required subscription format, follow that instruction rather than guessing from the URL. A subscription that returns HTML, a login page, an expiration notice, or an empty response cannot be parsed as a node list.
Check the URL and Account Status
- Paste the URL into a private text editor first and confirm that it is one uninterrupted line.
- Check whether the provider has limited the number of update requests or devices.
- Verify the account expiration date, traffic allowance, and remaining connection quota.
- Do not manually add
http://orhttps://if the provider already supplied a different complete scheme. - If the URL contains a token, avoid sending it to support in plain text; provide a redacted screenshot instead.
Provider subscription
- Input
- Complete subscription URL
- Output
- Multiple node profiles
- Update
- Refresh from the same source
Use one clearly named group so future updates remain easy to identify.
Single share link
- Input
- VMess, VLESS, or other share link
- Output
- Usually one node
- Update
- Manual editing or replacement
Use this for an individual profile, not as a replacement for a provider group.
Add Your First Subscription Group
Launch v2rayN and allow the main window to finish loading. If the application asks for a core or shows that no usable core is available, resolve that prerequisite first. Subscription parsing and node storage are client functions, but connection testing requires a working core. In v2rayN 7.x, the relevant controls are commonly exposed through the top menu named Subscription Group, Subscription Group Settings, or a similarly translated label. Minor releases and language packs may use slightly different wording.
-
Open group settings
In the main v2rayN window, open Subscription Group and choose the entry for managing or editing subscription groups. Look for a table or dialog containing group remarks and subscription URLs.
-
Create a group
Click Add, New, or the plus button. Enter a short remark such as “Provider A” or “Work account” instead of leaving the default name.
-
Paste the URL
Paste the complete provider URL into the subscription address field. Do not paste a node share link into a field intended for a subscription response.
-
Save the entry
Click Confirm, Save, or Apply. Reopen the group list if necessary and verify that the remark and the address are both present.
-
Update the group
Return to the main window, open the subscription update menu, and select the newly created group. Wait for the completion message before testing a node.
Some versions provide an option such as Update subscription without proxy and another such as Update subscription through proxy. Start with the direct method when the provider URL is reachable from the current network. If the direct request times out but an existing node works, select the through-proxy method and choose a known working profile first. Updating through an untested or expired node can create a misleading second failure, so keep the first test simple.
After the update completes, return to the main server list. The new profiles may appear with a group prefix, a provider remark, or a separate group indicator. Select one profile, use the latency test function if available, and then start the core. A successful latency result is useful but is not the same as confirming that every website or application will work. Open a normal test page and check the system proxy status as well.
Verify Imported Nodes and Local Proxy Settings
Imported nodes should be checked in two stages: first confirm that v2rayN parsed the subscription correctly, then confirm that the selected node can carry traffic. Open the node details only when needed. For a VLESS profile, review the address, port, user ID, transport, security mode, server name, public key, short ID, and flow when those fields are present. For VMess, check the user ID, alterId or compatibility field, encryption selection, transport, host, path, and TLS settings. These values are generated by the subscription and should not be changed casually.
A node can appear in the list while still being unusable. Common causes include an expired subscription, an invalid server address, a blocked port, a mismatched TLS server name, a missing REALITY public key, or a core that does not support the imported feature. If several nodes fail at once, suspect the subscription response, account status, local network, system time, or core configuration before editing every node individually.
| What you see | Most likely area | First action |
|---|---|---|
| Group is created but no nodes appear | URL, response format, or account status | Recheck the complete URL and update result message |
| Nodes appear but every latency test fails | Network, DNS, time, port, or expired service | Test another network and inspect the core log |
| One node works and others fail | Individual server or protocol parameters | Keep the working node and compare details carefully |
| Core starts but browsers show no traffic | System proxy, routing, or local port | Check the system proxy and local listener ports |
Practical conclusion: verify the group before editing nodes
If an entire newly imported group fails, changing VLESS to VMess or rewriting transport fields is usually the wrong first move. Confirm the URL response, account validity, system time, selected core, and subscription update result before changing generated parameters.
Manage Several Subscription Groups Safely
When using multiple providers, give every group a unique and meaningful remark. Names such as “Provider A”, “Provider B”, and “Provider C” become difficult to remember after a few weeks. A better pattern is “Work-Asia”, “Travel-Europe”, or “Backup-2026”, provided the name does not expose private account information. Keep the original provider URL associated with the correct remark and avoid replacing one group’s address simply because two providers use similar node names.
Update groups one at a time when diagnosing a problem. If all groups are refreshed simultaneously, it becomes harder to determine whether a failure came from a provider response, a local network interruption, or a rate limit. After each update, note the number of imported nodes and the time of the last successful refresh. If a provider suddenly returns zero nodes, preserve the previous configuration if v2rayN offers that option and contact the provider through its official support channel.
Why did the update finish but the list stay unchanged?
Check whether the selected group is the one you just updated. Then close and reopen the group or refresh the server list. If the update response contains no valid profiles, inspect the account status and the update log.
Should every provider use a separate group?
Yes, separate groups are the clearest arrangement. They preserve the relationship between a provider URL and its imported nodes and make deletion or renewal less likely to affect another service.
Can I rename a node after importing it?
You can usually edit the remark for easier recognition, but avoid changing technical fields unless the provider documents the change. A renamed node still depends on the original address, port, protocol, and security parameters.
Which group should be active when v2rayN starts?
The active item is normally an individual node, not simply the group name. Select a tested profile from the desired group, then start the core and enable the required system proxy mode.
- Set a practical update interval instead of refreshing repeatedly. Once or twice per day is usually enough unless the provider specifies another schedule.
- Remove expired groups only after confirming that no working node or local rule still depends on them.
- Keep one known working profile as a baseline for testing subscription updates through a proxy.
- When comparing providers, use the same local proxy mode, browser, destination, and test time.
- Review the v2rayN and core versions after an upgrade if a previously valid subscription stops parsing correctly.
Finish the First Connection and Keep It Maintainable
Once a node has passed a latency test, select it in the main list and start the core. Confirm that the local listener is running on the expected ports, commonly SOCKS on 127.0.0.1:10808 and HTTP on 127.0.0.1:10809, although your v2rayN configuration may use different values. The browser or application must use the same local proxy type and port. If the client shows a running core but the application is still direct, enable v2rayN’s system proxy option or configure that application manually.
Check one ordinary website, one domain that should follow the proxy route, and a direct destination if your routing policy separates traffic. Then inspect the core log for repeated DNS failures, connection refusals, TLS errors, or restart loops. If the first node fails, test another profile from the same group before changing the group URL. If every profile fails, test the subscription through a known network and review the provider’s status.
A clean routine prevents most subscription confusion: create one group per provider, use a descriptive remark, update it only when necessary, select a tested node, and keep the local proxy port documented. When a provider changes its node parameters, update the group instead of manually rebuilding every profile. When v2rayN changes its menus, look for the same concepts—subscription group management, update subscription, server list, active profile, core startup, and system proxy—even if the exact English label differs.