v2rayN Setup Guide

subscription import

Import a V2Ray subscription link

The completion criterion for this stage is clear: selectable servers appear in the client's main list. Only proceed to proxy mode settings after the list appears; if it is still empty, do not click Connect yet.

v2rayN desktop steps

First copy the complete V2Ray subscription link. After opening v2rayN, use the top menu to open “Subscription groups” or a similarly named subscription management entry, then add a new subscription group. Give the group a recognizable service name and paste the copied link into the address field. Check that there are no extra spaces and that the address was not truncated by line breaks from a chat app, then save it.

Saving the group only records the address; you still need to run an update. Return to the subscription menu and choose Update current subscription or Update all subscriptions. Once processing begins, new configuration rows will appear in the server list, usually showing an alias, address, port, and transport. For now, just confirm that the list appears instead of editing protocol parameters one by one. The subscription already supplies those parameters, and manual changes can easily make them inconsistent.

If no configurations appear after the update, reopen the subscription group settings and check that the address was saved to the correct group. Confirm that the local network still works, then run the update once more. If the client reports that the subscription is empty, the format is unrecognized, or the request failed, ask the subscription provider to verify the link instead of creating several identical groups. Duplicate groups create duplicate servers and make it difficult to tell which group is still updating.

v2rayNG Android steps

Open the v2rayNG side menu, go to “Subscription group settings,” and tap the add button. Enter a recognizable remark, paste the complete subscription link into the address field, save it, and return to the main screen. Open the menu again and run “Update subscription.” When the update finishes, one or more configurations will appear in the main list. Tapping one makes it the currently selected configuration, usually indicated by a color change, a check mark, or a change in list position.

Android may restrict an app's background network activity. During the first import, keep v2rayNG in the foreground until the update finishes, then switch apps if needed. If the system interrupts the update, return to the main screen and run it again. Do not tap repeatedly while the update is still in progress, or a network error may be mistaken for a subscription format problem.

After a successful subscription update, the client stores a copy of the configurations retrieved at that time. When the provider changes its servers, run Update subscription again. Updating does not automatically change the proxy mode or prove that the connection works; it only syncs configurations to the client. For expired subscriptions, update failures, duplicate servers, and group management, see Troubleshooting.

traffic scope

Choose a proxy mode

The mode determines which traffic the client handles. For first-time use, choose a straightforward combination that is easy to assess; there is no need to write complex routing rules immediately.

Distinguish system proxy from routing mode

In the v2rayN desktop client, “system proxy” and “routing mode” operate at different levels. The system proxy determines whether apps that support system proxy settings send requests to v2rayN. The routing mode determines whether requests entering the client use the proxy or a direct connection according to its rules. If you change only the routing mode without enabling the system proxy, the browser may continue using its original network path. If you enable the system proxy but choose the wrong routing policy, some websites may still behave unexpectedly.

For first-time setup, select “Automatically configure system proxy” from the tray menu or main screen, then set the routing mode to “Bypass LAN” or the rule mode provided by the client. Local routers, printers, and LAN addresses will usually remain direct, while other requests are handled by the configured rules. For a short troubleshooting test, you can temporarily use Global mode to determine whether split-routing rules are causing the problem, then switch back to your everyday mode when testing is complete.

Where to find the mode in v2rayNG

v2rayNG asks Android to create a local VPN interface when connecting, so there is no desktop-style “system proxy” switch to find. Before the first connection, the default routing settings are usually sufficient for basic verification. If “Predefined rules,” “Bypass LAN,” or per-app proxy settings have already been changed, note their current values first, then temporarily restore a simple state you can explain.

Per-app proxying specifies which apps use the connection. It is useful for fine-grained configuration later, but not for first-time verification. If you select only a few apps at the start, the browser used for testing may not be on the allowed list, leading to the false conclusion that the server has failed. Complete one full connection and access test first, then narrow the app scope based on your needs so the path is easier to troubleshoot.

After this step, the desktop client should be ready for system traffic to enter v2rayN. On Android, keep the routing settings clear and simple while preparing to start the connection. The next step does only two things: select one configuration and start the client.

active server

Select a server and connect

Identify the active server before connecting. A server appearing in the list does not mean it is selected, and a started client does not mean system traffic is using the current configuration.

