Advanced 13-minute read

v2rayN Add Subscription Guide: Step-by-Step Node Setup

A practical v2rayN walkthrough for beginners who have installed the app but are unsure how to import a provider link. Follow the menu path to create a group, update servers, and fix common subscription problems.

Before you add a subscription

A v2rayN subscription is a provider URL that contains one or more server profiles. Instead of entering every address, port, UUID, transport, and security field by hand, you add the URL once and let v2rayN download the current node list. When the provider changes a server, removes an expired node, or adds a new region, updating the subscription can refresh the local profiles without rebuilding them manually.

This guide assumes that v2rayN is already installed and opens normally on Windows. The exact wording of a menu can differ slightly between v2rayN releases or language settings, but the usual path is Subscription group → Subscription group settings. You will need the subscription URL supplied by your provider. A single share link such as vmess:// or vless:// is different: it normally represents one node, while a subscription URL is intended to return a list of nodes.

Quick summary

Create a subscription group, paste the provider URL into the group settings, save it, update the group, and then test one imported node. This workflow avoids manual protocol editing and gives you a clear place to check failures such as an expired link, an incorrect update mode, or a blocked request.

5
setup steps
10808
common SOCKS port
10809
common HTTP port
3
checks before troubleshooting

Create a subscription group

Start v2rayN and open the subscription management window from the main interface. In common releases, choose Subscription group from the top menu, then select Subscription group settings. Some translations display a shorter label such as Subscription settings. The goal is the window that lists subscription groups and provides an +, Add, or New control.

  1. Open group settings

    In the main v2rayN window, choose Subscription group → Subscription group settings. Do not use the separate node import command when you are adding a provider URL.

  2. Add a group

    Click + or Add, enter a recognizable remark such as Provider-main, and keep the group enabled for updates.

  3. Paste the URL

    Paste the complete subscription address into the URL field. Include the scheme, path, query string, and any access token supplied by the provider.

  4. Save the entry

    Click Confirm, Save, or the equivalent button. Check that the new group remains visible after the settings window closes.

  5. Update the group

    Return to the main window, open Subscription group, select the new group, and choose Update subscription or Update subscriptions.

Use a short group name that describes the provider or purpose rather than the current server location. For example, Work devices, Personal backup, or Provider-A remains useful after the provider changes individual nodes. If you use more than one subscription, create one group per provider. Keeping groups separate makes it easier to identify which URL failed and prevents an update from mixing unrelated profiles.

After saving, verify the URL character by character. Common copy errors include a missing final character, a leading or trailing space, a line break inserted in the middle, or copying the label next to the URL instead of the URL itself. Do not add https:// to a link that already begins with another scheme, and do not convert a provider link into a browser search. If the provider gives a QR code, use the provider's stated method to obtain the complete link before adding it to v2rayN.

Update and select an imported node

Once the group exists, update it from the subscription menu. Depending on the v2rayN release, you may see one command for updating the selected group and another for updating all groups. Start with the selected group. This produces a smaller and more readable log, and it confirms that the URL you just entered is the one being requested.

  • Wait for the update notification or log message before closing v2rayN.
  • Look for a change in the node list, such as newly imported profiles or updated remarks.
  • Click a node once to select it; do not confuse selection with starting the core.
  • Use the context menu or the main start command to launch the selected profile.
  • Run a latency test only after the profile has imported successfully.

A successful subscription update does not mean every node is reachable. It means that v2rayN received and parsed the provider response. The provider may return nodes in several protocol families, including VMess, VLESS, Trojan, or Shadowsocks. Keep each imported profile unchanged at first. The address, port, UUID or password, transport, TLS or REALITY settings, SNI, path, and flow settings are normally a matched set supplied by the server.

Item to check What it means Recommended action
Group name Identifies which provider entry will be updated Use a unique name and select the intended group before updating
Subscription URL Address used to retrieve the node list Paste the complete current URL and do not remove its query parameters
Imported profile A parsed node with protocol and transport fields Test it as imported instead of changing one field at a time
Core type Engine that handles the profile Use the core required by the profile, especially for newer Xray features

For a first test, choose a node with a clear provider remark and a nearby region rather than the most distant or heavily loaded option. Check latency, then open a small number of ordinary websites. If the connection works but performance is poor, compare two or three nodes from the same group. A latency result alone does not measure throughput, packet loss, congestion, or the quality of long-lived connections.

Practical conclusion: test the imported profile before editing it

If a provider-supplied node connects successfully, preserve its original fields. Manual edits often turn a valid VLESS, VMess, or Trojan profile into a client-server mismatch that is harder to diagnose than the original problem.

Understand local proxy settings and core behavior

v2rayN normally exposes local proxy ports on the computer so applications can send traffic to the running core. A common default arrangement is SOCKS on 127.0.0.1:10808 and HTTP on 127.0.0.1:10809, but the actual values can differ after installation or manual changes. Check the current values in v2rayN's settings rather than assuming the defaults. A browser configured for port 10809 will not work if v2rayN is listening on another port.

