V2Ray Setup Guide

Follow these four steps to connect for the first time. Make sure your subscription includes an available server, route a frequently used app through the proxy, then check where its requests went.

Import and Update a Subscription

Before you start, have the full subscription URL ready and make sure the client is installed. If it isn't, choose the right installer for your device on the client download page. A subscription URL is the link your service provider gives you to add to a client—not a web address for signing in to an account, or a share link for a single server. Copy the entire URL, including its query parameters, and avoid leading or trailing spaces. Don't post URLs containing access credentials in support tickets or chat screenshots.

v2rayN: Add a Group, Then Update It

Open the main window and go to Subscription Group Settings from the Subscription Group menu. Add a group, enter a recognizable name in Remarks, and paste the full subscription URL into Optional Address (url). Make sure Enable Update is on, then save. Leave Filter blank for the first import. Check that the unfiltered list appears before deciding whether to filter by name. After saving, return to the main window and select the group you just created.

Open the Subscription Group menu again and choose the option to update the current subscription. If the menu offers updates with or without a proxy, choose without a proxy for the initial setup when your current network can reach the subscription URL. Wait for the update to finish, then check the main list for server entries. Seeing the group name in subscription settings only confirms that the group was saved; server entries in the main list confirm that the client retrieved and parsed the subscription.

v2rayNG: Save the URL, Then Update from the List

Open the sidebar from the main screen, go to Subscription Group Settings, and tap the plus button in the upper-right corner. Enter a name and the subscription URL, make sure the group is enabled for updates, then save. Return to the configuration list and choose Update Subscription from the upper-right menu. When the update finishes, check for new entries. If another group was selected, switch to the new group or view all configurations so a list filter isn't mistaken for a failed import.

For either client, this step is complete when you can see server entries in the relevant group. If none appear, check the update message, URL, enabled setting, and selected group. A login page returned instead of subscription data, an expired subscription, or a response format the client can't recognize can all leave the list empty. Changing the system proxy or repeatedly tapping Start won't add missing servers. See the glossary to learn the difference between a subscription URL and a server share link. Once entries appear, choose how to route app traffic through the client.

Choose a Proxy Mode

Keep two questions separate: the proxy entry point determines how an app's requests reach the client; routing rules determine whether those requests connect directly, use a proxy, or are blocked. Setting the system proxy doesn't force all requests through the same server. For your first test, leave existing routing rules as they are and configure only the entry point. Changing both at once makes it harder to identify the cause if something fails.

v2rayN: Test a Browser with the System Proxy

Choose a browser that uses the system proxy settings as your test app. From the v2rayN system tray menu, open System Proxy and select Auto configure system proxy. This directs the system proxy to the client's local entry point. Clear system proxy removes the system proxy settings; Do not change system proxy leaves the existing settings in place and doesn't mean automatic configuration succeeded. If your device already has a proxy required by work or school, note its settings first so you don't remove them when you're done.

Leave TUN mode off in the main window for this test. TUN uses a virtual network interface to route traffic and is useful for apps that don't follow system proxy settings, but it is a different entry point. If a browser works but another app doesn't, first check whether that app uses its own proxy settings rather than assuming the server is at fault. To switch to TUN, wait until the basic connection test succeeds, then configure it separately using the platform-specific section in the installation guide.

v2rayNG: Start with a Full-Device Connection

Tapping Start in v2rayNG asks Android to establish a VPN connection; you don't need to copy the desktop system proxy steps. For the first test, leave routing settings unchanged. If per-app proxying was previously enabled, check in the client settings that your test app is included. You can temporarily turn off per-app proxying for this test, but note the original setting and restore it afterward. Per-app proxying determines which apps enter the client, not which routing rule their requests match.

If the system says another VPN service is already running, first check whether it's safe to disconnect it. Don't replace a connection managed by a work policy without permission. Once you've chosen the entry point, return to the client list and select a server. On desktop, even if the system proxy is set, you still need to confirm the active server. On Android, you'll start the connection in the next step.

