v2rayN Setup Guide

Before You Begin: Client and Subscription URL

First, visit the client download page, choose the installer for your device, install it, and open the client. Then get the subscription URL from your service provider and confirm that your account is active and has available data. The client reads configuration, runs the proxy, and manages connections; it does not create remote servers for you. If you install the software without adding node configuration, an empty list is normal.

A subscription URL is usually a long web address and may contain unique access parameters. Treat it like account credentials. Don’t post the full URL in public comments, screenshots, or online conversion tools. This guide covers the usual subscription import process. If you only have a link for a single node, use the client’s clipboard import feature instead of pasting it into the subscription URL field. For details, see Quick Reference: Subscriptions and Nodes.

Allow about ten minutes for the initial setup; the actual time depends on whether the subscription is reachable and on your network. Before you begin, close other proxy or VPN tools that are routing traffic, and note whether you can access your usual websites. Leave the client’s default DNS and core settings in place for now. Don’t enable TUN, change routing, and switch DNS methods all at once. Keeping changes to a minimum makes it easier to identify the cause if something goes wrong.

Step 1: Import the Subscription and Update Nodes

Add a Group and Save the Full URL

In the v2rayN main window, open the menu for subscription groups, go to “Subscription Group Settings,” and choose Add. Enter a recognizable name in the remarks field, such as “Everyday use,” then paste the full subscription URL into the address field. Check the beginning and end of the URL, and remove any spaces, line breaks, or quotation marks pasted by accident. Leave other options at their defaults, save the group, and close the settings window to return to the server list. The URL is now saved, but the nodes have not been fetched yet.

Next, select Update Subscription from the subscription menu. If the menu offers both “Update Current Subscription” and “Update All Subscriptions,” update only the group you just added during initial setup so you can check the result easily. Some versions also offer updates with or without a proxy. If you don’t have a working proxy yet, try updating without one first. Wait for the operation to finish, check the status message or logs, then select the relevant group and confirm that nodes appear in the server list.

In v2rayNG, open the side menu or overflow menu and find “Subscription Group Settings.” Tap Add, enter a name and subscription URL, save, then return to the home screen and select “Update Subscription.” If you already have other groups, check that the new group is selected rather than assuming the nodes shown belong to it. Node names, addresses, and protocol details come from the subscription; you don’t need to fill them in manually. Don’t change server connection parameters just to make the names look consistent.

Check the Update Results, Then Choose a Mode

When the update finishes, check whether the list is empty, whether the correct group is selected, and whether a keyword filter is active. A populated list means the client has loaded configuration, but it doesn’t prove that every node can connect. Avoid clicking Update repeatedly: this rarely fixes an expired URL, an inactive account, or an unreachable network, and it can make the logs harder to read. Once nodes appear, leave their settings unchanged and choose how to route traffic in the next step.

If the update fails, check these in order: whether the subscription URL was copied in full, whether the device date and time are correct, and whether your current network can reach the subscription service. For a timeout, check the network path first. If the URL is invalid or access is denied, contact your service provider to confirm the subscription status. Don’t paste the subscription URL into a search engine. Try updating through a proxy only if you already have a working connection and the subscription service requires it. See Subscription Management and Update Troubleshooting for more help.

Step 2: Choose a Proxy Mode and Routing

System Proxy: Send App Requests to the Client

In v2rayN, distinguish between the system proxy and routing. The system proxy tells apps that follow system settings to send requests to the local proxy. Routing determines whether the client connects directly to a destination or sends the request through a remote node. These are separate settings. For your first setup, use the system proxy and don’t enable TUN yet. This keeps changes to a minimum and makes it easier to see whether browser requests reach the client.

In v2rayN, find the system proxy control in the main window or in the system tray icon’s right-click menu. Look for an option such as “Set system proxy.” Note where it is, but wait until you’ve selected an active server and confirmed that the core is running before enabling it. “Clear system proxy” removes the proxy setting from the system; it does not delete your subscription. “Do not change system proxy” usually leaves the current system setting as is, so don’t mistake it for a definite off switch. If you have manually configured a proxy on your device, record its current values before making changes.

The system proxy won’t necessarily be used by every app. Some programs have their own proxy settings, while others ignore system settings. For your first test, use a browser that follows the system proxy rather than a game, command-line tool, or background updater. If only one program behaves differently, check its own network settings before switching nodes or reinstalling the client.

Routing Rules: Choose Where Requests Go

Open the routing selector in v2rayN and review the available rule presets. For everyday use, you can start with “Bypass mainland China” or a similar split-routing preset; exact names and rules depend on your client version. These presets typically send some destinations directly and route others through the proxy. Don’t assume a specific website’s route based on the preset name alone. If you switch to global proxy temporarily to troubleshoot, return to your original preset afterward so a temporary test setting doesn’t become your everyday configuration.

