Getting Started · First Connection

Getting started with v2rayN and v2rayNG

After importing a subscription, choose one node and test one app. First confirm the request goes through the proxy, then adjust your routing rules.

Before you begin, have your subscription URL ready and make sure your device is online. If the client isn’t installed yet, choose an installer from the client downloads page. Allow about 10 minutes for the basic setup. For now, avoid changing ports, DNS, and custom rules at the same time.

Import a subscription

First, check that you have a subscription URL, not a share link for a single node. A subscription URL retrieves a set of configurations; after saving it, you still need to update it. Import an individual node using the client’s share-link import option. Don’t use a service’s login or help page as a subscription URL. The URL may contain personal access credentials, so paste it directly into the client and hide the entire URL before sharing a screenshot for help.

v2rayN for desktop: Add a group and update it

Open the main window and go to Subscription Groups. Find the group settings or add option. Give the group a recognizable name, paste the URL into the URL field, make sure the group is enabled, and click OK. Back in the main window, open the Subscription Groups menu and update the group you just saved. If the menu offers updates through the proxy or directly, and you don’t have a working proxy yet, choose the direct option. When the update finishes, open the group and check that at least one selectable configuration appears.

When importing, create a new group if possible rather than replacing an address you already use. Saving only confirms that the client stored the URL; the subscription is retrieved only after an update, when entries appear in the right group. If the interface is showing another group, switch to the one you just named. Don’t add the same URL again just because the list hasn’t changed.

v2rayNG for Android: Save, return to the main screen, and update

From the main screen menu, open Subscription Settings, tap Add, enter a name and URL, then save. Return to the configuration list, update the subscription from the menu, and open the relevant group to check for entries. Depending on the version, the update command may be in the main screen menu or the group menu. Look for Update Subscription; the Connect button doesn’t refresh the list. If the settings page shows the group name but the main list is still empty, check for an update error, then confirm which group is selected.

If no nodes appear in either interface, copy the URL again from its source and check for missing trailing parameters or added line breaks. Then confirm the subscription is still valid. If the update times out, leave the client disconnected and check whether your current network can reach the subscription service. If the service returns a login page or an access-denied message, changing nodes won’t fix the subscription URL. For more help, see the Help Center troubleshooting steps for failed updates. Don’t connect yet; continue to the next step once entries appear.

Choose a proxy mode

In the group you just updated, choose a node with a known source that has been confirmed to work recently, and note its name. There are two separate settings to understand: the system proxy or VPN determines how apps send requests to the client; routing rules determine whether the client sends those requests through the proxy or directly. Both must be set correctly for a request to use the selected node. Setting routing to Global won’t capture desktop apps that don’t use the system proxy in the first place.

Choose a route that matches your test

In v2rayN, look for Routing in the main window or for routing settings. In v2rayNG, open Settings and check the routing options. Labels vary by version and existing rules. If there’s a Global preset, you can use it temporarily for the first check to avoid routing your test traffic directly. Switch back to your usual rules afterward. If the interface shows rule-set names instead, choose one you know will send the test traffic through the proxy rather than guessing from its name.

Direct is useful for comparison, but it can’t verify the proxy’s exit route. Presets such as Bypass mainland China are routing options, not connection switches; they only affect how the client handles matching requests. You don’t need to delete existing rules. Note your current preset, switch temporarily for a test, then restore it once the connection works. If your usual rules are complex, don’t add domain exceptions or change DNS during the first connection test.

Decide how apps will send traffic to the client

On desktop, start by testing v2rayN with the system proxy and a browser that follows the system proxy settings. Leave apps that ignore those settings until after you’ve verified the basic connection. Don’t enable both the system proxy and TUN just to get one app working. On Android, use v2rayNG’s Connect button to start the system VPN service. If per-app proxying was enabled before, make sure your test browser isn’t excluded—or is selected if the mode includes only specified apps. Once you’ve chosen the route and test app, connect without changing the rules again.

Connect

v2rayN for desktop: Select the active node and configure the system proxy

Return to the node list, open the selected node’s context menu, and choose Set as active server or the equivalent option in your version. Don’t rely on the highlighted row: selecting a row just focuses it; the active node is the configuration the client is actually using. Confirm that the active marker or status area shows your chosen node, then check the logs for core startup errors or port conflicts. If the core hasn’t started, don’t enable the system proxy yet; apps could send requests to an address with no service listening.

After the core starts normally, open the v2rayN tray menu and choose Automatically configure system proxy. Reopen the menu and confirm the option is checked. Don’t change system proxy leaves the current system settings unchanged; it doesn’t mean the client proxy is enabled. If the system proxy setting quickly reverts, check whether another proxy tool is managing it. Don’t override existing settings on public or organization-managed devices. At the end of the test, choose Clear system proxy to undo your changes if no system proxy was configured beforehand. Otherwise, restore the previous settings.

v2rayNG for Android: Select a node and authorize the connection

Return to the main screen and confirm the selected group and node are correct, then tap Connect. The first time you connect, Android usually displays a VPN connection request. Make sure it comes from the client you just opened, then allow it. Wait for the button to show Connected and check the system VPN status or the client notification. If another VPN is already running, check whether it can be paused before switching. Don’t disable a connection required by device management.

If the button switches back to disconnected right away, check the first clear error in the notification or logs. Determine whether the issue is authorization, core startup, or the upstream connection. You don’t need to reimport the subscription each time, and repeatedly tapping Connect won’t help. A checked system proxy on desktop or a VPN indicator on Android only shows that local traffic capture is active; it doesn’t mean the remote server has responded. Now you can test with a real app request.

Verify the connection

Make a new request and check its route

In the browser you chose in the previous step, open a test page that’s normally accessible and should match your proxy rules. Open a new window and refresh to confirm the page loads new content; an already-open page still being visible doesn’t prove the connection works. Note the time of the request, then check the client logs for the same period. If the logs show the destination and outbound route, confirm the request used the proxy. A latency test in the node list only reflects that one test request and can’t replace a real browser test.

If your current log level doesn’t show outbound details, use a trusted exit-check service in the same browser and on the same network to compare results before and after connecting. On desktop, temporarily undo the system proxy settings for comparison; on Android, pause the VPN, run the test again, then reconnect. A changed exit address supports the conclusion that this request took a different route; an unchanged one isn’t conclusive—also check whether the destination matched a proxy rule. Testing one page doesn’t mean all apps and domains use the same route.

Find the failing layer, then change one thing

If the client doesn’t show the request, first check whether the current log level records that type of traffic, then check app capture: on desktop, confirm the browser follows the system proxy; on Android, confirm the test app is covered by the VPN. If the request is logged but goes direct, check which rule matched the destination instead of changing the subscription. If the log shows it went through the proxy but timed out, keep the same test page, network, and route, and try another known-working node in the group. Comparing the results helps isolate app settings, rule matching, or an upstream connection issue.

After verification, restore the routing rules you plan to use and test one destination that should go through the proxy and one that should connect directly. If only a specific app still doesn’t work, troubleshoot by symptom in the Help Center. For desktop apps that ignore the system proxy, see the TUN section of the cross-platform guide. Before fine-tuning DNS settings or routing rules, note the configuration you’ve verified and retest after each change.