First-time setup · About 10 minutes

v2rayN User Guide: From Subscription Import to Connection Verification

Complete four stages in order: import a subscription, choose a proxy mode, connect the configuration, and verify the exit connection. This guide focuses on the interface steps required for first-time use, without covering advanced routing or core parameters.

v2rayN Desktop v2rayNG Android Four Steps
QUICK START Setup Path
  1. 01
    Subscription Group Add the URL and update the list
  2. 02
    Proxy Mode Choose how traffic is handled
  3. 03
    Active Configuration Select a server and connect
  4. 04
    Verification Check websites, exit IP, and logs

Confirm the Client and Subscription Details

Before you begin, make sure the client is installed and that you have the subscription URL provided by your service provider. Use v2rayN on desktop devices and v2rayNG on Android devices. A subscription URL is usually a link beginning with https:// that lets the client retrieve a list of configurations. It is not an ordinary webpage to open in a browser, nor is it the same as a single server configuration.

Make sure the subscription URL was copied in full, with no extra spaces at either end. Chat apps may collapse long URLs, so use “Copy link” or copy the complete text instead of selecting only the visible portion manually. The URL updates the client’s configuration list and should be managed like account information, not posted in public discussions or screenshots.

If the client is not installed yet, go to the client downloads page and choose the appropriate platform. If the installed interface differs slightly from this guide, the layout was likely changed in a newer version: “Subscription” may appear as “Subscription Groups,” and the connection control may be in the main window or system tray. Search for the feature names used in this guide and continue with the setup.

Client is running You can open the main interface or configuration list
Subscription URL is complete No spaces at the beginning or end of the link
Basic network access works The device can currently retrieve the subscription
Step 01

Import a Subscription and Build the Server List

In the v2rayN desktop client, open the “Subscription Groups” or “Subscription” menu, enter the subscription settings, and choose Add. Give the subscription a recognizable note, such as the service name or its purpose, then paste the complete URL into the address field. The note only identifies the source on this device and does not affect connectivity. Confirm that the entry is enabled, save it, return to the main interface, and choose “Update All Subscriptions” or update the current group.

After the update completes, the main window should show configuration entries generated from the subscription. The list typically includes an alias, address, port, protocol type, and subscription group. For now, simply confirm that configurations appear; there is no need to edit transport, security, DNS, or core fields. The subscription already provides the parameters required for connection, and changing them individually during first-time setup can easily create inconsistencies.

In v2rayNG for Android, open the top-right menu and look for “Subscription Group Settings” or another entry mentioning subscriptions. Tap Add, enter a note, and paste the subscription URL. Save it, return to the configuration page, and update the subscription from the menu. When the update finishes, a set of selectable configuration cards should appear. If manual configurations already exist, use the note or group name to identify the newly imported entries.

If the list is still empty after saving, do not repeatedly create the same subscription. Return to the subscription settings and check whether the group is enabled and the URL is complete, then update it manually once. A network timeout in the client log means the device could not retrieve the subscription successfully; a format parsing error means you should recopy the original URL provided by the service. A URL opening in a browser does not guarantee that its contents are suitable for the current client. If parsing continues to fail, confirm the subscription type.

The criteria for completing this stage are clear: the subscription settings contain one enabled entry, the main interface shows at least one selectable configuration, and the update is no longer stuck in an error state. Once confirmed, continue to proxy mode selection.

Step 02

Choose a Proxy Mode and Traffic Scope

The proxy mode determines which requests the client handles. For first-time setup, use a mode based on routing rules. It separates requests that should use the proxy, connect directly, or be blocked, making it suitable for everyday browsing while preserving access to local network devices. The client may label it “Rules,” “Bypass LAN,” or a preset routing configuration. The key point is that it reads routing rules rather than sending every request through the same path.

Global mode sends a broader range of requests through the current active configuration. It is useful for temporarily checking whether a routing rule is keeping a particular website out of the proxy, but it does not need to be the permanent choice for a first connection. Direct mode sends requests straight to their destinations and is generally used to pause the proxy or check the local network; it cannot perform the proxy verification required by this guide.

In v2rayN, routing mode and the system proxy operate at different levels. Routing mode determines how requests are handled after entering the client; the system proxy determines whether browsers and applications that follow system settings hand their requests to v2rayN. Choose a rule-based routing configuration here, then enable the system proxy when connecting. Changing only the routing mode while leaving the system proxy off may leave the browser on its original direct path.

v2rayNG uses a device-level connection to carry application traffic, while routing rules still take effect inside the client. In Settings or Routing Settings, keep the default rule configuration suitable for everyday use. During first-time setup, avoid changing custom DNS, per-app proxying, bypass rules, and low-level network options at the same time. Establish a verifiable basic connection first, then adjust settings one by one as needed so it is easier to identify what affects the result.

First Use

Rule Mode

Handle different destinations according to routing rules while supporting everyday access and local network connections. The verification steps later in this guide use this mode as the baseline.

Temporary Troubleshooting

Global Mode

Send a broader range of traffic through the active configuration to determine whether a routing rule is affecting the target website.

Pause the Proxy

Direct Mode

Send requests directly to their destinations through the local network. Use it to restore ordinary networking or compare results, not to verify that the proxy is working.

Routing rules involve concepts such as domain matching, IP rules, inbound and outbound connections. You do not need to understand every field for a first connection. When you need to investigate rule priority, see the routing, traffic splitting, and DNS entries in the Terminology Handbook. Keep the rule mode after selecting it, then choose an active configuration and connect.

