Quick Start Guide

v2rayN Setup Guide

From importing a subscription to testing the connection. For your first setup, choose one server, one test app, and one destination so you can check each step.

Before you begin, make sure the client is installed, your network is working, and you have the full subscription URL from your provider. If you still need to install a client, choose one on the download page.

Step 1 · Server List

Import and Update a Subscription

Open v2rayN and find Subscription Group at the top of the main window. Open Subscription Group Settings or a similarly named option. Add a group, enter a recognizable name in the remarks field, and paste the full URL into the subscription address field. Check that there are no spaces or line breaks at either end, and that you copied the entire link. Save, return to the main window, and select the new group. If the group name appears but the list is empty, it usually just needs an update: saving the URL and fetching the server list are separate actions.

From the Subscription Group menu, select Update Current Subscription. For a first-time setup, if your network can access the subscription URL directly, choose the option to update without using the client proxy; there is no working proxy connection yet. When the update finishes, check that server entries appear in the group. Remarks, addresses, or protocol fields show that the client has read recognizable entries, but do not confirm that a server can connect. Note one entry to test later; there is no need to test every server now.

If the list is still empty after updating, first check that the selected group is the one you updated, then look in the logs for network errors or parsing messages. A connection timeout usually means you should check whether your current network can reach the subscription URL. If content was received but parsing failed, check whether the link leads to a login page or whether your provider supplied a subscription format supported by this client. Do not use an account dashboard URL as a subscription URL, and never post the full link publicly while troubleshooting. Hide the subscription URL and server credentials before sharing screenshots.

In v2rayNG, open the subscription group settings from the main screen menu, add and save the URL, then return to the list and select Update Subscription from the menu. Once entries appear, find the imported server from the list or group selector. At this point, both clients have only imported server details; next, choose how the test app's traffic reaches the client.

Step 2 · App Traffic and Routing

Choose a Proxy Mode and Routing Rules

Treat the system proxy and routing rules as two separate things. The system proxy determines whether apps that follow system settings send requests to the client. Routing rules determine which outbound a request uses after it reaches the client. Even with global proxy routing, an app that ignores system proxy settings may never send its requests to the client. Conversely, a browser using the client does not mean every destination goes through the remote server: requests matching a direct rule may still connect directly.

For your first desktop test, leave Tun off and use a browser that follows system proxy settings. Open the client's routing menu, check the active rule group, and choose a test destination that should clearly use the proxy. Keep the current group if it already has a suitable rule. If you are unsure whether the destination matches, you can briefly switch to global routing on a device where changing proxy policy is allowed, then switch back after testing. Global routing only affects requests that reach the client; it does not take over the entire device's network.

If the device already uses a work proxy or another network client, note the current settings and avoid letting multiple tools change the system proxy at once. For now, just choose the option you plan to use. After selecting a server and confirming the core has started, choose Auto Configure System Proxy. The menu option Do Not Change System Proxy means the client will leave existing settings alone; it does not undo a proxy set earlier. For the difference between this and Clear System Proxy, see the basics FAQ.

On Android, the system VPN interface handles app traffic, so there is no need to copy the desktop tray settings. If you previously set per-app proxying in v2rayNG, make sure the test browser is included in the current scope: include it when proxying selected apps, and make sure it is not on the exclusion list when bypassing selected apps. Keep the scope unchanged for the first test, then adjust it if needed. Once connected, see the routing configuration reference for details on routing and DNS.

Step 3 · Select an Active Server

Select a Server and Connect

Return to the v2rayN server list and find the entry you noted in step 1. Right-click it and set it as the active server. If your version uses double-click to activate, double-click the entry and check for an active marker. A single click usually just selects a row; it does not switch the server in use. Afterward, check that the active server shown in the main window or status bar is the one you expect. If you select another entry later, confirm that the active server actually changes.

Next, check the log area in the main window for persistent messages about startup failures, incompatible configuration, or a busy local port. If the core starts, the client can accept local requests. Some remote connections are only established when an app sends a request, so this alone does not confirm that the server works. If the logs show a port conflict, check whether another client instance is running or another proxy is listening on the same port. Avoid changing the local port and switching servers at the same time, or it will be hard to tell which change affected the result.

Once you confirm that the core started without errors, choose Auto Configure System Proxy from the system tray or the client's system proxy menu, then check that the option is selected. If your test browser is already open, open a new window. If it is reusing an existing connection or has not picked up the proxy change, quit the browser completely and reopen it. If the browser has its own proxy settings, make sure they are not overriding the system settings. Use the same test destination next; do not change the routing rules or enable Tun at the same time.

In v2rayNG, select a server from the list and tap Connect. The first connection may show a system VPN permission prompt. Confirm the request is from the client you just opened, then grant permission. Wait until the button or system status shows that you are connected, then switch to the test app. If the system says another VPN is running, check whether you can pause it. On a managed work device, follow your organization's device policies. A system VPN indicator only confirms that the VPN interface is active; test an actual request in the next step to check remote connectivity.

Step 4 · Requests and Logs

Check That the Connection Works

Open the browser you chose in step 2, visit the test site that should use the proxy under your current rules, and wait for a fresh page request to finish. An already-open page does not count; it may be cached. Note the time, return to the client logs, and check for a corresponding request around then. If the current log level shows matched outbound tags, confirm that the request used the proxy rather than a direct connection. The test passes only when the page loads and the outbound matches your expectations.

If the page will not load and there is no corresponding request in the logs, first check whether the app is using the client. On desktop, check that the system proxy is still set to auto-configure, then check whether the browser uses its own proxy, an extension setting, or a direct-connection rule. On Android, check that the VPN is still connected and that the test app is not excluded. If a request appears in the logs but shows a direct connection, focus on routing: check the active rule group and whether the test domain matches a rule, rather than switching servers. The current log level may hide access records, so the absence of a visible request does not by itself prove that no traffic reached the client.

If the request was sent through a proxy outbound but then times out, fails its handshake, or returns an authentication error, check the remote connection first. Note the first clear error message, then check your network, device time, and whether the subscription is still valid. You can also test another known-working entry from the same subscription, keeping the app, destination, and routing unchanged for comparison. A successful port check does not contradict a page failing to load: an open port does not guarantee a successful protocol handshake, authentication, or access to the destination. For more troubleshooting steps, see Troubleshooting. If a protocol name or outbound tag is unfamiliar, check the glossary.

After a successful test, if you temporarily switched to global routing, switch back to your usual rule group and retest the same destination to confirm that your regular setup works as expected. You can also open a destination that should connect directly and check that both types of requests use the right outbound. This only confirms that the tested app and destinations work; it does not mean every app is connected. To extend coverage, read the Tun mode guide separately. Do not change it alongside the system proxy during your first test.

When you are done, if the desktop client temporarily changed the system proxy, clear that setting in the client before exiting. If the device had a manual proxy beforehand, restore the settings you noted rather than simply clearing them. On Android, return to v2rayNG and tap Connect to disconnect, then confirm the system no longer shows an active connection. Finally, open a site that normally connects directly and check that the device is back to its original network state.