After connecting, v2rayNG uses the system VPN interface to handle eligible traffic. For your first setup, keep the default handling method and check which routing rules are selected. Don’t change per-app proxy settings, allowlists, and custom rules all at once; you could exclude the browser or keep test requests from reaching the client. A VPN indicator in the system UI only shows that the traffic-handling interface is active, not that the remote node is working. For an overview of TUN, routing, and outbound traffic, see Quick Reference. Save complex rules for Advanced Routing.

Step 3: Select a Node and Connect

Set the Active Server and Check Core Status

Return to the v2rayN server list and choose a node that suits your needs. Don’t change the protocol, port, or transport settings; these are usually provided by the subscription. Select the node, then use “Set as active server” or the corresponding enable option in the right-click menu. Some interfaces offer shortcuts, but highlighting a row with one click may not switch servers. Check for an active marker or the current server name in the status area at the bottom.

After setting the active server, check the client’s log or status area at the bottom for errors such as configuration parsing failures, a port conflict, or a core that won’t start. The v2rayN core may already be running with the program, so there may not be a separate Connect button. Once the core loads the configuration, enable the system proxy using the option you located in the previous step. Browser requests can now be routed through the local proxy. Leaving the window open does not prove that the connection is working.

In v2rayNG, tap the node you want to use and confirm it’s selected, then tap Connect on the home screen. On the first connection, Android will ask for permission to create a VPN connection. Review the prompt and approve it; without permission, the client can’t create the expected traffic-handling interface. If another VPN is already connected, disconnect it before trying again. After connecting, check the status in the client. If an error appears, note its details before taking action; don’t clear the app data and risk losing the subscription you just added.

Real Connection Test: A Useful Check, Not a Substitute for Browsing

If the node list offers “Real Connection Test” or a similar feature, run it after selecting a node. It usually sends a request to a specified test destination, making it more like an app request than a simple port check. Results still depend on the test URL, timeout settings, and network path. A successful test only confirms that this particular request completed; visit the site you actually need in the next step. If the test times out, check whether the test destination itself is reachable before deleting the node.

If the selected node can’t connect, try another node from the same subscription for comparison, changing only the node. If all nodes fail, check your local network, account status, and client logs first. If only one node fails, check that node’s service status. Keep the error details, including the time and key message, but hide the subscription URL and authentication information before sharing screenshots. Once at least one node passes the test, move on to the final step and verify where traffic goes. Changing the core, DNS, and TUN repeatedly adds variables and isn’t a good starting point for a first connection.

Step 4: Verify the Proxy Is Working

Compare Exit Information and Test Real Websites

Open a browser that follows the system proxy and visit a test page expected to use the proxy. Check that it loads, then visit a trusted IP lookup page. Ideally, record the results before and after connecting, using the same browser and lookup service. If your current routing sends the lookup page directly, seeing your local exit IP is expected. First confirm that the page is routed through the proxy before judging whether the exit IP is right. Geolocation databases can be inaccurate, so don’t rely on the displayed location alone to decide whether the connection works.

Next, open a site you actually need and refresh it or try a simple interaction; don’t just check a homepage that may be cached. If the client provides connection records or logs, check for a request to the corresponding domain and see which outbound it used. If no records are visible, check whether the log level and interface support showing them. Don’t leave excessively detailed logging enabled just to find a single request. Connection status, real-world access, and request routing together provide stronger evidence than a status icon alone.

If you use split-routing rules, also test a familiar site that should connect directly. The setup is closer to everyday use when both proxy-routed and direct destinations work. If every site follows the same route, check whether global proxy is still enabled or whether custom rules override the preset. This guide doesn’t cover DNS or encrypted DNS in the browser. If you’re troubleshooting DNS resolution or unsure which exit is being used, follow the DNS Configuration section.

Troubleshoot Based on Symptoms and Restore Network Settings When Done

If the client says it’s running but your browser can’t open pages, first check that the system proxy is set and that its local proxy port matches the port the client is listening on. Then check the active node and logs. If the browser works but another app doesn’t, check whether that app uses the system proxy. If only some apps are unaffected in v2rayNG, review the per-app include and exclude settings. Check in this order: are requests reaching the client, can the node connect, and can the destination be reached? This is more effective than reinstalling the client straight away.

Once the connection is verified, note the active group, node, and routing preset. Change only one setting at a time afterward. Before closing v2rayN, select “Clear system proxy,” then close the program. If you had manually configured a proxy, restore its recorded values so the system won’t keep pointing to a local service that has stopped. When you’re done with v2rayNG, disconnect from the client. You can also use this guide to verify changes after updating a subscription or switching nodes.