Quick Start with v2rayN and v2rayNG

Import a subscription, choose which traffic to proxy, start a configuration, then check that your target app uses the proxy as expected. If you already have a client and a valid subscription URL, follow these four steps to get set up.

Step 1: Import and Update a Subscription

Get the full URL from your subscription provider. A subscription URL retrieves a set of connection configurations; it isn’t an account sign-in page or a link to an individual node. When copying it, keep any query parameters at the end and leave out surrounding quotation marks, explanatory text, and line breaks. The URL may contain access credentials, so redact the full URL and its parameters before sharing screenshots or diagnostic logs. For the difference between subscriptions, groups, and nodes, see the quick reference.

v2rayN: Save a Subscription Group, Then Fetch Configurations

Open v2rayN and select “Subscription Group” from the top menu to open the group settings. Add a group. Enter a recognizable source name under “Alias” and paste the full URL into “Optional address (url)”; confirm and return to the main window. The group will appear, but it may not contain any configurations yet. Switch to the group you just added, then select Update current subscription from the subscription menu. If your version only offers Update all subscriptions, you can use that instead. When the update finishes, check the server list in this group and confirm that entries have appeared.

v2rayNG: Update from the Configuration List

Open the top-right menu from the configuration list and select “Subscription group settings,” then tap the add button. Enter a remark or alias and the subscription URL, then save with the confirmation button in the top-right corner. Return to the configuration list and select “Update subscription” from the menu. If your version updates subscriptions by group, switch to the new group first. Wait for the fetch to finish before checking the entries; don’t tap Update again while a request is still in progress. Subscription groups and configuration lists are separate screens, so seeing the alias only confirms that the group was saved.

For both clients, this step is complete when configurations appear in the new group. If the list is empty, first check that you’re viewing the right group, then determine whether the update failed because the request couldn’t complete or because its contents couldn’t be parsed. For a request failure, check that the device is online and the URL wasn’t truncated. For a parsing failure, ask the subscription provider to confirm that the response uses a format your client can read, rather than returning a login page or error message. Choose a proxy mode only after configurations appear in the list. There’s no need to test latency yet or change the system proxy because an import failed.

Step 2: Choose Which Apps to Proxy

Decide which app you want to test before choosing a proxy method. For the first setup, start with a browser and test other apps after it works. The proxy mode determines how traffic reaches the client; routing rules determine whether traffic entering the client goes direct or through the proxy. These are separate settings. To make problems easier to diagnose, don’t change the proxy method, routing rules, and DNS all at once.

Desktop: Start with the System Proxy

Find the system proxy setting in the v2rayN system tray menu or main window. For your first test, choose the regular “Set system proxy” option and leave TUN disabled. You can set the system proxy in the next step, after choosing an active server. Some versions also offer options to clear the system proxy or leave it unchanged. Clear removes the current system setting; leave unchanged preserves it. Neither option creates a new proxy entry for the client.

The system proxy usually works with browsers and apps that read the system proxy settings. An app may bypass it if it’s configured for direct connections, uses its own proxy, or doesn’t read system settings at all. For your first test, use a browser that follows the system settings, and don’t enter a separate proxy address in a browser extension. If you need to route an app that ignores the system proxy through the client, see the TUN section of the user guide. Review its permissions and traffic coverage before switching.

Android: Use VPN Mode and Check App Coverage

v2rayNG normally captures app traffic through Android’s VPN interface. If your version lets you choose a service mode, select VPN for the first test rather than a mode that only starts a local proxy. If you’ve changed per-app proxy settings, check that your test browser isn’t excluded. If only selected apps are included, make sure the browser is on the list. For the initial setup, you can keep the default app coverage and adjust the list after verifying the connection.

If another app is using Android’s VPN interface, make sure switching won’t interrupt an active connection before stopping its session or testing on another device. Android will ask for VPN permission when you start the client in the next step; there’s no need to create a VPN configuration manually in system settings. Once you’ve chosen the system proxy for desktop or VPN for Android, and picked an app to test, you’re ready to connect.

Step 3: Select a Configuration and Connect

Return to the subscription group that updated successfully and choose a configuration for your first test. If the subscription provider specifies a purpose or usage requirements, follow their guidance. Otherwise, stick with one configuration until you’ve finished testing; don’t switch configurations and proxy modes at the same time. An entry in the list only means the configuration was imported. Check separately that it’s selected, set as active, and that the client is running.

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

Select an entry in the v2rayN server list, then choose Set as active server from the right-click menu. Check that the status area in the main window shows the selected configuration. Open the system tray menu, choose “Set system proxy,” and check that the menu reflects the selected option. Some versions restart the core after you switch active servers, so wait for the status to settle before opening a browser. If the log immediately reports a local listener or core startup failure, don’t keep refreshing web pages. Note the first error related to this startup, then see connection troubleshooting for possible causes.

Android: Tap Start and Approve VPN Permission

Select the configuration you just imported in the v2rayNG list, then tap Start. The first time you start a VPN connection, Android usually displays a connection request. Check that v2rayNG is requesting access, approve it, then return to the client and confirm that the Start button has changed to Stop. Android may also show a VPN connection indicator in the status bar or quick settings. If you denied permission, the VPN session wasn’t established; tap Start again and respond to the system prompt.

The active configuration, proxy switch, and VPN status show that a configuration is selected or a traffic entry point has been set up on your device. They don’t confirm that a remote connection succeeded. Many clients only establish an outbound connection after an app makes a request, so an empty connection log immediately after startup isn’t necessarily a problem. Keep the current configuration and test with fresh requests in both a browser and the app you intend to use.

Step 4: Verify the Proxy Is Working

First, make sure the proxy entry point is still running: on desktop, check the active server and system proxy; on Android, check the client status and the system VPN indicator. Open a new browser tab and visit a site you use regularly that’s accessible on your current network. Use a fresh request to check that it loads; don’t count an already-open page as a test. After the browser test succeeds, perform a network action in the app you actually intend to use, such as refreshing a list or reloading content.

Distinguish Network Access from Proxy Use

A page loading only confirms that the request succeeded; it doesn’t show whether it went direct or through the proxy. To check the exit IP, use a reputable public IP lookup service and compare results in the same browser and on the same network, first with the proxy stopped and then with it running. Make a fresh request after each change and, where possible, compare the same address type. If the client provides connection logs, look for the request at the time of your test and check which outbound route it used.

A changed exit IP can indicate that the tested request took a different route, but it doesn’t mean every app uses the same route. An unchanged IP doesn’t necessarily mean the proxy failed: the lookup site may match a direct-connection rule, or the browser may still be using an existing connection. Make a fresh request, then check the routing mode and app coverage. To find out which rule applies to a particular address type, see the routing guide; there’s no need to change all your rules just to check one site.

Narrow Down the Problem Based on Your Test Results

If both the browser and target app fail, restore the network settings from before startup and check that the device itself can connect to the internet. Once the basic connection works, restart using the same mode and test the same site, changing only to another configuration in the same group. This helps distinguish an unavailable configuration from a problem with the local proxy setup. If only the target app fails, first check whether it reads the system proxy or has its own proxy settings on desktop, or check per-app coverage on Android. Don’t re-import every subscription just because one app fails.

The initial setup is complete when the subscription group updates, the active configuration runs, the target app can make a fresh request, and you can confirm that it follows the expected proxy route when needed. When you’re done testing, clear the system proxy set by the client on desktop if you won’t be using it, or restore the proxy settings you recorded before the test. On Android, tap Stop in the client and confirm the session has ended. If you still can’t connect after stopping, see troubleshooting and follow the steps for what you’re experiencing; there’s no need to start again with installation.