V2Ray Client · First-Time Setup
v2rayN Quick Start
Import a subscription, choose a proxy mode, connect, then check whether your traffic is being proxied.
Before you start, get a working subscription URL and make sure your device can open websites. Haven't installed the client yet? Choose an installer from the download page. This guide uses one subscription and one configuration. Once connected, you can add groups or adjust routing as needed.
Step 01
Import a subscription and update the list
A subscription URL points to a set of server configurations that can be updated. Adding the URL to the client only saves the source; you must also run an update for the servers to appear in the list. Copy the entire URL, including any parameters after the question mark. Don't include a label, quotation marks, or sharing instructions. Subscription URLs may contain access credentials, so don't paste the full URL into a chat or screenshot.
v2rayN: Add a subscription group
Open the main window and go to “Subscription group” → “Subscription group settings,” then click “Add.” Enter a recognizable label in the remarks field and paste the subscription URL into the address field. Confirm, then return to the main window. Select the new group and use the “Subscription group” menu to update that group. For a first-time setup with no working proxy yet, choose the “Update without proxy” option if the subscription URL is directly accessible. If you already have other subscriptions, there's no need to update them all; this keeps errors from older groups separate from this import.
v2rayNG: Save the URL and update manually
Open the sidebar from the main screen and go to “Subscription group settings,” then tap the plus icon. Enter a label and subscription URL, make sure updates are enabled for the group, and tap the save button. Return to the main list and select the new group. From the more options menu in the upper-right corner, choose “Update subscription.” When the update finishes, check the current group. If another group is still selected, switch back to the new one before checking whether the import worked.
Before continuing, make sure the new group contains at least one selectable configuration. If the list is still empty, check the update message: a request timeout and a parsing error have different causes. For a timeout, first check whether your current network can reach the subscription source. For a parsing error, make sure you copied a subscription URL, not a login page, subscription information page, or single share link. Don't try to fix a list that hasn't imported by switching TUN or changing DNS. If you're unsure which type of URL you have, see the subscription and node entries in the glossary. Once configurations appear, continue to the next step.
Step 02
Choose a proxy mode
The proxy mode determines how app traffic reaches the client; the server configuration in the list determines which remote server the client tries to connect to. These are separate choices: selecting a server doesn't mean your browser is using the proxy, and enabling a proxy mode won't fix an invalid server configuration. For your first test, use a standard option built into the client and keep your existing routing and DNS settings. This makes it easier to pinpoint the source of any issue.
v2rayN: Start with the system proxy
Find “System proxy” at the bottom of the window or in the tray menu. For a standard browser test, choose “Set system proxy automatically” and leave “Enable Tun” off. If an app or your system already has a proxy required by your organization, note the existing settings first; on managed devices, follow your network requirements. To establish a baseline, open an accessible test page in your browser first. After setting an active server in the next step, enable the system proxy.
“Clear system proxy” removes the system proxy settings. “Do not change system proxy” means the client won't modify the current settings; it doesn't turn off a proxy that's already active. A browser extension can also set its own proxy, independently of the system settings. For your first test, use a browser that follows the system proxy and don't rely on apps with their own proxy rules.
v2rayNG: Choose VPN mode
Open “Settings” in the sidebar, find the mode option, and select “VPN mode.” In some versions, the mode setting is in the main screen menu, or VPN mode is enabled by default. If “Proxy only” is available, use it for apps that explicitly connect to a local proxy; it won't work for testing in a browser that hasn't been configured to use one. For your first test, keep your current per-app proxy settings. If you previously set an app scope, make sure the test browser isn't excluded.
Choosing a mode is just preparation. Android usually asks for VPN permission when you start the connection; on desktop, you also need a usable active server. Next, return to the configuration list and start one configuration. Don't change routing, DNS, and proxy mode all at once. For details on how system proxy and TUN differ in their traffic coverage, see the advanced guide after you've confirmed the connection works.
Step 03
Connect with a configuration
Return to the subscription group you just updated and select a configuration to test. Note its label so you can tell which test it belongs to when checking logs or switching configurations later. Don't mistake a highlighted row, a test result in the list, or a successful subscription update for an active configuration handling your traffic.
v2rayN: Set an active server
Right-click the target in the server list and choose “Set as active server” or an equivalent menu option. Check the list or status area to confirm the selected configuration is active, then enable “Set system proxy automatically” from the bottom of the window or the tray menu. Keep the client running; minimizing the window is fine, but don't exit the process. On desktop, you usually won't find a Connect button like the one in the Android app. Once the configuration is active, apps such as your browser send requests, and the core attempts to connect to the remote server for each request.
If an error appears in the message area as soon as you set the active configuration, address it before testing a webpage. For example, if a local listening port is already in use, check whether another proxy client is running; don't close unfamiliar system processes. If the configuration isn't compatible with the current core, try a known-compatible configuration from the same group before deciding whether to change the core.
v2rayNG: Select a configuration and connect
Tap the target configuration in the list and make sure the selection indicator moves to it. Then tap Connect in the lower-right corner of the main screen. The first time you use VPN mode, check the app name in the system prompt. If it identifies v2rayNG, allow the connection. Return to the client and confirm the button now lets you stop the connection. A VPN indicator may also appear in the status bar. If another VPN is running, check whether it's OK to disconnect it first. Don't force a replacement if your work device's connection is managed by an administrator.
If the button returns to the disconnected state immediately after starting, note the message and check system permissions or the client logs. If the connection stays active, proceed to the webpage test. A connection indicator only shows that the local service has started; it doesn't prove that a specific webpage is using the proxy or that the remote server accepted the request.
Step 04
Verify the proxy is working
Compare the same webpage before and after
In the browser you chose in step two, visit the same test page. Keep the same network, open a new tab, and refresh so you don't mistake a previously loaded page for a successful new request. First make sure the page loads, then check whether the request took the expected route. If the test domain is set to connect directly under your current routing rules, it's normal for the page to open both before and after connecting. That alone doesn't mean the proxy isn't working. Choose a test destination that your current rules are expected to proxy; there's no need to route all traffic the same way just for this test.
If you use a test page that shows your public IP, treat a changed address as evidence only when that page is routed through the proxy and the expected exit IP differs from your direct connection. To avoid sending requests to an extra testing service, you can instead compare the refresh time, destination domain, and outbound entry in the client logs, if available. Core startup messages alone don't show whether a particular request was proxied. Before viewing or sharing logs, remove subscription URLs, account parameters, and other information that shouldn't be public.
Narrow down the cause based on what you see
If your browser can reach ordinary websites but requests expected to use the proxy don't appear in the client, first check on desktop that the system proxy is still enabled and the browser uses it. On Android, check the VPN status and per-app scope. If the logs show that a request reached the client but the remote connection failed, try a known-working configuration in the same mode, then revisit the same test page. If only one configuration fails, focus on that configuration. If they all fail, use the error message to check for a DNS resolution, remote connection, or authentication issue. Change one setting at a time so you can tell which change affects the result. For specific errors, see the FAQ.
Disconnect and confirm your connection is restored
When you're done testing, choose “Clear system proxy” from the bottom of the window or the tray menu in v2rayN, then exit the client. If the system already had a proxy before the test, restore the settings you noted earlier; clearing the proxy isn't the same as restoring them. In v2rayNG, tap the connection button again to stop the service and make sure it returns to the disconnected state. Then make a fresh webpage request to confirm your device is back to its original connection method. Your first setup is complete when the subscription list contains a configuration, the test request takes the expected route, and your network works as before after disconnecting.