v2rayN Setup Guide

Import a subscription, choose a proxy mode, connect to a node, and verify the target app. If the client is installed and you have a valid subscription URL, allow about 10 minutes for the initial setup.

Import and Update a Subscription

Create a Subscription Group

First, copy the full subscription URL from your provider's account page. This is the URL the client uses to fetch a list of nodes—not the account sign-in page or a single node's share link. Keep any query parameters at the end of the URL; remove only accidental leading or trailing spaces. The URL may contain access credentials, so don't post it in public chats, shared documents, or screenshots sent for support. If you only have a single share link, use the client's share-link import option instead; you don't need to create a subscription group. See the glossary for the difference between these options.

Open v2rayN and go to “Subscription Group” > “Subscription Group Settings” in the main window, then add a group. Enter a recognizable source name under “Alias” and paste the copied link into “Optional Address (URL)”. Make sure the group is enabled, then click “OK”. For the first import, keep the default auto-update interval and leave the filter fields blank. If the list is empty after updating, you can then check the URL and response format without also having to determine whether a filter hid the nodes.

Update the Current Group and Check the List

Return to the main window, select the group you just saved, open the “Subscription Group” menu, and choose the option to update the current subscription. Saving a group stores the URL; updating it sends the request. Wait for the result to appear in the message area, then check whether nodes with names and protocol types appear under the group. Update only the current group the first time so you can match the result to the URL you entered without changing any other groups in use.

If the group is still empty, first make sure the correct group is selected in the main window. Then use the message area to distinguish a download failure from a parsing failure. For download failures, check that the URL was copied in full, the subscription is valid, and your current network can reach the provider. If the provider explicitly requires updates through a proxy, first confirm that you have a working connection, then use the relevant update option. Without a working node, repeatedly toggling that option won't establish the connection. If the content downloads but can't be parsed, check whether the provider's subscription format is supported by your client. See the FAQ for details.

In v2rayNG, open “Subscription Group Settings” from the side menu, add a group, enter a note and subscription URL, and save. Return to the main screen, switch to that group, and use the top-right menu to update the subscription. Wait for the nodes to appear in the list. In either client, seeing nodes only confirms that the subscription was imported; it doesn't mean a node is connected or that app traffic is using the proxy.

Choose a Proxy Mode

Start with the System Proxy for Browsing

If you only need a connection for a browser or another desktop app that follows the system proxy, start with the system proxy. Once v2rayN starts its core, it provides a local proxy endpoint. Choosing automatic system proxy configuration from the tray menu adds that endpoint to the system's proxy settings. Apps that use those settings will send requests accordingly; apps with their own proxy configuration may not be affected. For now, just choose this approach. Enable it after selecting a node and confirming that the core is running in the next step.

Before the first setup, note your existing system proxy settings. If the device is managed by an organization, or already has a proxy server or auto-configuration script configured, don't overwrite those settings. Test only with authorization, or configure the target app alone. If another proxy tool is running, check which program controls the system proxy to avoid two clients overwriting the same setting. For an initial test, enable only one approach; it's easier to tell where requests are going than when several features are enabled at once.

Understand Traffic Capture vs. Routing

The system proxy and TUN determine how requests enter the client. Routing determines whether those requests are proxied, sent directly, or blocked. These settings work independently: even with the system proxy enabled, requests matching direct-routing rules may still bypass the proxy. And broad proxy routing won't automatically capture traffic from an app that ignores the system proxy. For your first connection, keep the existing routing rules and test one specific target that's expected to use the proxy. If you're unsure which requests will be captured, read the glossary entry on proxying and routing rather than changing several rules at once.

If the target app doesn't use the system proxy, first check whether it lets you enter a local proxy directly. If it does, configuring that app alone is usually easier to verify. Consider v2rayN's TUN mode only if you need to capture traffic from an app that has no proxy settings. Before enabling TUN, check system permissions, possible conflicts with other virtual network adapters or VPNs, and whether the rules exclude the target traffic. Starting TUN doesn't guarantee that all traffic will use a remote node. The beginner setup on Android uses v2rayNG's VPN connection: keep the default app-scope settings and don't follow the desktop tray-menu steps.

Select a Node and Connect

Set an Active Server, Then Enable the Proxy

In v2rayN's main window, open the group you just updated and choose a currently available node from your subscription. Right-click the node and select “Set as active server” or the equivalent option. Highlighting a row by clicking it doesn't necessarily make that node active. Afterward, check the active node name shown in the interface, then look in the message area for errors such as a failed core startup, configuration load failure, or a local listening port conflict. Fix startup errors before enabling the proxy; otherwise, apps may be pointed to a local port with no service listening on it.

If you chose the system proxy in the previous step, open the “System Proxy” menu from the v2rayN tray icon and select “Automatically configure system proxy” or the equivalent option. Keep the client running. If the menu also offers “Do not change system proxy”, that means the current system settings are preserved—it does not enable automatic configuration or clear existing settings. If you're testing TUN instead, enable it in your version's interface and approve any system permission prompts. Don't also enable the system proxy. Check for client errors again, then open the app you'll use to verify the connection.

Approve the VPN Permission on Android

Select a node on v2rayNG's main screen and tap Start. When the system connection prompt appears for the first time, make sure it comes from the v2rayNG app you just opened, then tap Allow. Return to the app and check that the Start button has changed to a Stop button; you can also check whether the system shows a VPN connection. If it immediately returns to a disconnected state, check the client message first. If another VPN is already running, see whether you can stop that connection before retrying; don't disconnect a managed connection without authorization. The VPN indicator confirms that a local VPN connection is established, but you'll still need to check whether the remote node works in the next step.

Verify the Proxy Connection

Compare Before and After in the Same App

Start with one specific app, such as a browser that follows the system proxy. Choose a test page that is normally reachable and expected to match a proxy rule. Keep the network, node, and routing unchanged during the test. To compare results with the proxy disabled, use the same app and page to make a fresh request in each mode. Close the old page or use a new browser window to reduce interference from cached content and existing connections. Seeing the page load isn't enough: direct connections and cached content can look the same.

After making a request, check the client message area or logs for entries around that time that correspond to the target request, such as a proxy outbound connection or a connection error. The details shown vary by version and log level, so the absence of a line for every request doesn't by itself prove that traffic bypassed the proxy. You can also check a trusted service that reports your public IP, but only if that service is expected to match a proxy rule. A changed IP only suggests that this particular request may have taken a different route; it doesn't mean every app is using the proxy. Finally, test the app you actually intend to use.

Narrow Down the Failure, Then Restore Settings

If the browser works but another app doesn't, check whether the app uses the system proxy, has its own proxy settings, or is excluded by the system or routing rules. If the client logs show the target request but it times out or fails during the handshake, keep the test target and proxy mode unchanged and try another node in the same group. Change one thing at a time to tell whether the app isn't being captured, routing is sending requests directly, or the current node can't connect remotely. A successful subscription update doesn't mean the proxy connection works, so there's no need to delete the imported group after one failed connection.

When you're done testing, turn off the system proxy settings you enabled from the tray menu, or disable TUN. On Android, return to v2rayNG and tap Stop. If the device had custom proxy settings before you began, restore the values you noted; don't assume “Clear system proxy” will restore the previous configuration. Once the system settings are restored, reopen the same page to confirm normal access. If the issue persists, look up the symptoms in the FAQ. For help checking protocol, core, or subscription format compatibility, see the protocol guide.