Quick Start

v2rayN and v2rayNG Setup Guide

From importing a subscription to verifying the connection: first get one browser working through the proxy, then configure other apps.

01Subscriptions and Nodes

Import a Subscription and Update Nodes

First, make sure you copied a subscription URL, not the provider’s login page. A subscription URL is usually a link beginning with https://. The client fetches it to load a set of nodes. Share links beginning with vmess:// or vless:// usually contain a single node. Import one from the client’s “Import from clipboard” menu instead of creating a subscription group. Both link types may contain access credentials. Before pasting, check that you have not selected extra explanatory text. When asking for help, do not share the full URL or a QR code containing the share link.

v2rayN: Add a Group, Then Update It

Open the main window, go to Subscription Group Settings from the Subscription Group menu, and add a group. Enter a recognizable name in the remarks field, paste the URL into the subscription URL field, and save. Back in the main window, select the group you just named, then choose Update Current Subscription from the Subscription Group menu. During initial setup, if your current network can reach the subscription URL directly, choose an option like “Update Current Subscription (without proxy)” to avoid sending the request through a proxy that is not running yet. Wait for the update to finish, then check the selected group’s list. The step is complete only when nodes appear; a group name alone is not enough to connect.

v2rayNG: Save the URL, Then Update from the List

Open the side menu and go to Subscription Group Settings. Tap the add button, enter the remarks and subscription URL, save, then return to the node list. Choose Update Subscription from the menu in the upper-right corner. If your version lets you filter nodes by group, switch to the group you just added after updating. For a single-node share link, use the clipboard import option in the add menu on the list screen. The node should appear after import; there is no need to update a subscription.

If the list is still empty after updating, switch back to the all-nodes view to rule out a group filter or other list filter. If the update reports a request failure, check that your internet connection is working and that the subscription URL is current. If the request succeeds but no nodes are imported, ask your subscription provider whether its response format is supported by your client. Do not change your system proxy yet: wait until nodes appear before deciding which apps should use them.

02Proxy Setup

Choose System Proxy or VPN Mode

Two settings are easy to confuse: proxy mode determines how app requests reach the client, while routing rules determine whether those requests connect directly or through a proxy. Enabling system proxy or TUN does not mean every site will use a node. For your first test, leave the existing routing rules as they are and avoid changing the mode, rules, and node at the same time. Otherwise, even if the connection works, it will be hard to tell which change made the difference.

v2rayN: Start with System Proxy

If you want to proxy a browser or another app that respects system proxy settings, first find System Proxy in the desktop tray menu and look for an option such as “Set system proxy automatically.” Enable it after selecting an active node in the next step. The client directs apps that support system proxy settings to its local proxy. Some apps use their own network settings, so a working browser connection does not mean other apps are using the proxy. Before testing, check whether your browser uses the system proxy, and temporarily disable any proxy extension that overrides it.

If the app you want to use does not respect system proxy settings, consider TUN mode in v2rayN. TUN routes traffic through a virtual network interface and usually covers more traffic than system proxy mode. Whether administrator privileges are required depends on your system and client configuration. For initial troubleshooting, test only one mode at a time: before switching to TUN, end the current test and clear the system proxy setting you enabled for it. Then enable TUN. If other proxy software or virtual network adapters are running, make sure they will not conflict with the new mode’s network settings.

v2rayNG: Start with the Default VPN Mode

On Android, start a VPN connection from v2rayNG as usual; you do not need to enter a manual proxy in Wi-Fi settings. If you have configured per-app routing, first check that your test browser is not excluded. If the client is set to proxy only selected apps, make sure the browser is on the list. If another VPN is already running on the device, disconnect it before continuing in the client. On a work- or school-managed device, follow its management policies if you cannot switch VPNs.

Your traffic entry point is now set. Return to the main list to connect. For more on TUN permissions, virtual interfaces, or split tunneling, see the complete setup guide for all platforms. There is no need to configure everything before your first test.

