How To Add A Subscription In v2rayN: Beginner Guide

What you need before adding a subscription

After installing v2rayN, the interface may look almost empty. That is normal. The application is the desktop client, but it does not provide proxy servers by itself. To create usable server profiles, you need a subscription URL from your service provider, or an individual share link such as vmess://, vless://, trojan://, or ss://. This guide focuses on the subscription workflow because it is the easiest way to manage several nodes at once.

A subscription is normally a web address that returns a list of server profiles. The provider can update that list without asking you to copy every node manually. A single share link, by contrast, represents one profile. Do not paste a single-node link into the subscription manager and do not assume that a provider dashboard page is itself a subscription URL. Look for wording such as “subscription,” “copy subscription,” or “subscription link.”

Before opening v2rayN, copy the complete URL into a temporary text field and check that it starts with http:// or https://. Avoid copying extra spaces, quotation marks, line breaks, or a shortened page address that only opens the provider website. If the provider supplies multiple links, use the one described for desktop clients or V2Ray-compatible applications. Keep the URL private: anyone who obtains it may be able to access your plan information or retrieve your node list.

It is also worth checking the basics first. Make sure your computer has a working internet connection, the system clock and time zone are correct, and v2rayN is allowed to access the network. A subscription update happens before a proxy node is selected, so it may need to reach the provider directly through your current connection.

Add the subscription URL in v2rayN

Open v2rayN and locate the subscription management area. In different releases, the wording may appear as “Subscription Group,” “Subscription Settings,” or a similar entry under the main menu. The exact position can change between versions, but the idea is the same: you are creating a named source for a group of nodes, not adding one server profile directly.

  1. Open the subscription management window from the v2rayN main menu.
  2. Choose the option to add a new subscription group or source.
  3. Enter a recognizable name, such as the provider name or plan name.
  4. Paste the complete subscription URL into the address or URL field.
  5. Save the entry, then close the settings window if the current version requires it.
  6. Use the subscription update command to download the nodes.

The name is for your local organization only. It does not change the provider account or the server list. Choose something short but meaningful, especially if you expect to add more than one subscription later. Names such as “Work plan,” “Travel,” or “Provider A” are easier to recognize than a long URL.

After saving, find the update command in the subscription menu. Some versions offer an option to update all subscriptions, while others let you update one selected group. For the first import, updating the specific group is clearer because you can immediately tell which source produced the new profiles. Wait for the operation to finish instead of clicking the command repeatedly. Repeated requests can make a slow provider appear to be broken and may trigger temporary rate limits.

If the update succeeds, the server list should contain newly imported profiles. The number of nodes depends on the provider and the subscription format. A successful update does not mean every node is usable; it only confirms that v2rayN fetched and parsed the subscription content. You still need to test and select a profile.

Refresh and check the imported nodes

When the subscription window reports success but the main list does not seem to change, refresh the server or profile view. Depending on the release, imported nodes may appear under a group, in the main server list, or after reopening the application. Do not immediately add the same URL again. First check whether the existing subscription group has a new update time or a larger node count.

Imported profiles often contain names supplied by the provider. They may include country codes, location names, bandwidth labels, or technical tags. These names are useful, but they are not a guarantee of speed, privacy, or availability. Treat them as labels for sorting and comparison rather than as proof that one node is better.

If no nodes appear, separate the possible causes:

  • The URL was not saved: reopen subscription management and confirm that the entry still exists.
  • The address is incomplete: copy it again from the provider and compare the beginning and ending characters.
  • The network cannot reach the provider: try another network, such as a mobile hotspot, then update once more.
  • The content is not compatible: the provider may be returning a format or encoding that this v2rayN version cannot parse.
  • The list is filtered: clear search terms or group filters in the main server view.
  • The subscription has expired: check the provider dashboard, account status, traffic balance, and expiration date.

Do not confuse an empty imported list with a connection failure. If the list is empty, focus on the URL, download request, response format, or filters. If profiles are visible but none connect, move on to latency tests, node selection, and proxy settings.

Organize subscription groups and profiles

Organization becomes important as soon as you use more than one subscription. Keeping every profile in one unstructured list makes it difficult to know which source is current and can lead you to test an old or duplicate node. Use a separate subscription group for each provider, plan, or purpose. This also makes future updates easier to understand.

