Quick start · Set up in four steps

v2rayN Setup Guide

Import a subscription, choose a proxy mode, connect, and verify the route. If the client and subscription URL are ready, follow these steps to finish your first setup in about 10 minutes.

Import a subscriptionUpdate the group and confirm its servers appear

Open the v2rayN main window and get the subscription URL from your service provider. A subscription URL fetches a list of servers; it is not the provider's login page or a server address. Copy the entire URL, including any parameters after the question mark, without selecting surrounding instructions. Some subscription URLs contain account access details, so avoid sharing them in public screenshots, chats, or logs sent to others. If you haven't installed the client yet, choose an installer on the client download page. Come back once the main window opens.

Find “Subscription Group” at the top, then open “Subscription Group Settings” and add an entry. Enter a recognizable name, such as the service name, in the remarks field, and paste the complete subscription URL into the address field. After saving, return to the main window and select the new group above the server list. Then open the “Subscription Group” menu and update the current group. Labels may vary slightly between versions; choose the command that applies to the current group. There's no need to refresh every group just to import one subscription.

Saving the URL and fetching servers are two separate actions. An empty group immediately after saving doesn't mean the import failed. Wait for the update to finish, then check the main window's message area and current list. If server names and their protocols appear, the list has been imported—but that doesn't mean every server can connect. If the group is still empty after the update, make sure you haven't selected a different group, then check that you didn't use an account page URL or miss any parameters when copying. If your provider has replaced the URL, edit the existing group's address and update it rather than repeatedly creating groups with the same name.

If the client reports a download failure or timeout, first check that your internet connection is working and that the subscription service is available. A subscription update failure and a server connection failure are different problems: the first happens while downloading the server list; the second happens when traffic is sent through a selected server. Switching to TUN or changing a server's transport settings won't confirm that the subscription URL is correct. If your provider sent a single server share link, use the client's clipboard import feature instead of pasting it into the subscription URL field. See the glossary for the difference between the two link types.

In v2rayNG, open “Subscription Group Settings” from the side menu, add a group, and enter its name and URL. Save it, return to the main list, then use the menu in the top-right corner to update. Once the servers appear, keep the settings supplied by your provider; there's no need to edit them one by one. Whichever client you use, confirm that the current group contains at least one server you can select before moving on.

Choose a proxy modeStart with the system proxy; try TUN later

First decide which app you want to test. If it's a browser that uses your system proxy settings, start with “Set system proxy automatically” on desktop. Find “System Proxy” in the v2rayN tray icon's right-click menu and confirm the option is available; don't apply it yet. You'll enable it after selecting an active server in the next step. This sets the system proxy entry, but whether an app uses it depends on the app itself. If a browser extension or in-app proxy setting points elsewhere, note it first. Otherwise, you might mistake an app overriding the system proxy for a faulty server.

TUN is another way to route traffic into the client. It uses a virtual network interface and is worth trying only after the regular system proxy works, if an app doesn't use the system proxy. For your first test, don't enable both modes at once: even if a page loads, it can be hard to tell which route the request took. To try TUN, first undo the system proxy enabled for this test, then enable TUN as prompted by the client. Some environments require elevated permissions. If you see a permission or virtual interface initialization error, address that error before switching between servers. Follow your organization's device policies if permissions are managed.

The system proxy and TUN control how traffic enters the client; routing rules determine whether traffic is sent directly or through a proxy after it enters. These are independent settings. For your first test, keep your existing routing rules and note the current selection. Choose a test destination that those rules should send through the proxy. If a rule classifies the destination as direct, a page loading normally doesn't prove the proxy route works. For more on routing, virtual interfaces, and DNS, see the glossary and then the cross-platform guide. There's no need to rewrite rules before your first connection.

On v2rayNG for Android, there's no desktop tray or “Set system proxy automatically” option. The usual setup routes traffic through the system VPN, so keep the default app routing settings for your first test. If you've previously set the VPN to include or exclude specific apps, make sure the browser you're testing is included. If the device already has an active VPN, check that you can pause the existing connection; don't replace a work or school connection that's still in use. Once you've chosen how traffic will enter, select the server that will handle it.

ConnectSet an active server before sending requests

Return to the v2rayN server list and choose an available server from the group you just updated. Right-click it and select “Set as active server”; some versions also let you double-click a server. Don't rely only on the row being highlighted—check the active marker or window status to confirm the server changed. A regular click may only select a row without changing the server in use. After switching, wait for the log to update before judging the connection while the core reloads.

Now apply the traffic mode you chose in the previous step. For the system proxy, select “Set system proxy automatically” from the tray icon's right-click menu and make sure TUN is still off. For TUN, restore the system proxy to its pre-test state, then enable TUN and watch for startup messages. v2rayN usually has no single “Connect” button: once the active server, core status, and traffic mode are ready, a new request from an app triggers the connection. Closing the main window may only minimize the client to the tray; it doesn't necessarily exit.

If an error appears immediately after startup, start with the first error logged after your latest action. If the local listening port is already in use, check whether another client or proxy app is using it. Close only an app you're sure you no longer need, then try again. If setting the system proxy fails, check whether your current system account is allowed to change proxy settings. If the core won't start, address the client version or runtime environment first; don't guess at changes to the server's protocol, port, or transport. Change one thing at a time so you can tell what affected the result.

In v2rayNG, select a server and tap Connect on the main screen. On first use, read and approve the system's VPN permission prompt. Back in the client, check the button state or your device's VPN status. If you denied permission, the server may remain selected, but traffic won't enter through the VPN. Start the connection again and approve the prompt. On desktop and Android alike, a running status means the connection is ready to use; it doesn't prove the remote server has responded. A new request will help you tell the difference.

Verify the connectionCheck both the app response and the request route

Quit the browser you're using for the test, reopen it, and visit a destination that your current routing rules should send through the proxy and that you're authorized to access. Don't rely on a tab that was already open before connecting: the page may be cached or using an existing connection. Open a new tab and visit a page on the site you haven't loaded yet, then check that it loads as expected. If you have a trusted IP lookup service, you can also compare results before and after testing. A changed IP only shows that this lookup used a different exit; it doesn't mean other apps or destinations use the same route.

Return to the client and check its logs or connection records for the time of your request. You can confirm the route worked when the target request is shown going through the proxy outbound and the browser receives the expected response. If the page loads but the record shows a direct connection, the test destination didn't use the proxy. Check your routing rules or choose a destination that should clearly use the proxy. If the page loads but there's no corresponding record, first check whether the log level displays requests. Then check whether the browser uses the system proxy or, on Android, whether the app is excluded from VPN routing. Don't conclude that the client didn't handle the traffic just because the log is empty.

If the record shows the request went through the proxy but the page still times out, keep the same traffic mode and test the same destination with another available server in the same group. If it works, the issue may be specific to the original server or the network path to it. If several servers fail, check your local connection, system time, and client messages in turn. For example, if you see a certificate time error, check the date, time, and time zone instead of disabling certificate verification. A latency test may not make the same request as a browser, so it can't replace this step. For a step-by-step diagnosis, see How to troubleshoot a node timeout.

Once the test succeeds, note the active group, server, and traffic mode. If something changes later, start by checking the setting that changed. For a temporary test, turn off TUN if you enabled it, or restore the previous system proxy from the tray, then exit the client. If you had a manually configured proxy before testing, restore it rather than clearing the settings. On Android, disconnect from the v2rayNG main screen. Finally, make a new request from your usual apps to confirm the restored network works. For platform-specific settings, see the relevant section of the cross-platform guide.