Step 03

Select a Configuration and Connect

Return to the server or configuration list and select a configuration generated by the subscription. In v2rayN, you can usually double-click a server, press Enter, or use the context menu to choose “Set as Active Server.” After selection, the row may show a highlight, check mark, or active status, and the system tray menu should display the current server name. Do not stop at merely highlighting a row; list focus and the active server are not always the same thing.

If the list contains many entries, use the client’s real connection test or batch testing feature to see which configurations can connect. Test results are only an initial filter; actual performance also depends on the target website, route load, and current network conditions. Continue with any configuration that passes the connection test rather than repeatedly comparing every entry during first-time setup.

After choosing the active server, enable the system proxy from v2rayN’s system proxy menu. Normally, the tray icon, status bar, or system proxy menu will show the corresponding state, and the log window will begin recording core startup and request details. If the program reports that the core did not start or that a port is already in use, close duplicate client instances and restart the current connection. Do not let multiple proxy programs control the same system proxy settings.

In v2rayNG, tap the target configuration card to make it current, then tap the circular connection button at the bottom of the page. During the first connection, the system displays a device connection authorization prompt; the client can carry application traffic only after you confirm it. Once authorized, the top status area or connection button shows a connected state, and a connection indicator appears in the system status bar. If it immediately returns to disconnected, open the log and review the latest errors, then confirm that the configuration came from the subscription you just updated.

After this stage, the desktop client should have both an active server selected and the system proxy enabled. On Android, the current configuration should be selected and the connection should be enabled. If only one condition is met, webpage results may not match expectations. Confirm the status, keep the client window open, and do not terminate its background process while you continue with connection verification.

Step 04

Verify Websites, Exit IP, and Client Logs

Use three levels of verification. First, check basic webpage access: open a new browser window and visit a familiar website that normally loads reliably. Confirm that local network access still works with the client enabled. This helps rule out basic issues such as complete DNS failure, an incorrect system proxy port, or an unexpected client exit. If no webpages open, check the connection status and logs before judging the server’s region or speed.

Second, check the exit IP. Open a familiar IP lookup page and note the public IP or region shown, then temporarily disable the system proxy or disconnect v2rayNG for comparison. Reconnect and refresh the page. If the exit information changes as expected for the configuration, browser requests are using the proxy path. Refresh the page or use a new private window during testing so cached content does not lead to a false result.

Third, review the logs. In v2rayN, view runtime records in the main window’s log area or the log menu; in v2rayNG, use the side menu or log entry to view recent requests. While verifying a webpage, the logs should show a new connection record and indicate that a request was handled by an outbound connection or routing rule. You do not need to understand every log line for this first guide. Just confirm that new records appear while the page loads and that repeated connection failures, DNS errors, or timeouts are not continuing.

If the client reports a normal connection but the exit IP does not change, first check that the system proxy is actually enabled and that the browser is not using separate proxy settings. Some applications do not follow the system proxy automatically and may require separate configuration or TUN mode. This is an advanced platform configuration covered in the All-Platform Guide. On Android, confirm that the system status bar still shows the connection indicator and check whether per-app settings are excluding the current application.

If only a specific website is inaccessible while other pages and the exit IP check work normally, the cause is more likely a routing rule, DNS resolution, or the target service itself. Temporarily switch to global mode for comparison: if global mode works but rule mode does not, check which routing rule matches the domain; if neither mode works, continue reviewing the connection logs and subscription status. Switch back to the original rule mode after testing.

Check 1 A familiar webpage opens
Check 2 Exit information changes
Check 3 New requests appear in the logs

When webpage access, exit information, and log records confirm one another, the first connection is complete. You can now keep the current subscription group, active server, and rule mode. To switch servers later, select another configuration from the list and set it as active; you generally do not need to add the subscription again.

Common Actions After Connecting

How should I update the subscription later?

When your service provider changes the configuration, update the subscription in the client to sync the list. In v2rayN, update by subscription group; in v2rayNG, update from the subscription menu. There is no need to delete the old group first. Deleting and recreating it can discard existing notes, filters, and group settings.

Why does the proxy work only in my browser after connecting?

Desktop applications support system proxies differently. Browsers that follow the system proxy usually work immediately, while some applications use separate network settings. Check the system proxy status first, then decide whether to configure the application’s own proxy entry or use TUN mode. See the All-Platform Guide for TUN permissions and conflict handling.

There are many servers in the list. Which one should I choose first?

Run a real connection test first to remove configurations that cannot connect, then choose based on the target region, traffic multiplier, and actual browsing performance. Latency is only one filter and does not by itself indicate download speed or peak-time stability. For first-time verification, a usable configuration matters more than chasing the lowest number.

Will updating the subscription overwrite manual settings?

Server parameters generated by a subscription are normally synchronized with the remote content during updates, so they are not suitable for long-term direct editing. Client-level settings such as routing, the system proxy, and interface preferences are generally stored separately. If you need to keep custom server parameters, duplicate the configuration and use a clear note to distinguish it.

Move from a Basic Connection to Platform Configuration

After the first connection works, read the structured documentation when you need to configure startup behavior, TUN, DNS, subscription groups, or platform permissions. Terminology and platform procedures are organized separately so you can go straight to the relevant section.