Keep the subscription source separate from manual profiles. A profile downloaded from a subscription may be replaced or removed during a later update, while a manually imported node may have its own lifecycle. If you edit an imported profile, remember that a future subscription refresh could overwrite provider-controlled values. Store important custom settings outside the provider data when possible, and avoid changing transport, host, or security fields unless you understand why the change is needed.

Useful organization habits include:

  • Use one clear subscription name rather than creating several entries with the same URL.
  • Remove expired subscriptions so old nodes do not remain mixed with active ones.
  • Keep a manual test profile separate from automatically updated profiles.
  • Use the application’s group or filter features to narrow the list before testing.
  • Do not judge a subscription by its node count alone; a smaller list can be more stable.

If a provider gives you a subscription URL with a short expiration period, update it only when needed and record when it was copied. If the provider changes the URL, edit the existing subscription entry instead of adding a second group with an outdated address. This prevents duplicate profiles and makes later troubleshooting much faster.

Test latency and choose a node

Once nodes have been imported, select one or more profiles and run the latency or connectivity test available in your v2rayN version. A latency result usually measures how quickly the client receives a response from a test endpoint. It is useful for removing obviously unreachable nodes, but it is not a complete measurement of browsing quality. A node can respond quickly while being overloaded, unstable, or slow when downloading larger files.

Start with several different locations instead of testing only the first item in the list. Compare both the result and its consistency. A node that reports a moderate but repeatable delay may be more practical than one that briefly shows an excellent number and then times out. If the client provides a real connectivity test, prefer that over treating a numerical latency value as the final decision.

Use a simple selection process:

  1. Filter the list to a manageable group of profiles.
  2. Run a latency or connectivity test on several candidates.
  3. Remove profiles that consistently time out or fail.
  4. Choose a stable candidate with acceptable delay, not necessarily the lowest number.
  5. Test ordinary browsing or the application you actually need to use.

Testing can fail for reasons that do not mean the node is dead. The test endpoint may be blocked, the provider may limit repeated requests, or a local firewall may interfere. If every profile fails at the same time, check the subscription update, computer network, system time, and v2rayN core status before deleting the entire list. If only one or two profiles fail while others work, the problem is more likely profile-specific.

Select a profile and enable system proxy

After choosing a candidate, set it as the active server profile through the main server list. The selected item should be visibly marked in the interface. Selecting a node alone does not always send browser traffic through it. v2rayN usually separates the active server from the traffic mode, so you must also choose how desktop applications will use the proxy.

For a beginner’s first test, enable the system proxy option in v2rayN. This changes the operating system proxy settings so that browsers and applications that respect system proxy configuration can use the selected node. It is the simplest baseline because the behavior is easy to confirm: select a working profile, turn on system proxy, then open a browser and test a normal website.

Do not enable several proxy or VPN applications at the same time. Another client may overwrite the system proxy, occupy the same local port, or route traffic through a different profile. If the browser still uses the direct connection, check whether system proxy is actually enabled, whether the browser has its own proxy extension, and whether another network tool has taken control.

TUN mode can provide broader coverage for applications that ignore system proxy, but it introduces additional permissions, virtual network adapters, routing rules, and possible conflicts. Establish a working system-proxy baseline first. If a particular application bypasses the proxy while the browser works, investigate that application’s proxy behavior before switching modes blindly.

Keep the subscription healthy after the first setup

A subscription is not a one-time installation step. Nodes can expire, addresses can change, and providers can publish new profiles. Set a practical update routine based on the provider’s instructions. Updating too often is unnecessary, while never updating leaves you with stale nodes. If v2rayN supports scheduled updates, choose a moderate interval and avoid running updates during an important meeting, download, or other activity that depends on a stable connection.

When the connection stops working, use an orderly sequence: confirm the active profile, test another node, update the subscription once, check whether system proxy remains enabled, and then inspect local conflicts. Save error messages and note whether all nodes fail or only one group fails. This information is much more useful than repeatedly reinstalling v2rayN.

Finally, protect your subscription URL as you would protect an account credential. Do not post it in screenshots, public issue reports, or chat rooms. If you accidentally expose it, ask the provider whether the link can be reset. A clean setup is simple: one current subscription group, a few tested profiles, one selected node, and one clearly understood proxy mode.