Select a Server and Connect

Choose a configuration marked available by your provider from the group you just updated, and note its name. Don't test several servers at once or sort by latency yet. A server name is just a label; it doesn't prove the server is currently reachable. Start with one configuration. If the test fails, try another under the same network and routing settings so you can compare the results.

v2rayN: Check the Active Server and Logs

Find the entry you want in the main list and choose Set as active server from its right-click menu. Clicking a row to highlight it doesn't switch the active configuration. Check that the active server shown in the window matches the name you selected, then look for persistent startup errors in the log. If you chose the wrong entry among duplicates, return to the relevant group and check again. Make sure the system proxy in the tray is still set to Auto configure system proxy, then switch back to your test browser.

If the logs immediately report that a local port is already in use, check whether another client instance or program is listening on the same port. Don't change subscriptions first; switching remote servers won't free a local port. If the logs say a configuration couldn't be loaded, note the first error and the current server name. Avoid changing multiple subscription import fields before you've identified the problem.

v2rayNG: Select a Configuration and Approve the System Request

Tap the configuration you want in the list and confirm the selection indicator is on the correct row, then tap Start at the bottom of the main screen. The first time you connect, Android displays a system connection request. Check that it came from the client you just used, then approve it. When you return to the app, the Start button should change to a state that lets you stop the connection, and Android will usually show a VPN status icon. If you denied permission, return to the client and try again. Selecting an entry while the button still says Start means the connection hasn't begun.

A running status means the local service is running or the system interface is established; it doesn't guarantee the remote server is available. If the button quickly returns to its stopped state, check the client's status message and system connection permissions. If the connection stays active, don't keep toggling it. Keep the same server and network, then move on to the next step and test with an actual request.

Test Your Connection

Send a new request from the test app you selected. For example, open a new browser tab and visit a site you can test and expect to use the proxy under your current rules—don't rely on a page that was already open. On desktop, if the browser has kept an old connection open, close and reopen it before testing. A page that loads shows the app can reach that site; to confirm the proxy is working, also consider when the request was made, the client logs, and the expected routing.

Test a Proxied Request, Then Check Direct Connections

If the client logs show request destinations or outbound tags, check for entries timestamped around the time the page loads, then confirm that the outbound matches your routing rules. You can also compare the result on a site you trust to show your public IP before and after connecting, as long as your rules say that site should use the proxy. If it matches a direct-connection rule, an unchanged result is expected. Conversely, a changed IP on one site only tells you how that request was routed; it doesn't mean every app is being routed through the client.

If your configuration has a clear direct-connection rule, visit a destination that should use it and check that it still works without being incorrectly sent through the proxy. If you don't already have a suitable direct-connection test, skip this step rather than adding a temporary rule. Use the same device and network for both checks. Switching between Wi-Fi and mobile data can change your public IP and make the comparison unreliable.

Change One Thing at a Time When Troubleshooting

If no matching request appears after you try to connect, first check whether the test app uses the system proxy, whether per-app settings exclude it, and whether the log level shows requests. No log entry doesn't necessarily mean the request never reached the client. If the logs show a proxied request that then times out, keep the entry point and routing unchanged, switch to another server in the same group, and retry the same page. If both fail, note where the error occurred, the client's message, and whether you used the system proxy or Android connection, then search the FAQ by symptom. Remove subscription URLs, server credentials, and other sensitive details before sharing logs.

Once the test succeeds, keep the mode you've verified; there's no need to enable TUN or change routing. For a temporary test in v2rayN, choose Clear system proxy from the tray, then exit the client. If you noted the previous proxy settings, restore them afterward. In v2rayNG, tap Stop on the main screen and confirm that Android's VPN status ends; restore any per-app settings you changed for the test. If something goes wrong later, check in this order: the server appears in the list, the client is running, and the app's requests match your routing rules. There's no need to start by reinstalling.