V2Ray Setup Guide

Import a subscription, choose a proxy mode, connect to a node, and verify the connection. Already installed a client and have a subscription URL? Start with step one.

Step 1: Import a Subscription and Update the Node List

Make sure you copied a subscription URL, not an account page URL or a single-node share link. A subscription URL lets the client update a group of configurations at once; import a single-node share link using the client's clipboard import feature. Either type of link may contain account credentials, so don't post the full URL in public logs, screenshots, or online conversion tools. Keep its query parameters intact when copying; remove only accidental spaces or line breaks.

Desktop v2rayN: In the main window, open “Subscription Group” and go to “Subscription Group Settings” to add a group. Give it a recognizable name, paste the URL into the subscription URL field, and save. Back in the main window, use the “Subscription Group” menu to update the current group. If the menu offers updates with or without a proxy, try the direct update option first when no working node is available. Once the update finishes, switch to the new group and confirm that server entries appear—not just the group name.

Android v2rayNG: Open “Subscription Group Settings” from the side menu, tap Add, enter a name and URL, then save. Return to the node list, open the top-right menu, and select “Update Subscription.” Check the relevant group afterward. If you were viewing a different group, a successful update may not switch the current view. Select the new group or show all nodes before deciding that nothing was imported.

If the list is empty, first determine whether the download failed or the download succeeded but parsing did not. For a download failure, check whether the device's current network can reach the subscription source and whether the URL has expired. Parsing often fails when the link returns a login page or uses a format the client doesn't recognize. Ask the provider which subscription type to use before changing node ports or enabling TUN. Once nodes appear, note one node's name and group; use that same entry for the tests below so you don't mix up the effects of changing nodes and modes.

Step 2: Choose a Proxy Mode and Routing

The proxy mode determines whether an app's requests reach the client; routing determines whether those requests go direct or through the proxy. For the initial setup, choose a mode that covers the app you're testing and keep the default routing rules. Changing the system proxy, routing, and DNS all at once makes it difficult to identify the cause if a page won't load.

Desktop v2rayN: To start with a browser test, choose “Set system proxy automatically” under “System Proxy” in the tray menu. “Automatically” means the client configures the system proxy; it does not route all device traffic through the client. Browsers that follow system settings should work for this test, but apps with their own proxy settings may ignore them. If you previously set a proxy directly in the browser, note the old value and make sure the browser now uses the system proxy. Don't let an extension change the same setting at the same time.

Android v2rayNG: To test with a browser, use VPN mode so the client can capture app traffic. If the service mode was changed to proxy-only, switch it back to VPN in settings. Check that per-app proxying or an exclusion list isn't leaving the test app out. For now, just choose the mode; Android will request VPN permission when you start the service. If another app is already using the VPN, consider the effects before disabling it. On managed devices, follow your organization's network policies.

Routing Rules: Keep the Current Rules First

If your current configuration already has routing rules, note which rule set is active. For a useful test, choose two targets with clear expected outcomes: one that should go through the proxy and one that should connect directly. A direct connection only confirms that the request succeeded; it doesn't prove the proxy node works. Likewise, seeing a proxy exit IP for one site doesn't mean every app is using the proxy. You don't need to import a full new rule set for the first test—check whether the existing rules produce the expected results. For details on protocol, transport, and core compatibility, see the protocol handbook.

TUN Mode: Enable It Only When Needed

If a desktop app ignores the system proxy and has no proxy settings of its own, consider v2rayN's TUN mode after confirming the node works. TUN captures traffic through a virtual network interface; it is separate from the system proxy toggle in the tray menu. Before switching it on, note your current settings and make sure the system allows virtual interfaces. Afterward, retest with the same node and app. If local services stop working, turn TUN off, restore the previous mode, and test again. Then check for conflicts with other virtual adapters, routes, or DNS settings.

Step 3: Select a Node and Start the Connection

Return to the subscription group you checked in step one and choose a node with a clear purpose for the test. If the group contains several entries with the same name, distinguish them by their remarks, protocol, and group. The subscription already includes the node settings, so you don't need to re-enter them for a first connection. If fields are missing or the core reports an unsupported feature, check the subscription type and client version. Don't copy an address, security layer, or public key from another node to assemble a configuration.

Desktop v2rayN: Right-click the test node in the server list and choose “Set as active server.” If your version lets you activate a node by double-clicking, check which entry the interface marks as active. Highlighting a row doesn't always switch the outbound server. After setting it, check the information or log area and confirm the core starts without repeatedly exiting or reporting that a local listening port is already in use. Then check the system proxy status in the tray and make sure it hasn't changed from the mode you chose in step two.

Android v2rayNG: Tap the target node and confirm the selection indicator moves to the right entry, then tap the Connect button in the bottom-right corner. The first time you start VPN mode, check the app name in Android's permission prompt and approve the request. Back in the list, make sure the button changes to a stop control. If Android shows a VPN status indicator, check that too. If the button immediately returns to its disconnected state, check the client logs and system permission instead of tapping repeatedly and obscuring what happened.

A connected status means the local service has started or the system has established a traffic-capture route; it doesn't prove requests are reaching the remote server. If the logs show a local port conflict, close duplicate client instances or check the listening port. If the remote connection times out, check the current network, node address, and port; if needed, compare with another known-working configuration from the same subscription. Change only one variable at a time. Once the service stays running, move on to the actual traffic test.

Step 4: Verify That the Target App Uses the Proxy

Open the browser you plan to test, start a new page, and visit a target that should use the proxy under the current rules and that you're authorized to access. Generate a fresh request rather than relying on an already-open page or cached content. Note the time, then check the client logs for requests from that moment. If the logs show the destination and outbound, compare them with the expected routing rule. If you use an exit-IP lookup service, check only the result of this request and compare it with the expected proxy exit; that result applies only to traffic received by that lookup service.

If the page loads but there's no matching log entry, first check whether the test app follows the system proxy or is excluded by Android's per-app settings. The log level may not record every request, so a missing entry alone doesn't prove traffic bypassed the proxy. If the logs show a direct outbound, return to routing rules and check the destination's rule and priority; there's no need to import the subscription again. If only one app fails while the same target works in a browser, check that app's proxy settings and whether its traffic is being captured.

If the request matches the proxy outbound but the page still won't load, start with the earliest error in the logs. For a DNS lookup failure, check DNS and the current network. For a connection timeout, compare another known-working node on the same network. For a handshake error, verify the node settings, core support, and device time. Don't weaken transport security to troubleshoot. A successful page load in one browser doesn't verify the app you actually need; once the browser works, run the same test in that app.

When you're done testing and don't plan to keep using the proxy, stop traffic capture on desktop and make sure the system proxy is back to its previous setting. Turn off TUN separately if you enabled it. On Android, tap Stop and confirm the VPN has disconnected. If direct connections still fail afterward, check whether the desktop system proxy still points to a stopped local proxy or Android is set to keep the VPN always on. Keep a note of the working group, node name, and mode. Next time, update the subscription and repeat the checks without reconfiguring everything.

Download a Client