V2Ray Setup Guide: From Subscription Import to Connection Verification

The goal of importing a subscription is not merely to save its URL in the client. The client must successfully read the remote content and turn its configurations into selectable server entries. When complete, you should see server names, protocol types, or a subscription group—not just a subscription URL. If the list is still empty, do not move on to proxy mode settings; there is no active server to connect to yet.

v2rayN desktop instructions

Open the v2rayN main window, find the subscription-group option in the top menu, and add a new subscription. Enter a recognizable name such as “Primary subscription,” then paste the complete subscription link into the URL field. Check that there are no spaces at either end, then save. Saving only records the source; you still need to update it from the subscription-group menu. Keep the network available while v2rayN requests and parses the content.

After a successful update, several configuration rows should appear in the server list. Open the subscription group to confirm that the entries belong to the source you just added. If the window is still empty, run the update again. For request or parsing errors, check whether the link was copied completely, the subscription has expired, and the current network can reach the source. Do not repeatedly change protocol, security, or transport settings before the subscription has been parsed; those parameters have not entered the client yet.

v2rayNG Android instructions

Open v2rayNG, go to Subscription settings from the top-right menu, and create a subscription entry. Add a recognizable note, long-press the URL field to paste the complete link, and save it. Return to the configuration list and use the menu to update subscriptions. Some versions return to the list after updating, while others show a brief result message; the key sign of success is that selectable entries appear in the configuration list.

If the provider gives you a single sharing link beginning with vmess://, vless://, trojan://, or ss:// instead of a subscription URL, use an option such as “Import from clipboard” to add that configuration. A single imported link does not provide automatic subscription updates, so you must import it again when the service parameters change. For long-term use, save the subscription URL provided by the service so it can be updated centrally.

Confirm the result

This step is complete when the client contains a subscription group with at least one selectable server configuration. Do not judge speed by the name or make bulk changes yet. Select one entry as the test server for the next step. To understand the relationship between subscriptions, nodes, and server configurations, see subscription and node terminology, then return to Step 2.

Before connecting, three conditions should be met: the subscription updated successfully, servers appear in the list, and the proxy mode is set. Now choose one configuration as the active server. A server name is only a provider-supplied label and does not prove that the configuration works. The real tests are whether the core starts, the handshake completes, and the target app can reach its destination through the current routing rules.

v2rayN desktop connection

Click the target entry in the server list, then use the context menu or press Enter to set it as the active server. The selected entry usually changes color, font, or status marker. Next, open the system proxy menu and choose “Set system proxy automatically” or the equivalent enable option in your version. This points the system proxy to v2rayN's local listening port, allowing browsers and apps that follow system proxy settings to send requests to the client.

Afterward, check the status at the bottom of the window or the tray icon to confirm that the core has started. If the client reports that a port is already in use, another program is using the same local port; exit the old proxy client and restart v2rayN. If the core stops immediately after starting, open the logs and inspect the first error rather than only the last line. Invalid configuration, an unreachable destination, and a local port conflict require different fixes; the first clear error is usually closest to the cause.

Some apps do not read system proxy settings and may remain on a direct connection even when v2rayN is connected. For the first test, use a browser that follows the system proxy to confirm the basic path. To intercept more programs, see TUN and platform-specific settings in the complete guide; do not add extra network layers during the initial connection.

v2rayNG Android connection

Select a server in the configuration list and confirm that it is marked as the current configuration, then tap the connection switch on the main screen. The first time Android creates a local VPN tunnel, it displays an authorization dialog. Approve it so the client can handle network requests from the selected apps. Return to the main screen; the switch and status area should show that the connection is active, and the system status bar will usually display a connection indicator.

If the connection quickly returns to a disconnected state, open the logs and inspect the core startup messages. Common causes include expired configuration parameters, incomplete subscription parsing, an unreachable server, or a battery-saving policy that stops the background process too soon. Keep v2rayNG in the foreground for one browser test first. Once the basic connection works, adjust the device settings to allow continued background operation. Background persistence is a device-management issue, not something to fix by repeatedly changing protocol fields.

Do not run bulk speed tests yet

The priority during first-time setup is confirming that one normal request can complete. Bulk speed tests contact multiple servers at once, and their results are easily affected by the current network, server load, and test destinations. Complete Step 4 with one server first; if it fails, compare it with another entry from the same subscription. If several entries fail at the same stage, the issue is more likely the subscription source, local network, system proxy, or client settings than one server name.