How to Add a Subscription Group in v2rayN: Step-by-Step Guide

What a Subscription Group Does

A subscription group is a saved set of update settings in v2rayN. It usually includes a name, a subscription URL, and optional update or routing preferences. When you refresh the group, v2rayN requests the latest profile data from the provider and adds or updates the corresponding server entries in the client. The group is a convenient way to keep those entries associated with one source; it is not itself a proxy server and does not create a service account.

Keep three items distinct: the provider account, the subscription URL, and the imported server profiles. The provider account controls what service is available to you. The URL is a private access link used by the client to fetch configuration data. The resulting profiles contain the connection settings that v2rayN can use with a supported core. A subscription can update successfully while a particular profile still fails to connect, because downloading profile data and connecting to a remote server are separate operations.

For setup, use the subscription URL supplied by a provider you trust. It is usually an HTTP or HTTPS address, sometimes with a long token in the query string. It is not necessarily the same as a single-server link such as a VMess or VLESS share link. A share link generally describes one profile; a subscription URL is intended to provide a list or feed that the client can refresh.

Menu wording and placement can vary between v2rayN releases and interface layouts. Look for the subscription-group settings or subscription-management entry in the main window. If the labels in your version differ, use the description of the action—adding or editing a subscription group—rather than assuming that every release uses the same menu path.

Add the Subscription Group

Before opening the settings, copy the complete subscription URL from the provider’s account page or setup instructions. Make sure it belongs to your account and has not expired. Avoid copying surrounding punctuation, spaces, or explanatory text. If the provider supplies more than one address, check which one is intended for a desktop client; a browser login link or a single-node share link may not be the subscription feed.

1. Open group settings

   In the v2rayN main window, open the subscription-group management or settings command. Depending on the release, it may be under a Subscription Group menu, a subscription button, or a settings dialog. Choose the action to add a group, rather than importing one server profile.

2. Name the group

   Enter a short name that identifies the source, such as “Personal” or “Work.” Names are labels for your own organization, not credentials. If you will add several feeds, use distinct names so you can tell which group supplied a profile later.

3. Paste the URL

   Paste the complete subscription address into the URL field. Check its beginning and end for missing characters, accidental spaces, or line breaks. Do not add quotation marks unless the provider explicitly includes them as part of the address.

4. Save the entry

   Save or confirm the group settings. If the dialog provides optional remarks or an update interval, leave unfamiliar options at their defaults for the first test. A simple baseline makes it easier to identify whether a problem comes from the URL, the network, or an optional setting.

5. Update the group

   Return to the main window, select the new group if required, and use the command to update or refresh that subscription. Wait for the result message and check whether profiles appear in the server list. If the update command is available from a right-click menu, confirm that the selected item is the group rather than an individual server.

After saving, reopen the group settings once and verify the name and URL. This catches a common setup mistake: pasting the address into a remarks field or editing an existing group unintentionally. If v2rayN displays a confirmation or update notification, read it before repeating the operation. Repeated refreshes do not repair an incorrect URL and can make it harder to distinguish the first useful error from later attempts.

Check the URL and Group Settings

Subscription addresses are usually long, so a visual scan is more reliable than trying to memorize them. Compare the saved value with the provider’s current account-page value, especially if the feed contains a token. The example below uses a reserved example domain and a deliberately redacted token; it is not a working subscription address.

https://provider.example/subscription?token=REDACTED

Do not post a subscription URL in a public chat, issue report, screenshot, or support message. Anyone who obtains a valid token may be able to retrieve the profiles associated with it, depending on the provider’s implementation. If the URL has been exposed, check whether the provider offers a way to reset or renew it. Redact the token before sharing diagnostic information.

Some providers offer multiple feed formats or parameters for different clients. Use the address specifically documented for v2rayN, and do not add query parameters based on guesses. If the provider supplies a conversion option, use its instructions rather than changing the URL manually. A syntactically valid HTTPS address can still return an error page, a sign-in page, or content in a format the client cannot parse.

When a group contains optional settings, change only one at a time and record the original value first. For an initial test, the essential values are the group’s identifying name and the correct feed URL. A successful fetch confirms that v2rayN can reach and interpret the feed; it does not confirm that each profile’s protocol, credentials, or remote server is currently working.

Organize and Refresh Multiple Groups

