Quick V2Ray Client Setup: From Subscription Import to Connection Verification

Before you begin, confirm that the appropriate client is installed on your device. Use v2rayN on Windows, macOS, and Linux desktop devices, and v2rayNG on Android. If it is not installed yet, visit the client download page and choose a version for your platform. After installation, launch the client normally. There is no need to change core, port, DNS, or TUN settings yet; a first setup only requires the subscription, active server, and connection switch.

You also need a working subscription URL. It is usually a link beginning with https://, provided by your subscription service. Unlike a single vmess://, vless://, or trojan:// configuration, a subscription URL can provide multiple servers and be updated later by the client. Copy the URL from beginning to end without adding spaces, line breaks, or explanatory text automatically inserted by a chat app.

If you received a QR code, a single protocol link, or a complete configuration instead of a subscription URL, the import entry will be slightly different. This guide focuses on the most common subscription workflow; for single-node imports, QR recognition, and configuration migration, see the installation and configuration section in the Help Center. Whatever the format, the later workflow—choose a proxy mode, connect, and verify—is largely the same.

The goal of subscription import is not merely to save a link in the client, but to have the client read its contents and generate a server list. This step therefore has two consecutive actions: add a subscription group, then run a subscription update. If you save the link without updating it, the main interface may remain empty—one of the most common first-time oversights.

v2rayN Desktop: Add a Subscription Group

Open the v2rayN main window and find “Subscription Groups” or a similarly named subscription management entry in the top menu, then open “Subscription Group Settings.” Some versions place it in a submenu under Subscriptions; if the main window is narrow, expand it to view the full menu. On the settings page, click “Add” or a button with a plus sign to create a subscription group.

Enter an easy-to-recognize name in the “Alias” or “Notes” field, such as “Daily Subscription.” This name is only used for local organization and does not affect server settings. Paste the copied subscription URL into the URL field. Check that there are no spaces at either end, save the settings, and return to the v2rayN main window. The group now exists, but its server content may not appear immediately.

Open the “Subscription Groups” menu again and choose “Update All Subscriptions,” or update the group you just created. The client will request the subscription content and parse its server configurations. After a moment, the main server list should show items such as protocol type, server alias, and transport method. The number of entries depends on the subscription, so do not use a fixed count as the success criterion. Once selectable server rows appear and the logs are not showing persistent parsing errors, continue to the next step.

v2rayNG Android: Add and Update a Subscription

In v2rayNG, open the side menu and go to “Subscription Group Settings.” Tap the plus sign in the upper-right corner to create a group. Enter an identifying name in the notes field, paste the complete subscription URL into the address field, and save it. Return to the main page, open the upper-right menu, and choose “Update Subscription,” or update the current group from the subscription group page.

After the update finishes, the main page will show a set of configuration entries. Each usually displays an alias, and some versions also show the protocol or an address summary. Tapping an entry only selects it; it does not start the connection. The selected configuration typically has a color marker, check mark, or highlighted background. For now, simply confirm that the list was created and avoid repeatedly toggling multiple switches.

How to Diagnose an Empty List After Updating

Return to the subscription settings and reopen the group you saved to check whether the URL is complete. If the URL was truncated at the end, pasted twice, or contains line breaks, delete it and paste it again. Confirm that the group is enabled, then run the update. If the log says the content cannot be retrieved, open an ordinary website using the device's current network to confirm basic connectivity. If only this subscription fails to update, check whether the subscription URL itself is still valid.

If the update reports success but no new configurations appear, check whether the client has enabled server filters or whether the current view is showing a different group. Switch to “All Servers” or the subscription group you just added, then check the list again. For more detailed troubleshooting of subscription formats, Base64 content, and filter rules, see the Help Center. This page continues with the basic connection workflow once the server list is visible.

Once the server list is ready, avoid changing a large number of rules immediately. Two easily confused concepts need to be separated: how the client takes over traffic, and which requests use the proxy after that takeover. The first is usually presented as “System Proxy,” a “Connection” switch, or “TUN Mode.” The second is generally called “Routing Mode” or “Routing Rules.”

