Have a URL but aren’t sure where to import it? First identify whether it’s a subscription URL, a single-node share link, or a link to a YAML config. This guide covers subscription groups, manual updates, and node checks in v2rayN and v2rayNG—and explains how to tell connection failures from format and response issues.
Subscription URLs, Base64 Lists, and Single-Node Share Links
A subscription URL is a URL the client requests periodically; a share link describes a single node. A URL beginning with https:// only tells you it points to a web resource. The prefix alone can’t tell you whether it returns a node list, a config file, or a login page. Copy the dedicated subscription URL from your provider’s dashboard—not the dashboard page URL from your browser’s address bar.
Client-Compatible Node List Subscription
RecommendedCommon responses contain node share links, one per line, or the entire list encoded as Base64. The client requests the subscription URL, parses the response, and adds recognized entries to a group. Base64 is an encoding, not encryption; don’t share readable node details or their encoded text publicly.
Best for: Keeping a set of nodes up to date using the same subscription URL
Single-Node Share Link
Text beginning with vmess:// or vless:// is usually a node share link. Import it from the clipboard rather than entering it as a subscription URL. A VMess share link may contain Base64 text after its prefix, but it describes one node—not a subscription with multiple nodes.
Best for: Adding a known node or checking whether the client can parse a single node’s protocol
Clash YAML Config
Common config fields include proxies:, proxy-groups:, and rules:. Even if the config uses familiar protocol names, that doesn’t mean a standard subscription field can import the whole file. Renaming the YAML file or encoding it as Base64 won’t turn it into a list of node share links.
Best for: Using YAML groups and rules through a compatible config import feature; for standard subscriptions in these clients, use a provider’s v2rayN- or v2rayNG-compatible URL
v2rayN Desktop: Add a Group and Update the Subscription
These steps are based on the commonly used Simplified Chinese interface in v2rayN 7.x. Saving a group only stores the subscription URL; it doesn’t download any nodes. For the first import, update the current group rather than all groups so it’s easier to match any errors in the log to the URL you just added.
Open Group Settings
In the main window, select “Subscription Group” → “Subscription Group Settings,” then click “Add.” If there’s a “+” next to the group tabs, you can use it to open the add dialog instead.
Enter the Subscription URL
Enter a recognizable name under “Remarks” and paste the full URL into “Optional Address.” Some builds label this field “Address.” Keep any query parameters after the question mark. Don’t copy just the domain, or include any instructional text from the page. Click “OK” to save.
Update the Current Group
Select the new group tab, then choose “Subscription Group” → “Update Current Subscription (No Proxy).” If the subscription endpoint is only reachable through a proxy you know works, choose “Update Current Subscription (Via Proxy)” from the same menu. Without a working node, the second option won’t fix a connection problem during the initial update.
Check the Node List
Check whether entries appear in the current group and review the update log. If the list already contained old nodes, a non-empty list alone doesn’t mean the update succeeded—make sure the latest request didn’t fail. Then test a node in the new group and enable the system proxy if needed once you’ve confirmed the node works.
v2rayNG on Android: Save a Subscription and Refresh the List
These steps use the menus commonly found in v2rayNG 1.9.x. The “+” in the top-right corner of the config list is often for adding a node; save subscription URLs in a subscription group instead. Menu labels may vary slightly between versions, so follow the options shown in your app.
- Open the menu in the top-left and select “Subscription Group Settings”; some versions call this “Subscription Settings.” Tap “+” in the top-right, enter a remark and the full subscription URL, then tap the check mark to save.
- Return to the config list and switch to the new group. In the “⋮” menu at the top-right, select “Update Subscription.” If your version offers separate options for updating the current group or all subscriptions, update the current group first so you can confirm which URL was refreshed.
- Wait for the update message to finish and confirm that entries appear in the group. Select a config and tap the start button at the bottom. The first time you start, Android will ask to set up a VPN connection; confirm to let the app route device traffic in VPN mode. The VPN doesn’t need to be running while the subscription updates.
- If you have a single-node share link instead, copy the entire link, return to the config list, and tap “+” → “Import from clipboard.” There’s no need to create a subscription group. After importing, check that the new entry’s name, protocol, and server look right.
Subscription Update Failed? Check the Request, Then the Format
If the client reports an HTTP status code, use it to check whether the request reached the server and whether the server accepted it. These numbers are status codes, not node counts or speed test results. A timeout or DNS lookup failure may mean the client never received an HTTP response.
It Keeps Timing Out. Is the Format Wrong?
For a timeout, check the network first rather than switching formats. Try updating the current group on another working network using the same device. Check the system date and time, and look for DNS or certificate errors in the log. If a direct request fails and you have a working proxy, try updating through the proxy in v2rayN for comparison.
The Server Returns 200, but Why Are There No Nodes?
Make sure you copied the dedicated subscription URL. Some URLs redirect to a login page that still returns HTTP 200, so the client receives HTML instead of a node list. If your provider labels the link as YAML, choose the v2rayN- or v2rayNG-compatible format in the dashboard, then update the current group.
It Updated Yesterday. Why Am I Getting a 401 or 403 Today?
First check the provider’s dashboard to confirm that the subscription is active, the URL hasn’t been reset, and you copied all its parameters. If you have a new URL, edit the existing group and update it again. If the full new URL still fails, send the provider the status code and time of the error. Never post a URL containing a token in a public comment.
Why Are Some Nodes Missing on My Phone?
First confirm that both devices use the same subscription output and that you’ve selected the corresponding group. Some services return different content depending on the client identifier; individual entries may also be skipped if their link format or protocol parameters aren’t supported. Comparing update logs and the protocols of missing entries is more useful than repeatedly creating new groups.
The Nodes Imported, but Why Won’t Websites Load?
Check the connection rather than importing again. Make sure the system proxy is enabled on desktop or the VPN is running on Android, then try another node in the same group. If only certain entries fail, check their transport and TLS settings. If the entire group fails, check the core log and device network.
Subscription Updates and URL Security
A group identifies the source used for updates; it isn’t a node backup. When refreshing a subscription, the client may replace existing entries with the server’s latest list. If you need to keep manually edited settings, copy the node first and put the copy in a separate group to prevent the next refresh from overwriting your changes.
- Changing the URL: Edit the existing group, then update it and verify the new list. Avoid creating multiple groups with the same URL while troubleshooting, or you may accidentally select a node from an outdated group.
- Sharing logs: Include the client version, time of the error, and error type. Redact the full subscription URL, its query parameters, and any single-node share links. Check the address bar and config details in screenshots, too.
- URL shared by mistake: If your provider lets you reset the subscription token, do so in the dashboard, then replace the group URL in both desktop and Android clients. Deleting a public message won’t invalidate a URL that’s already been exposed.