When you have more than one subscription, keep each provider feed in its own group. This makes it easier to tell which source supplied a profile and to refresh or remove one source without confusing it with another. Use names that remain clear in the server list, such as “Personal,” “Travel,” or the provider name. Avoid using the same label for separate feeds, even if they currently contain similar servers.

Choose an update method that fits how often the provider changes its profiles. If the client offers a manual update command, use it after adding a group and whenever you need to test whether the feed is reachable. If an automatic update interval is available, set a modest interval only after a manual update succeeds. Updating every few seconds is rarely useful and may trigger provider-side limits. The available interval options vary by v2rayN release, so follow the controls in your version rather than assuming a particular default.

• Keep sources separate: Add one group per distinct provider feed instead of combining several URLs into a single field.
• Use a naming convention: Include a purpose or provider label, but never put a password or subscription token in the group name.
• Refresh deliberately: Run a manual update when diagnosing a problem and note the result before changing settings.
• Review the server list: Check whether the expected profiles appeared and whether the entries belong to the group you intended to update.
• Remove obsolete sources carefully: Confirm which profiles came from the old group before deleting it, especially if you also added profiles manually.

Profile names can change when a provider updates its feed. A profile that disappears or is renamed is not necessarily a v2rayN failure; the provider may have changed its list. Conversely, seeing profiles in the list does not prove the latest update succeeded, because older entries may remain visible. Check the update result and the list together. If your version exposes timestamps, compare the most recent update time with the time you initiated the refresh.

For a clean test, start with one group and one profile. Select a profile from the updated list, start the client’s core, and test a site or connection method that you normally use. If the profile is unavailable or the connection fails, try another profile from the same group before changing subscription settings. This separates a feed-import problem from a single server or profile problem.

Troubleshoot Update Failures

An update failure can happen before v2rayN receives data, while it is reading the response, or after profiles have been imported but a connection test fails. Start with the message shown by the client and change one thing at a time. Check that the computer has network access, then verify the saved URL, and only then investigate proxy settings or provider status. The group can be configured correctly even when the provider’s server is temporarily unavailable.

• Connection timeout: Confirm that ordinary web access works, then try the update again. If the provider documents access restrictions, check whether your current network can reach its subscription endpoint. A timeout alone does not show whether the URL is mistyped or the endpoint is unreachable.
• HTTP error or access denied: Recheck whether the subscription has expired, reached an account limit, or needs renewal. Sign in to the provider’s account page directly and copy the current desktop subscription URL instead of reusing an old address.
• Update succeeds but no profiles appear: Confirm that the URL is a subscription feed, not a portal page, sign-in URL, or individual server link. Check the provider’s instructions for the expected client format and whether the account currently has profiles available.
• Profiles appear but cannot connect: The fetch worked, so test a second profile and inspect the client’s connection log. Check whether the selected profile is still active and whether its protocol and transport are supported by the core currently selected in v2rayN.
• Only some profiles are missing: Compare the current list with the provider’s account page or service notice. The provider may have removed, renamed, or filtered entries; avoid manually editing imported profiles until you know whether the change is expected.

If the update still fails, record the v2rayN release, the time of the attempt, the exact error text, and whether other websites load normally. Do not include the full subscription URL in a report; replace any private token with REDACTED. If you need to inspect logs, focus on the subscription request and response rather than publishing a complete configuration that may contain server addresses or credentials.

When the feed updates successfully but the core fails to start, troubleshoot that as a separate stage. Check the selected profile, the core log, and whether another local process is already using a required listening port. A subscription group does not set every local proxy option, and an imported profile may require a core version or feature that is not active in the current v2rayN setup.

Confirm the Result and Next Steps

A working setup has three observable outcomes: the group remains saved in the group list, an update completes without a fetch or parsing error, and one or more expected profiles appear in the server list. These checks confirm subscription management, not necessarily remote connectivity. Select a profile and test it separately; if the profile fails, compare another profile from the same group before editing the subscription URL.

For repeatable troubleshooting, write down the group name, update time, result message, and profile selected for the connection test. If you have multiple feeds, note which group supplied that profile. This small record prevents a common mix-up: refreshing one group while testing a similarly named server from another source. It also helps identify whether a later change came from a provider update, a new profile selection, or a local client setting.

For general setup help, continue with the usage guide. To choose a supported client package for your operating system, visit the download page. Keep the subscription URL private, and use the provider’s account instructions whenever feed format, access limits, or renewal rules are unclear.