v2rayN Desktop: Start with the System Proxy

For a first v2rayN setup, use the system proxy for the initial verification. It provides a connection for browsers and apps that follow the operating system's proxy settings, has a shorter workflow, and is easy to disable if something goes wrong. Find the system proxy control in the main window's bottom status bar, tray menu, or “System Proxy” menu, and switch from “Clear System Proxy” to “Automatically Configure System Proxy,” or the equivalent enable option in your version.

Next, review the “Routing” or “Routing Mode” setting. If the client already includes default rules, keep them for now. Common modes include global, rule-based routing, and direct connection: global mode sends more eligible requests through the current server; rule-based routing chooses the route by domain, address, and preset rules; direct mode is mainly for temporarily disabling the proxy path. For a first everyday setup, the default rule-based mode is usually preferable to building complex custom rules.

TUN mode can cover more apps that do not read system proxy settings, but it involves a virtual network interface, DNS interception, and routing tables, so it is not necessary for a first connectivity test. First confirm that the subscription and server work normally through the system proxy. If you later need full-device routing, configure it step by step using the TUN Mode chapter in the Advanced Usage Guide. This keeps subscription, server, and traffic-coverage issues separate during troubleshooting.

v2rayNG Android: Confirm the Current Configuration and Routing

The v2rayNG main page usually shows the currently selected configuration, with a connection button at the bottom or lower right. In the settings page, look for “Routing Settings,” “Predefined Rules,” or a similarly named option. Keep the default routing for your first setup. If a predefined rule set is already selected, there is no need to change it just to explore more options. The default configuration is best for first confirming that the server can connect.

When starting a connection on Android, the system may show a network connection permission prompt. Read it and confirm permission so the client can create its local network interface. Handle this prompt only when Android requests it; if you cancel, the main page may quickly return to a disconnected state. Tap the connection button again and complete the system prompt—there is no need to re-import the subscription.

When Should You Change the Mode?

If the browser works normally but a desktop app that does not read system proxy settings bypasses the client, consider TUN mode after completing the basic connection test. If only certain addresses should use the proxy, use rule-based routing instead of repeatedly switching servers. If a local device, LAN service, or commonly used direct address is affected, check LAN bypass and direct-connection rules. These are optimizations for an already working connection and should not be changed during the first startup.

Connecting consists of two actions: selecting the active server and starting traffic takeover. Highlighting a server without enabling the system proxy or connection switch does not automatically route app traffic through the client. Conversely, an enabled connection switch cannot establish the intended connection without a valid active server. Follow the fixed order: select a server first, then start the connection.

v2rayN Desktop: Set the Active Server

In the main server list, click the entry you want to use and confirm that the entire row is selected. Then press Enter or open the context menu and choose “Set as Active Server.” Depending on the version, the current server may be indicated by bold text, a color marker, a vertical bar on the left, or status bar text. The important point is not a specific visual style, but that the active item is clearly identified in the bottom of the window or the server list.

After confirming the active server, check that the system proxy is still enabled as described in the previous step. If the status bar still says “System Proxy Not Set” or “Clear System Proxy,” open the system proxy menu and switch to automatic configuration. v2rayN will then start its local core and generate the relevant configuration. The bottom of the main window usually shows the local port, system proxy status, or current server name, while the log area begins displaying startup messages.

Do not treat latency test results in the server list as the only measure of success. A latency test only shows whether a particular probe received a response; it does not prove that browser traffic is correctly passing through the client. For a first setup, choose a server marked as commonly used by the subscription provider when possible. If no guidance is available, pick any entry for a real connection test. Try another one only if needed to rule out a problem with an individual server configuration.

v2rayNG Android: Select a Configuration and Tap Connect

