For your first import, save the full subscription URL to a group, then update it manually. You don't need to Base64-decode the URL; Base64 may be used to encode the content returned by the server. If the list is still empty after saving, check which group you updated, whether the request succeeded, and whether the response could be parsed.
Import a subscription in v2rayN: add a group, then update it
In the v2rayN 7.x desktop app, open the Subscription Groups menu at the top of the main window. Choose Subscription Group Settings to save the URL; Update Current Subscription sends a request to that URL. If you see the new group but no nodes, you probably haven't updated it yet.
-
Copy the subscription URL
Copy the subscription URL intended for client use from your provider's account page. Don't copy the logged-in management page URL or substitute a
vmess://orvless://share link. Keep any query parameters after the question mark, and remove spaces or line breaks introduced during copying. -
Create a subscription group
In the main window, open Subscription Groups → Subscription Group Settings → Add. Enter a name, then paste the full URL into the Optional Address field; some versions label it Address or URL. If there's an Enable Updates option, make sure it's checked, then save.
-
Update the current group
Return to the main window, select the new group, then choose Subscription Groups → Update Current Subscription (without proxy). Use this if your current network can reach the subscription URL directly. If the URL requires a proxy, first make sure an existing proxy works, then choose Update Current Subscription (through proxy).
-
Check the import
After the update, stay on the new group and check its list, along with any log or status message in the main window. For a first import, update only the current group rather than all groups so any error is easier to trace. Once nodes appear, test their connections separately.
Import a subscription in v2rayNG: group settings and update menu
On Android, the options to save a subscription and update it are usually in different menus. Open group settings from the top-left menu and save the URL. Return to the main list, then start the update from the top-right menu.
- Open group settings: From the top-left corner of the main screen, tap “☰” → “Subscription Group Settings.” Some versions shorten this to “Subscription Groups.”
- Save the URL: On the group settings screen, tap “+” in the top-right corner, enter a name, and paste the subscription URL. Tap the checkmark in the top-right corner to save. Don't import a subscription URL as a node configuration from the “+” menu on the main list.
- Return to the main screen and update: Select the new group, then tap “⋮” → “Update Subscription” in the top-right corner. If your version offers separate options for the current group and all groups, update only the current group first so you can check the result.
- Check which group contains the nodes: After updating, return to the group you just added and check its list. If nodes appear under “All” but the new group is empty, make sure those nodes weren't already imported. Don't mistake old entries for a successful update.
Base64 subscriptions, plain-text link lists, and single-node links
A subscription URL is the address the client requests each time it updates. Base64 and plain text are two possible response formats. With a Base64-encoded list, the client usually decodes the response before parsing the share links line by line. A plain-text list can be parsed directly. Even when the outer list is plain text, an individual vmess:// link may contain Base64-encoded parameters. Treat these as separate encoding layers.
Base64-encoded link list
RecommendedThe provider encodes the entire newline-separated link list, which the client decodes after fetching it. If the provider says this subscription format works with your client, add the corresponding URL directly. Don't paste the response body into the URL field.
Best for: Providers offering a Base64 subscription format supported by both clients, with updates as needed.
Plain-text link list
The response body contains share links such as vmess:// or vless://, usually one per line. If the client can parse this output, the update should work. If the clients return different results, check their versions and compare the actual responses.
Best for: Providers that explicitly support plain-text output, when you need to check the link type on each line.
Single-node share link
Copy a link that starts with a protocol name, then import it using the client's clipboard import feature. This imports the node configuration as it is at that moment; it doesn't create a subscription group. If the address or port changes, get a new link and import it again.
Best for: Importing a single configuration without needing bulk subscription updates.
Base64 is encoding, not encryption. Query parameters in a subscription URL may contain an access token, and the decoded node list may contain connection credentials. When asking for help, share only the client version, status code, and a redacted message. Never post the full URL, raw response, or decoded content.
Update failed, no nodes found, or imported nodes won't connect
Troubleshoot in this order: did the client receive a response, is it a node list, and can the nodes connect? An HTTP status code describes what happened to the subscription request; it doesn't show whether a node works. The numbers below are status codes, not speed-test results.
- Timeout or no status code: First check whether your current network can resolve the subscription domain. Then confirm whether the client is updating directly or through an existing proxy. If you see a certificate error, check the device's date and time and review the certificate warning. Don't bypass the error by disabling certificate verification.
- Response is 401, 403, or 429: For a 401 or 403, copy the subscription URL from the provider again and check whether it has expired and whether your account still has access. For a 429, wait as instructed in the response before trying again. Don't repeatedly refresh on both desktop and Android.
- Response is 200 but no nodes appear: Check whether the response body is a login page, an error page, or an empty list. Opening the URL in a browser doesn't prove the client can fetch the subscription: the browser may be logged in, and the two may receive different content. If the provider offers multiple export options, choose a link-list format explicitly supported by your client.
- The group has nodes, but connections fail: The subscription imported successfully. Next, check whether the selected node's protocol, transport, and security settings are compatible with the client core. Test one node and review the connection log. Refreshing the subscription usually won't fix an error that occurs while connecting.
Using the same subscription on desktop and Android
Save the same URL in both clients only if the provider allows it and both clients support the same output format. Each client manages its own group names, update schedule, and selected node. Saving the same URL doesn't sync these settings.
Verify the same subscription on both clients
Desktop: v2rayN
- Update from the new group, then note the result and number of entries. Don't include nodes from an older group.
- Check whether the update uses a direct connection or an existing proxy so you don't mistake a network difference for a format difference.
Android: v2rayNG
- Update manually at around the same time, and check the group for that subscription rather than the “All” list.
- If some entries appear only on desktop, first check the client version and group filters, then ask whether the provider returns different content depending on the client.
Different entry counts don't necessarily mean the import failed. Compare the update messages and the specific missing entries from the same update, then check whether the response differed, filters were different, or some links couldn't be parsed.