Subscriptions · Routing · Connection

v2rayN Setup Guide

Go from importing a subscription to testing browser traffic. Start with a valid subscription URL, one node, and one browser. Haven't installed a client yet? Choose an installer from the Download Center.

Step 1: Import a subscription

First, make sure the link is a subscription URL, not an account login page or a link to share a single node. A subscription URL retrieves a group of nodes, while a single-node link adds just one configuration. Copy the entire URL, including its query parameters—don't stop at the domain. Subscription URLs may contain access credentials, so redact the full URL before sharing a screenshot or copied log.

v2rayN: Add a subscription group and update it

In the main window, open the Subscription Group menu and choose Subscription Group Settings. Add a record, enter a recognizable name in the remarks field, and paste the URL into the subscription URL field. If there's an Enable Update option, turn it on. Save, return to the main window, and select the group you just named. Then use the Subscription menu to update the current group. For the first update, if the subscription URL is directly accessible on your network, you can choose the update option that bypasses the proxy.

Seeing the group name only means the URL has been saved locally. Wait for the update to finish, then check that the group contains server entries with fields such as an alias and type. If the window is still showing another group, switch to the new one before checking. If nodes were already present, confirm the update record corresponds to this attempt so you don't mistake old entries for newly fetched configurations.

v2rayNG: Save a subscription and refresh the list

Open the main screen menu and go to Subscription Group Settings, or the equivalent subscription settings page in your version. Tap Add, enter the remarks and subscription URL, then tap Save and return to the server list. From the main menu, choose Update Subscription. Once the refresh finishes, check the group you just added. If you have multiple groups, find the right one by its remarks, then select a node from that group.

If the list is empty after an update, check the update message before changing proxy modes. For a download failure, make sure the URL is still valid and accessible on your network. For a read or parsing error, check that you imported a subscription URL rather than a login page or single-node link. Adding the same URL again usually makes troubleshooting harder. Continue to proxy setup only after nodes appear in the target group. If you're unsure which type of link you have, see Frequently Asked Questions.

Step 2: Choose a proxy mode

First, distinguish the proxy entry point from routing. The entry point determines whether a browser's requests reach the client. Routing determines whether requests received by the client go direct, through a node, or are blocked by a rule. Setting routing to Global won't automatically connect programs that aren't using the client. Likewise, enabling the system proxy doesn't mean every request received by the client will go through a node.

Desktop: Set routing, then check the system proxy

In the v2rayN main window, find Routing or Routing Settings. For everyday use, start with an existing routing preset and confirm that your test destination should use the proxy under that preset. If you're not sure which rule matches the destination, temporarily switch to an existing global proxy preset for the test, then switch back. There's no need to edit rule files or change DNS during the initial setup. Leave other settings as they are so you can tell what changed when you switched routing.

Next, find System Proxy in the tray menu or main window. For this test, use a browser that follows the system proxy. Once the connection is ready, choose Auto Configure System Proxy. Do Not Change System Proxy leaves the current system settings as they are; it won't enable the proxy for you. Clear System Proxy is also separate from stopping the core. If your computer already has a manual proxy or settings managed by your organization, note the existing configuration before making changes.

If your browser has its own proxy settings or extensions, check whether they override the system settings. For the test, use a browser you know follows the system proxy, and avoid changing multiple entry points at once. You don't need to enable TUN for the initial desktop test. First get one known entry point working, then decide whether other programs need access.

Android: Check that the test app is included

v2rayNG routes app traffic through the system VPN, so you don't need to copy the desktop system proxy setup. Keep the default routing and app scope for the initial setup. If you've enabled per-app proxy settings before, check that your test browser is on the allowed list and not on the exclusion list. Note the selected route so you can tell whether the test page should connect directly or through a node. Then start the connection.

Step 3: Connect

Return to the group you updated in Step 1 and choose a node you can identify by its alias. Note the alias and avoid switching nodes repeatedly during the test. A highlighted row may only indicate that it's selected; check the active server indicator or connection screen to confirm which node is actually in use. If a latency test is available, treat it as a reference—not proof that a browser can connect.

v2rayN: Confirm the active server, then enable the system proxy

In the server list, right-click the target entry and choose the option to set it as the active server. Confirm the active indicator has moved to the right entry, then check the message area in the main window. If your version restarts the core automatically when you switch nodes, wait for the startup message. If there's a separate start command, use it. If the core reports a configuration error or fails to listen, stop here; switching routing won't fix a startup problem.

Once the core is running, open the System Proxy menu and choose Auto Configure System Proxy. Open the menu again to confirm that option is selected. On desktop, both conditions must be met: the local proxy service must be listening, and the browser's proxy entry point must point to it. If the core is running but the browser isn't connected to it, pages may still load directly. If the proxy is enabled but the core isn't running, pages may fail because the local entry point is unavailable.

v2rayNG: Select a node and approve the system prompt

Select the target node and confirm it's shown as selected, then tap the Connect button at the bottom. When the system VPN prompt appears for the first time, make sure it was opened by the v2rayNG app you're using, then allow it. Return to the app and check that the Connect button or status has changed. If another VPN is already running, first check what it's for and whether device management policies apply. Don't replace it forcibly; only end the existing session and reconnect if it's safe and allowed to do so.

After connecting, stay on the same network. Don't switch between Wi-Fi and mobile data while changing nodes. If v2rayN repeatedly fails to start, note the first clear error in the message area. If v2rayNG disconnects immediately after authorization, check the client log. Once the status is stable, continue to the next step. This confirms only that the local service has started—not that the remote node can forward browser traffic.

Step 4: Test the connection

Use the browser you confirmed is connected to the proxy and open a reachable page that should use the proxy under your current routing rules. Make the request in a new tab; don't treat cached content from an already open page as a result. You can also open a page on the same site that you haven't visited yet to confirm it loads fresh. Note the approximate time so you can compare it with the client logs.

Compare the page load with outbound connection logs

If your version provides access or connection logs, find the request by time and check its destination and outbound tag. A successful page load, together with a matching request to the same destination marked as proxy outbound, is enough to confirm that this test used the proxy. If the log shows a direct connection and that matches your routing preset, the rules are working as configured—but this request doesn't test the node. Try a destination that should use the proxy instead; there's no need to change the rules right away.

If the message area shows only core startup messages and doesn't log each connection, an empty log doesn't mean the browser failed to connect. Note your current routing, then briefly retest on the same network with a global proxy preset and check the access log if available. If you can only compare access with the client on and off, treat that as a connectivity clue, not proof of the route taken by a specific request. A successful test only confirms that the network, node, and test app work at that moment.

If the test fails, return to the relevant step

If access logs are available but don't show the browser's test request, go back to Step 2 and check the entry point first: on desktop, confirm the browser follows the system proxy; on Android, check that per-app rules haven't excluded it. If the request reaches the client but proxy outbound times out, switch to another node in the same group, change nothing else, and retry the same page. If proxy outbound appears but the page still fails, note the domain, time, and first error, then use the Troubleshooting Guide to identify a DNS, connection, or routing issue.

When you're done testing, restore any temporary routing changes to your everyday preset. Before exiting v2rayN, disable the system proxy you enabled for this test. If you started with a manual proxy, restore the settings you noted earlier. In v2rayNG, tap the Connect button to disconnect and confirm the system VPN status updates. The next time you start up, you usually only need to check that the target group has nodes, confirm the active node, and repeat the browser test—you don't need to import the same URL again.