This guide explains the complete v2rayN desktop workflow for creating and managing subscription groups. You will learn how to identify a real subscription URL, open the correct menu, enter the provider address, assign a group name, refresh profiles, select a server, and enable the local proxy. It also covers update settings, duplicate groups, empty results, timeouts, format errors, and the checks that help you decide whether a problem comes from the provider, the network, or v2rayN itself.
Understand subscription groups before adding one
A subscription group is a saved relationship between a provider URL and the node profiles returned by that URL. The address is normally an https:// or http:// link supplied by your service provider. After v2rayN requests the address, the provider returns a collection of share links or structured node data. v2rayN parses that response and creates local profiles under the selected subscription group.
The group is more than a folder name. It stores the source address, the group label, and update-related settings. When you choose an update action later, v2rayN requests the same source again and refreshes the profiles associated with that group. If the provider removes a server, changes its port, or adds a new VLESS + REALITY profile, those changes can appear after a successful update.
Do not confuse a subscription URL with an individual share link. A string beginning with vmess://, vless://, trojan://, or ss:// normally describes one node. It should be imported through the share-link or clipboard import function, not pasted into a subscription group field. A subscription URL may return Base64 text containing many share links, plain line-separated links, or a provider-specific JSON response.
| Input you received | What it usually represents | Correct v2rayN entry | Can update automatically? |
|---|---|---|---|
https://... labeled as a subscription |
A provider endpoint returning multiple profiles | Subscription group settings | Yes, after an interval or manual update |
vmess:// or vless:// |
One individual share link | Import from clipboard or batch URL import | No, unless re-imported or edited |
| Long Base64-looking text | An encoded collection of share links | Use it only through the provider subscription URL | Depends on the source URL |
A JSON file containing inbounds and outbounds |
A complete core configuration | Custom configuration workflow | Usually maintained separately |
Prepare the URL and v2rayN installation
Before opening the subscription dialog, copy the complete provider address from the provider dashboard or account message. Make sure the link is not a shortened login page, a plan-management page, or a temporary browser URL containing unrelated parameters. A valid subscription address may be long, and some providers include an access token after the question mark. Do not remove that token or insert spaces when copying.
Use a current v2rayN desktop build that matches your Windows architecture and runtime requirements. In 2026, many desktop distributions are based on the 7.x interface family, but menu wording can vary slightly between releases and language packs. The important entries are usually named Subscription Group, Subscription Settings, Update Subscription, and Update All Subscriptions. If your interface uses a translated label, look for the same function rather than relying on an identical English phrase.
Extract v2rayN to a writable folder instead of running it from a compressed archive. A folder such as a personal applications directory makes it easier for v2rayN to save settings, subscription metadata, logs, and core files. If the program does not start, check the package dependency first. A non-self-contained package may require a compatible .NET Desktop Runtime, while a self-contained package normally includes the required runtime components.
Open v2rayN
Extract the package, start the main executable, and wait for the tray icon and main window. Allow the application through the Windows firewall only when the prompt matches the local proxy functions you intend to use.
Open group settings
Choose Subscription Group from the main menu, then select the add or manage action. Some builds place this function under Settings or Subscription Settings.
Enter the URL
Paste the complete provider-issued subscription address into the URL field. Avoid adding quotation marks, spaces, or a single-node URI prefix that belongs to another import function.
Name the group
Enter a short label such as “Primary Provider” or “Work Nodes.” Choose a name that remains clear when several groups are displayed in the server list.
Save and update
Confirm the dialog, return to the main window, and select Update Subscription or Update All Subscriptions. Wait for the completion message before selecting a server.
Do not start by changing advanced core parameters. Subscription parsing occurs before Xray or another selected core establishes a proxy connection. If the group remains empty immediately after saving, the first question is whether the URL request and response succeeded. Changing routing rules, TUN mode, or transport fields cannot repair a provider URL that returns an error page.
Choose the right group options
When v2rayN presents the group dialog, keep the initial configuration simple. The group name is for local organization, while the URL is the remote source. If the dialog includes a user-agent field, proxy-update option, or sorting preference, leave it at the provider’s recommended value unless the provider documents a requirement. A subscription can be valid in a browser but still fail in a client if the endpoint expects a particular request header or access method.
Multiple groups are useful when you maintain separate provider accounts, testing sources, or work and personal profiles. Give every group a distinct name. If two groups use the same URL, they may produce duplicate nodes and make troubleshooting harder. If you replace a provider, edit the existing group when you want to preserve its organization, or delete the old group when it is no longer valid. Removing a group may also remove the local profiles associated with it, so export or back up anything you need first.
Basic subscription group
- Source
- Provider-issued HTTPS URL
- Label
- Primary Provider
- Update
- Manual first, scheduled later
- Nodes
- Parsed from the response
Best for a first import because every variable remains easy to verify.
Separate testing group
- Source
- Second provider or test URL
- Label
- Temporary Test
- Update
- Manual when comparing results
- Nodes
- Kept apart from daily profiles
Useful for isolating provider quality without mixing profiles in the main list.
After the first successful update, inspect the resulting names and protocols. A normal list may contain VMess, VLESS, Trojan, or Shadowsocks entries, depending on what the provider publishes. VLESS + REALITY profiles commonly include a server address, port such as 443, UUID, SNI, public key, Short ID, and fingerprint. Those fields should arrive from the subscription parser; do not invent a public key or Short ID because the values are server-specific.
- Group label: Use a stable name that describes the source, not a temporary speed result.
- Update interval: Start with manual updates, then use a provider-compatible interval such as 60 minutes if scheduled updates are supported.
- Proxy update: Enable update-through-proxy only when direct requests fail and an already working profile is available.
- Duplicate control: Avoid saving the same URL under several names unless you intentionally need separate local handling.
- Backup: Preserve the application configuration before deleting a group or changing client editions.
Refresh profiles and select a server
Saving a subscription group does not always download its nodes automatically. Return to the main v2rayN window and use the subscription update command. Choose the specific group when you want to test one source, or use the update-all command when several groups have already been configured. A successful request should produce a completion notification, a changed update timestamp, or a refreshed node count depending on the build.
Once the profiles appear, select one entry in the server list. Start with a profile that has a complete name and recognizable protocol. Right-click the profile to find actions such as setting it as the active server, testing availability, copying its share link, or opening its details. Menu names differ by version, but the selected row and the active-server indicator should make the current choice clear.
A latency test is only a reachability indicator. It does not guarantee that every website, application, or protocol will work through that server. A node can respond to a TCP test while failing during TLS, REALITY authentication, DNS resolution, or destination routing. For a first functional test, select a profile, enable the system proxy, and open a simple HTTPS page. Then check the core log if the connection fails.
| Action | What to verify | Expected result |
|---|---|---|
| Update one group | The target group is selected | Only that group receives a new request |
| Update all groups | Each saved URL is still valid | Every group reports success or its own error |
| Set active server | The selected row is highlighted | New proxy connections use that profile |
| Enable system proxy | The local proxy switch is on | Proxy-aware desktop applications use v2rayN |
v2rayN commonly exposes a local SOCKS listener on port 10808, although the actual port depends on your configuration. HTTP proxy settings may use another local port. If a browser or application requires manual proxy configuration, use the exact protocol and port shown in v2rayN’s local proxy settings instead of copying a common example. Only one process can normally bind a particular port, so an existing proxy, development service, or security tool can cause a port conflict.
Why did the group save but show no nodes?
Saving stores the source; it does not prove that the endpoint returned parseable data. Run Update Subscription, inspect the result message, and confirm that the provider URL is complete and still authorized.
Should I update one group or all groups?
Update one group while testing a new URL so the error is isolated. Use Update All Subscriptions after every group has been verified and you want a routine refresh.
How do I know which server is active?
Look for the highlighted row or active marker in the server list, then check the tray menu’s current server entry. Selecting a profile in the list may only highlight it; use the explicit set-active action if required by your build.
Can I use the same group on another computer?
You can add the same provider URL on another trusted device, but the URL must be copied securely. Do not send it through public channels, and remember that provider account limits may apply.
Troubleshoot empty groups and update failures
Use a layered troubleshooting order. First verify the URL itself: copy it into a browser or another controlled HTTP tool only if doing so does not expose the credential to an unsafe environment. Check whether the response is a subscription payload rather than an HTML login page. A status such as 401 or 403 generally indicates authorization, expiration, or access-control trouble. A 404 suggests an incorrect path, while a timeout points toward DNS, firewall, routing, or provider availability.
Next compare direct and proxied updates. A provider may block the current network or require the request to come from a different route. If v2rayN already has one working node, enable the option that updates the subscription through the proxy, then retry the target group. Do not enable this blindly before any profile works, because the client would then depend on the very subscription it is trying to download.
Finally inspect the client and core logs. Parsing errors usually mean that the response format is unsupported, truncated, encoded unexpectedly, or actually an HTML page. Core connection errors occur later, after profiles have been created, and should be analyzed through the selected node’s address, port, transport, TLS, REALITY, DNS, and routing fields.
Error: subscription update timeout
Cause and fix: v2rayN could not complete the HTTP request. Check whether the URL opens on the current network, confirm DNS resolution, and retry through an already working proxy if the provider allows it.
Error: 401 Unauthorized or 403 Forbidden
Cause and fix: The provider rejected the request because the token expired, the account limit was reached, or access is restricted. Generate or copy a current subscription URL from the provider account.
Error: failed to parse subscription
Cause and fix: The response is not in a format that the selected parser understands. Check for an HTML login page, incomplete Base64 text, unsupported JSON, or a provider option intended for a different client.
Error: address already in use
Cause and fix: Another process is using the configured local port, commonly 10808 for SOCKS. Change the local port in v2rayN or stop the conflicting process, then restart the core.
Error: REALITY handshake failed
Cause and fix: The node was imported but its authentication parameters are invalid or the server is unreachable. Verify the public key, Short ID, SNI, fingerprint, system time, address, and port supplied by the provider.
If the group contains nodes but every connection fails, do not delete and re-add the subscription immediately. First test a different profile from the same group. If all profiles fail at the same time, the provider, account, or network path is a stronger suspect. If only one profile fails, compare its protocol and transport fields with a working profile. For VLESS + REALITY, a wrong SNI or public key is more significant than the local group name.
Build a maintainable daily workflow
Once the initial import works, keep the workflow predictable. Use one clearly named primary group, update it manually after a provider changes plans or credentials, and only then decide whether scheduled updates are useful. A 60-minute interval is a reasonable example for a desktop that stays running, but the provider’s own update policy and traffic limits take priority. Frequent requests may waste allowance without improving the node list.
Keep server selection separate from subscription maintenance. Updating a group changes its available profiles, while setting an active server determines which profile the core uses. After a refresh, the previously selected profile may have been removed or renamed. Check the active marker again instead of assuming that v2rayN will always retain the same server.
For everyday proxy use, confirm the local mode required by your applications. System proxy mode generally affects programs that honor Windows proxy settings. TUN mode works at a lower network level but introduces additional routing, DNS, and permission considerations. Use one mode at a time while testing, and avoid running another local proxy with the same listener ports. If only selected domains should use the proxy, review routing rules rather than changing the subscription URL.
- Before updating: confirm the group label and source URL, and avoid exposing the URL in logs.
- After updating: verify the node count, update timestamp, and presence of expected protocols such as VLESS or VMess.
- Before connecting: select a complete profile and confirm the active-server indicator.
- During testing: check the local port, system proxy state, and core log separately.
- Before changing editions: back up the v2rayN folder or export important profiles and settings.
- When a provider changes format: ask for a v2rayN-compatible subscription output instead of manually editing every imported node.
The most reliable v2rayN setup is not the one with the largest number of profiles. It is the one where the source URL is identifiable, the subscription group has a clear purpose, updates can be verified, and the active profile can be tested independently. After these checks are in place, routine maintenance becomes simple: update the group, select a valid server, confirm the local proxy mode, and use the logs only when one of those steps fails.