The system proxy switch and the core start state are separate concepts. Starting the core creates the local forwarding service; enabling the system proxy tells supported Windows applications where to send web traffic. If the core is running but the system proxy is disabled, a browser using system settings may continue to connect directly. If the system proxy is enabled while the core is stopped, applications may report that the proxy server refused the connection.

A clean first-test arrangement

v2rayN side
  • Select one imported node
  • Start the core
  • Confirm the local port values
Windows side
  • Enable the system proxy if needed
  • Close competing proxy tools
  • Test one browser first

Use one client and one selected node during the first test; adding another proxy layer makes port and routing errors much harder to isolate.

Core selection matters when the subscription contains features that older engines cannot parse. A VLESS profile using REALITY or Vision flow control generally requires a compatible Xray core. A legacy VMess profile may work with a broader range of cores, but compatibility still depends on the transport and security parameters. If v2rayN imports a profile but shows a core error when starting it, check the selected core type and the core log before changing the node fields.

Do not treat a browser's successful page load as proof that every application is proxied. Some programs ignore the Windows system proxy, use their own network stack, or require a TUN-based configuration for traffic capture. First confirm the v2rayN core and one supported browser path. Only then investigate application-specific routing, DNS behavior, or firewall rules.

Fix common subscription failures

When an update fails, identify whether the problem occurs while downloading the provider response or after v2rayN parses the response. A timeout, DNS failure, or TLS error points to access to the subscription URL. A successful download followed by zero nodes or malformed profiles points to the response format, an expired link, or an unsupported encoding. This distinction prevents repeated changes to the wrong setting.

Error: request timeout

Cause and fix: The computer cannot complete the request to the subscription host. Confirm that ordinary web access works, try the provider's alternate URL if available, and test updating through an already working proxy when the client offers that option.

Error: 401 Unauthorized or 403 Forbidden

Cause and fix: The access token may be expired, revoked, or copied incorrectly. Obtain a fresh subscription URL from the provider and replace the old group entry instead of repeatedly retrying the same link.

Error: no nodes found

Cause and fix: The response may be an HTML login page, an empty account response, or a format v2rayN cannot parse. Open the provider's account panel, confirm that the subscription is active, and ask for a v2rayN-compatible link format.

Error: failed to start core

Cause and fix: The selected core may not support a profile field, or another process may already occupy the local port. Check the core log, switch to the provider-required core, and inspect port conflicts before editing the profile.

Error: connection refused at 127.0.0.1

Cause and fix: An application is pointing to a local proxy port where v2rayN is not listening. Compare the application's proxy port with v2rayN's current SOCKS or HTTP setting and make sure the core is running.

If subscription updates work only when another proxy is active, use the update-through-proxy option carefully. First start a known-good node, then enable the setting in the subscription group or update dialog, and retry the selected group. Do not apply a proxy-dependent update rule to every group before confirming that one group updates correctly. Otherwise, a failed primary group can prevent you from refreshing the backup group needed for recovery.

Why did the group save but show no nodes?

Saving stores the URL; it does not download profiles. Select the group and run Update subscription, then check the update result and node list.

Should I paste a single VMess link into group settings?

No. Use the individual node import function for one share link. Use group settings for a provider URL that returns multiple profiles.

Why does the core start but the browser stay offline?

Check whether the system proxy is enabled and whether the browser uses the same HTTP port shown by v2rayN, commonly 127.0.0.1:10809.

Why did an update remove an old node?

The provider controls the subscription result. The node may have expired or been removed; keep an independent backup only if the provider permits it.

Maintain subscription groups safely

After the first successful update, establish a simple maintenance routine. Update the selected group when the provider announces a server change, and use update-all only when you have several groups that should be refreshed together. Remove duplicate or expired groups from the settings window so that you do not accidentally test an obsolete URL. If a provider gives separate links for different device limits, name them clearly rather than storing them under one ambiguous label.

Keep the v2rayN application and its configured core current enough to support the protocol features used by your provider, but do not upgrade blindly in the middle of an important session. Before changing the core, note the current core type, local ports, selected node, and whether the system proxy is enabled. After an update, test the same node again. If behavior changes, the recorded values provide a useful comparison point.

  • Keep one working node selected as a baseline for later tests.
  • Do not expose subscription URLs in screenshots or diagnostic logs.
  • Update one group first when several providers are configured.
  • Record the core error before deleting a profile that fails to start.
  • Use the provider's current link when a token or account status changes.

For a new installation, the complete sequence is therefore straightforward: create a named group, paste the complete provider URL, save it, update the selected group, start a compatible core, and test one imported node through the local proxy. If the update fails, separate URL access from profile parsing; if the node imports but will not connect, inspect core compatibility and server parameters; if the core works but applications do not, check the system proxy and local port. This approach keeps subscription management predictable without requiring beginners to manually rewrite protocol configurations.

Download v2rayN