Getting Started · First Connection

v2rayN Setup Guide

Import a subscription, choose a proxy mode, connect, and test the connection. For your first setup, get one node working with one browser before adjusting routing rules.

01 Node List

Import and Update a Subscription

First, get the client and your subscription URL ready. If you haven’t installed the client yet, choose the right package for your system on the download page. Get the subscription URL from your configuration provider—not from the browser’s address bar on an account page. Both may look like web links, but the client needs a subscription endpoint that returns node configurations. A single-node share link is not a subscription; add it using the client’s node import feature. See subscription terminology for the difference. Subscription URLs may contain access credentials, so share only the error message when troubleshooting—not the full URL.

v2rayN: Save the Group, Then Fetch Nodes

Open the “Subscription Groups” menu in the main window, go to the group settings, and add a group. Enter a recognizable name in the remarks field, paste the full subscription URL, and save. Return to the main window. Seeing the group name only confirms that the URL was saved; the nodes haven’t been fetched yet. Select the new group and use the subscription menu to update it. If the menu offers updates with or without the proxy, choose the direct update option for your first setup if you don’t have a working node yet. Wait for the update to finish, then check the node names and protocol column in the selected group.

v2rayNG: Add a URL in Subscription Group Settings

Open the side menu, go to “Subscription Group Settings,” tap the add button, enter a remark and subscription URL, then save. Return to the node list and choose “Update subscription” from the top-right menu. Check the relevant group afterward. If you’ve already imported other sources, switch to the new group so you don’t mistake older nodes for the latest update. When changing a subscription URL, edit the existing entry before updating so you can tell whether the new URL worked.

If the list is still empty after an update, check that the pasted URL doesn’t include spaces, line breaks, or an ellipsis shown in the interface, then review the client’s message. A network timeout, a server refusing the request, and unparseable subscription data point to different stages of the process. Note the error type and, if needed, ask your configuration provider to confirm the URL and format. Once nodes appear, move on to the next step—you don’t need to test each one yet. A node appearing in the list only means its configuration was read; it doesn’t confirm that the server is reachable.

02 Traffic Capture and Routing

Choose a Proxy Mode

Think of proxy settings in two layers: first, how app requests reach the client; second, which outbound route they take once there. The desktop system proxy and Android VPN mainly handle the first layer. Routing rules handle the second. Enabling the system proxy doesn’t mean all traffic is proxied, and enabling a VPN doesn’t guarantee every destination goes through a remote node. For your first test, use one specific app and one destination that should go through the proxy. That makes the result easier to interpret.

Desktop: Use the System Proxy for Your First Test

Find the system proxy options in v2rayN’s main window, but leave TUN off for now. After selecting an active server in the next step, enable the system proxy and test with a browser that uses the system proxy by default. If the browser has a proxy-switching extension, make sure it isn’t overriding the system settings. Desktop terminal tools and some apps have their own proxy settings, so a working browser and a non-working terminal don’t necessarily mean the client connection failed. Keep the initial setup simple; troubleshoot other apps after the browser works.

Android: Route Your Browser Through the VPN for the First Test

In v2rayNG settings, confirm that the service mode is VPN if your version has this option, and check the per-app routing settings. If per-app proxying is enabled, make sure the browser is included in the allowlist and not in the blocklist. To check connectivity first, you can temporarily turn off the client’s per-app filter and restore it after the connection works. If another VPN is running on the device, check whether you can disconnect it. Don’t change system policies on a device managed by your organization.

Next, review routing settings on desktop or routing rules on Android. Keep an existing split-tunneling setup if you know which destinations it sends through the proxy or directly. If you’re unsure which rule will match your browser’s test destination, temporarily select the client’s global proxy route for a comparison, then restore your settings. “Global” here still applies only to requests that reach the client. Rule names don’t determine where traffic goes; check the destination and the route actually matched. See the JSON manual for rule order and outbound tags.

03 Active Node

Select a Node and Connect

Return to the subscription group you just updated and select a node for your first test. Don’t change protocol parameters, routing, and DNS all at once. Note the node’s remark so you can identify it if you need to retry. The active configuration and the highlighted row in the list aren’t necessarily the same thing; after selecting a node, check which one the client shows as active.

v2rayN: Set the Active Server, Then Enable the System Proxy

Right-click the node you want to test and choose “Set as active server,” or the equivalent option in your version. Confirm that the active indicator has moved to that node, then check the main-window logs for errors such as the core exiting, a configuration read failure, or a local port conflict. Once the core is ready, find the system proxy option in the status bar or tray menu and choose “Automatically configure system proxy,” or the equivalent setting in your version. If the client was already running, check the logs again after switching nodes so you don’t mistake output from the previous node for the current status.

v2rayNG: Start the Service and Approve VPN Access

Tap a node on the main screen and confirm it’s selected, then tap the connect button. The first time the VPN service starts, Android displays a connection request. Confirm that it was initiated by the current client before approving it. Once permission is granted, the client button should show that it’s running, and Android will usually display a VPN icon or notification. If the button returns to a disconnected state after you tap it, check the client logs or notifications instead of tapping repeatedly. No prompt doesn’t necessarily indicate a problem; Android may have already saved permission for the client.

If the client reports an incompatible configuration before starting, try another node from the same subscription that’s supported by your client and core version. If it says a local listening port is in use, close the duplicate instance that’s using that port—don’t start by changing the remote server port. A core-started message or VPN-connected status only confirms that the local service is running. Keep the same node and routing settings as you move on to the next step so the test conditions stay consistent.

04 Compare Requests

Test the Connection

Send a new request in the browser you selected earlier. Choose a test destination that should use the proxy under your current rules; don’t rely on a page that was already open before connecting. If needed, open a new window and revisit the destination so cached content or an existing connection doesn’t skew the result. If you’re using a public IP lookup site, make sure the current routing rules send it through the proxy. Split-tunneling rules may send that site direct, in which case an unchanged exit IP is expected and doesn’t mean the proxy failed.

Compare Before and After, Then Check Routing

First, note the result while the client is running. Temporarily clear the system proxy set by the client on desktop, or pause the client VPN on Android. Keep the browser, network, and destination unchanged, then send a new request. Restore traffic capture and test again. If the result or exit IP changes, check whether that matches your routing rules. If both requests work, that alone doesn’t prove traffic went through the proxy. Likewise, an unchanged exit IP may mean the browser isn’t using the system proxy or the request matched a direct route.

If the client’s current logs include access records, search for the request by its timestamp and destination, then check the outbound tag shown in the record. If a request matched a direct route, review the routing rule order. If it tried to use the proxy but repeatedly failed during the handshake or timed out, keep the routing unchanged and test another node. If there’s no record, first confirm that access logging is enabled, then check whether the desktop browser uses the system proxy or the Android browser is included in the VPN. Missing logs alone don’t prove that traffic bypassed the client.

Restore Your Usual Settings

After comparing results, restore any temporary global route or per-app settings, then test one destination that should use the proxy and another that should connect directly. Before closing the desktop client, clear the system proxy with the client or restore your previous proxy settings if the system proxy still points to the client’s local port. On Android, stop the VPN with the client’s connect button. For browser and terminal proxy differences, see system proxy troubleshooting. To change outbound, routing, or DNS fields, refer to the JSON manual.