Set the active server in v2rayN

Return to the v2rayN server list and click the server you want to use. Set it as the current server by double-clicking it, choosing “Set as active server” from the context menu, or using the corresponding shortcut. Labels may vary slightly between versions, but a successful selection usually shows a marker on that row, while the status bar or tray menu displays the current server name.

Next, check that the client core has started. Normally, the main log area shows startup and listening messages, and the tray icon status changes. If the system proxy is not enabled, return to step two and select “Automatically configure system proxy.” The order is not absolute, but all three conditions must ultimately be met: an active server exists, the core is running, and apps that need the system proxy have received the correct proxy settings.

Do not treat a latency test as the Connect button. Test results only help assess whether a configuration responds; they do not replace “Set as active server” or “Enable system proxy.” Likewise, the first server in the subscription list does not necessarily become active automatically. Follow the active status shown by the client.

Start the connection in v2rayNG

In the v2rayNG main list, tap a configuration and confirm that it is the current item, then tap the circular connection button at the bottom of the main screen. The first time, Android displays a connection request; read the system prompt and confirm it. Once connected, the button changes state and the system status area shows the corresponding connection indicator.

If the connection immediately returns to a disconnected state, do not switch rapidly among many servers. Open the v2rayNG log and check the last few lines for a configuration error, unreachable network, or local port problem. Then return to the subscription page, run an update, and select the current configuration again. If only one configuration fails while others connect, the problem is more likely with that server or its parameters. If all configurations behave the same way, check the local network, system time, and app permissions first.

If you see one brief error during connection and the log then returns to normal, continue with verification. If the same error persists, repeated restarts usually will not change the result. Note when the error occurs—during subscription update, core startup, DNS resolution, or remote connection—then search Troubleshooting Manual by symptom. This is faster than reinstalling at random.

result check

Verify that the proxy works

Check both the webpage result and the client log during verification. Looking only at the connection icon can miss system proxy settings, separate browser configuration, or routing rule problems.

Make a fresh access request first

Keep the client connected, close the browser tab used for testing, and open a new tab to visit a commonly used website you have not opened yet. A new page reduces interference from cached content and existing connections. If it opens normally, visit two or three different domains in succession and check that they load consistently. Do not simply refresh a page that has already been fully cached; it may not generate enough new network requests.

During desktop verification, watch the v2rayN log area as well. When the browser makes a new request, the log will usually show a new connection entry. If the webpage generates requests but the log does not change at all, first check that the system proxy is enabled and that the browser is not using a separate proxy. Some browsers inherit system settings, while some apps use their own network configuration, so one app's behavior cannot represent the entire client.

On Android, reopen the browser while keeping v2rayNG connected. If per-app proxying is enabled, confirm that the test browser is included. If it is not enabled, keep the default scope for the first verification. After verification succeeds, add detailed rules and repeat the same test after each change so you can identify which setting changed the result.

Troubleshoot a connection that does not work in order

If the page will not open, disconnect the client first and confirm that ordinary local websites are still accessible. Once the basic network works, reconnect and check that the client still shows the current server. Then update the subscription, select the server again, and recheck the proxy mode. This separates the problem into four layers—local network, configuration source, connection status, and traffic entry—instead of mixing every setting together.

1. Check the local network

   Disconnect the client and test an ordinary webpage. If it also fails, fix the Wi-Fi, wired network, router authentication, or system network issue first.

2. Check the system time

   Enable automatic synchronization for the date, time, and time zone. A significantly incorrect system clock can affect connections that require certificates and time validation.

3. Check the subscription and active server

   Confirm that the subscription was updated recently, the list is not empty, and the active server is the one you intend to test.

4. Check whether traffic reaches the client

   On desktop, verify the system proxy. On Android, verify the connection status and per-app scope, then check whether the new request appears in the log.

5. Compare with another configuration

   Change only one server while keeping all other conditions unchanged. If the behavior differs, you can better determine whether the issue is limited to one configuration or comes from local settings.

If the log shows a clear symptom such as DNS failure, port conflict, connection timeout, or an ineffective system proxy, there is no need to cover every advanced option here. Find a short answer in Troubleshooting, or use the chapter-by-chapter process in the Troubleshooting Manual for a systematic investigation.