03Connect

Select an Active Node and Connect

Choose a node from the group you just updated and use that same node for the tests that follow. A highlighted row may only mean that a node is selected for an action; it does not necessarily mean it is being used for the connection. A speed test is not the same as connecting: even if a node has test results, system proxy or VPN mode may still be off.

v2rayN: Set the Active Server, Then Enable the Proxy

Right-click the node you want to use and choose “Set as active server”; some versions also let you double-click it. Check the main window’s status bar or active indicator to confirm that the node you selected is shown, then check the runtime logs for startup errors. For system proxy mode, choose “Set system proxy automatically” from the tray menu and confirm that the menu reflects the current state. For TUN mode, turn it on from the main window or the relevant settings and follow any permission prompts required by your system. If you have only selected a node without configuring a traffic entry point, the client may be running, but your browser will not automatically use the proxy.

v2rayNG: Tap Connect and Approve the System Prompt

Tap the node you want to use in the main list and confirm that its selection indicator appears, then tap the Connect button at the bottom of the screen. The first time you connect, Android will ask whether to allow a VPN connection. Before approving, confirm that the prompt names the client you just opened. Back in the list, the button should change to a disconnect option. You can also check the system VPN status or the client notification to see whether the connection is still running. If you dismiss the permission prompt, the service will not start; return to the client and try again.

If the client disconnects immediately after starting, check its runtime logs. If the desktop client reports that a local port is already in use, check whether another proxy client is running. If so, quit the one you are not using and retry with the same node. If v2rayNG says it cannot establish a VPN, check whether another VPN is active. Once the client status is stable, open your browser. A normal status only confirms that the local service has started; it does not prove that your browser request went through the proxy.

04Verify the Connection

Check Whether Browser Requests Use the Proxy

Choose a site you know that should use the proxy under your current routing rules, and note its domain and the test time. Do not rely on a page that was already open; your browser may be showing a cached copy. Open a new window, visit a page on that site that you have not opened before, and check the client’s runtime logs. If the logs show requests and outbound connections, find the entry matching the test time, domain, or destination address and confirm that it uses the proxy rather than a direct connection. If the logs do not show outbound details, do not assume the test succeeded just because the page loads.

Compare Results Before and After Connecting

If you know the node’s expected exit IP, use a reputable IP lookup service to help verify the connection. First make sure requests to that service should also use the proxy, then make a fresh request in the same browser both before and after connecting. Seeing the expected IP afterward is evidence that the lookup request used the proxy, but it does not verify other apps. If the IP has not changed, check whether the lookup domain is routed directly, then review your browser’s proxy settings or v2rayNG’s per-app routing list. Do not route all traffic through the proxy just to make the IP change.

Troubleshoot Based on What You See

If the client has no matching request record, first check whether traffic is reaching the proxy: on desktop, revisit system proxy settings and confirm that the selected mode is still enabled and that the browser is not overriding it. On Android, check that the VPN is still running and that the browser has not been excluded. If the current logs do not show requests, temporarily enable access logging if the client supports it, then try once more. If the request appears but uses a direct connection, review the routing rule that matches the domain. If it uses the proxy but times out, select another known-working node in the same group and retry the same page in the same browser. Change one thing at a time to identify whether the issue is the entry point, routing, or node.

End the Test and Restore Your Settings

When you are done testing, turn off TUN if you enabled it, or clear the system proxy setting you configured from the desktop tray menu, then exit the client. If your device already had a manual or organization-managed proxy, restore its original settings rather than turning everything off. On Android, tap Disconnect and confirm that the VPN created by the client has stopped. Finally, make a fresh request in the same browser to confirm that your expected network settings are restored. If you continue to see timeouts, update failures, or inconsistent behavior between apps, review the troubleshooting section of the complete setup guide alongside your notes. Before sharing logs, redact subscription URLs, node credentials, and unrelated browsing records.

Download Clients