On the v2rayNG main page, tap a configuration entry to make it current. A selection marker usually appears at the top or beside the entry. Then tap the circular connection button at the bottom of the page. If Android displays a network connection request on the first launch, confirm it and wait a few seconds. After a successful connection, the button's appearance changes, the page status switches from disconnected to connected, and the system status area usually shows an ongoing connection notification.

If the connection stops immediately after you tap it, open the v2rayNG logs and inspect the last few lines. Common causes include an unparsable server configuration, an expired subscription, a significant device time difference, or a temporary inability to reach the target address. Do not tap the connection button repeatedly in quick succession. Stop once, confirm the selected configuration, and start again. Rapid switching mixes multiple startup records into the log and makes diagnosis harder.

Use the Logs to Identify the Startup Stage

During a normal startup, the logs typically show configuration loading, core startup, and local connection listening before entering a waiting state. No new log entries do not necessarily indicate failure; there may be no app requests until you open a website. Pay attention instead to recurring error lines such as unrecognized configuration fields, address resolution failures, connection timeouts, or ports already in use.

If the desktop client reports that a local port is already in use, first close other clients using the same proxy port, then restart v2rayN. If v2rayNG says the current configuration is unavailable, stop the connection, choose another configuration from the same subscription group, and try again. More complete explanations of log keywords and issue categories are available in the troubleshooting section of the Help Center.

When verifying the connection, do not rely only on the button color or the highlighted server. A more reliable approach is to watch three places at once: the client's connection status, request records in the logs, and the actual result in your browser or app. Together, they help identify whether the issue is with the subscription, server, traffic-takeover method, or the specific app.

Test an Ordinary Website First

Keep the client running, open your usual browser, create a new tab, and visit a commonly used website. First disable any separately configured proxy extension in the browser so it does not override the operating system proxy settings. Once the page loads, open another tab and repeat the test. If v2rayN logs show new connection records during browsing, the browser requests have reached the client; in v2rayNG, activity may also appear in the logs or connection status.

If the browser is still using the connection state from before the client started, close it completely and reopen it. Some desktop apps read system proxy settings only at startup and may not refresh them after the proxy is switched while they are running. Restarting the app is more direct than repeatedly changing client ports. For desktop programs that do not read system proxy settings, note this behavior and consider TUN mode only after the basic test is complete.

Status Looks Normal, but Websites Do Not Open

Return to the server list and confirm that the active server is still the entry you selected. Stop the connection, choose another server from the same subscription, and start again. If access works after switching, the issue is usually concentrated in the original server configuration rather than the client installation. If several servers behave the same way, check whether the subscription updated successfully, whether the device date and time are accurate, and whether the current network can resolve domain names normally.

Next, check the proxy mode. v2rayN users should confirm that the system proxy is not set to “Clear” and that the browser is not separately configured to never use a proxy. v2rayNG users should confirm that the connection button is still running and that the system has not stopped the client because of battery-saving policies. Resolve these basic status issues before changing DNS or routing rules; changing DNS too early often turns a simple switch problem into a stack of configuration issues.

Websites Work, but Some Apps Do Not

This usually means the server connection itself is working and the difference comes from whether the app follows the current traffic-takeover method. v2rayN's system proxy mainly affects programs that read the operating system proxy settings; some independent network programs connect directly. Do not re-import the subscription or delete a server that already works. First check the app's own proxy settings. If broader coverage is genuinely required, read the TUN Mode Configuration.

If only certain domains behave abnormally, the cause is more likely related to routing or DNS. Temporarily switch back to the client's default routing and check whether the issue disappears. Once the default route works, restore custom rules one at a time, applying the configuration and testing after each change. Subscription filters, DNS priority, FakeDNS, and custom outbounds are advanced topics best handled separately after the basic connection is stable.

How to Tell Whether All Four Steps Are Complete

A complete setup should meet these conditions: the client maintains a stable connection; the main interface identifies the active server; browser requests appear in the logs; stopping the client changes the status and access path accordingly; and restarting the client does not require importing the subscription again. These conditions show that subscription storage, server selection, traffic takeover, and the connection workflow are all in place.