First Connection · 4 Steps

V2Ray Quick Start

Go from importing a subscription to checking your exit IP by routing one browser request through one node. You’ll need a client and an authorized subscription URL. Haven’t installed a client yet? Choose a package on the downloads page, then come back here.

Import a Subscription: Make Sure Nodes Appear in the Group

Copy the full subscription URL from your provider. Don’t use an account login page or paste a single node’s share link into the subscription URL field. Subscription links may contain access credentials, so paste them only into the client’s subscription settings. Blur the URL and node identifiers in any screenshots you share for help. If you already have a working configuration, keep its group and create a new one with a clear name to avoid mixing old and new nodes in the same list.

v2rayN on Desktop

Open the main window and find the “Subscription Group” menu at the top, then choose “Subscription Group Settings.” Add a group, enter a name and subscription URL, and save. Back in the main window, select the group you just created, then use the “Subscription Group” menu to update it. If this is your first setup and you don’t have a working proxy, try updating without a proxy first. Updating through a proxy may send the request through a connection that isn’t available yet. When the update finishes, make sure servers appear under the selected group.

v2rayNG on Android

Tap the top-left menu and open “Subscription Group Settings.” Tap the add button, enter a name and URL in the corresponding fields, then tap the checkmark in the top-right corner to save. Return to the main screen, open the top-right menu, and select “Update Subscription.” When the update finishes, switch to the group you created and check for nodes. If the main screen has a search term or filter applied, clear it so nodes aren’t hidden. You don’t need to connect yet; seeing nodes means the import step is complete.

Saving a group only means the client has stored the URL; it doesn’t mean the configuration has been fetched. If the list is empty, first make sure you’re viewing the new group and that an update has run, then check the message: a request timeout and an unreadable response are different problems. For a timeout, check whether your current network can reach the subscription service. If the response can’t be parsed, confirm that your provider supplied a subscription format supported by the client. If you’re stuck, see how to troubleshoot subscription update failures. Once nodes appear, move on to proxy settings.

Choose a Proxy Mode: Route Traffic to the Client, Then Choose Where It Goes

Keep two settings distinct. System proxy or VPN mode determines whether app traffic reaches the client. Routing rules determine whether traffic that reaches it is forwarded through a node or sent directly. Enabling the system proxy doesn’t mean every app will use it, and global proxy routing won’t capture requests that never enter the client. For your first check, use one browser and configure traffic entry and routing separately.

Use the System Proxy on Desktop and VPN Mode on Android

Find “System Proxy” at the bottom of the v2rayN main window or in the tray menu. After choosing a node, select “Automatically Configure System Proxy” so browsers that honor the system proxy settings can use the client. Leave the browser’s proxy behavior at its default. If it has a separate proxy configured or an extension is handling connections, the result won’t tell you whether v2rayN’s system proxy is working. You don’t need to enable TUN or switch between multiple connection methods for the first check.

In v2rayNG settings, make sure VPN mode is selected. It uses Android’s VPN interface to route app traffic through the client; approve the system prompt when you connect for the first time. If you’ve enabled per-app proxying, check whether it’s set to “Proxy only selected apps” or “Bypass selected apps,” and make sure the browser you’re testing will be routed through the client. If another VPN service is already running, check whether you’re allowed to pause it. If not, don’t override settings required by your organization or device management just to run a test.

Use a Clear Routing Setup for Your First Check

In the client’s “Routing” or “Routing Settings,” temporarily select a global proxy preset for your first check if one is available. This routes test traffic that has reached the client through the node. If you want to keep your existing split-routing preset, choose a test page that should clearly go through the proxy. Don’t use a site that should connect directly to compare exit IPs: successful access with no IP change may mean the rule is working as intended. Once the test passes, restore your usual split routing. To distinguish rule matching from how traffic enters the proxy, see the quick reference or the routing troubleshooting guide.

Connect to a Node: Check the Active Node, Then Send a Request

First, record a direct-connection baseline. Stay on the same network. Before enabling the proxy, open a familiar webpage and visit a trusted public IP lookup page. Note the displayed address and whether it’s IPv4 or IPv6. If the proxy is already running, disconnect it using the client’s controls before testing. If ordinary webpages won’t load over a direct connection, fix your basic network connection first; otherwise, it’s hard to tell a local network problem from a node connection failure.

Select a Node and Connect

In v2rayN, open the group you just imported, right-click a node, and choose “Set as Active Server” or the equivalent menu item. Check whether the active server name in the status area has updated; a highlighted row in the list isn’t necessarily the node currently in use. Then choose “Automatically Configure System Proxy” from the “System Proxy” menu and open your test browser. If a core startup error appears as soon as you enable the proxy, keep the first error message and don’t repeatedly toggle the system proxy.

In v2rayNG, select a node on the main screen and check that it’s marked as selected, then tap the Connect button in the bottom-right corner. When the system asks for VPN permission the first time, check which app is requesting it and approve. Return to the client and check that the button shows a running state; you can also check whether the system indicates that a VPN is active. If you denied permission, the button immediately returns to the disconnected state, or the system says another connection is in use, resolve that message before testing webpages.

A running status only means the local service has started; it doesn’t prove that a particular site is reachable. If the client offers a “real connection latency test,” run it once for the selected node to narrow down the issue. TCPing only shows whether a connection to a port is possible; it doesn’t prove that proxy authentication or actual webpage forwarding works. A successful real connection test only confirms that its test destination is reachable. Always make a request from your test browser to verify the result. If you suspect a node is faulty, try one other node in the same group; don’t change networks or routing at the same time.

Check That It Works: Compare Web Access and Your Exit IP

Keep the same network, browser, and IP lookup page you used for the direct-connection baseline. After connecting, don’t rely on a tab that was already open: the page may be cached or may reuse an old connection. Reload the test webpage. If results are inconsistent, fully quit and reopen the browser, then request the IP lookup page again. First make sure the page loads, then compare the address with your direct-connection record. Compare the same type of IP address; don’t use an IPv4 address and an IPv6 address to judge whether your exit has changed.

If the webpage loads, the same type of public IP differs from your direct-connection record, and the current routing rules say the test site should use the proxy, these signs together suggest the request used a different exit. To double-check, disconnect the proxy, reopen the browser, and look up your IP again to see whether it returns to your direct-connection address. This only verifies the specified browser and request; it doesn’t mean other apps use the same exit. Public IPs can also change when your network changes, so stay on the same Wi-Fi or mobile network throughout the comparison.

If the webpage loads but your IP hasn’t changed, check how traffic reaches the client first. On desktop, confirm the system proxy is enabled and the browser hasn’t overridden its proxy settings. On Android, confirm the VPN is running and the browser isn’t excluded by per-app settings. Then check whether routing sends the lookup site through a direct connection. If connection logs are available, find the entries for the test time and destination domain. Check whether the request entered the client and which outbound route it used. An unchanged IP alone doesn’t prove the node is faulty: the lookup may have reused an old connection, or both exits may share a public IP.

If webpages won’t load, disconnect and test the direct connection again. On desktop, clear the system proxy settings you changed from the tray menu. On Android, return to the client and tap Stop. If the device had a fixed proxy configuration before the test, restore it afterward. If direct access works but the proxy still fails, note the error time, platform, client, and connection mode, then continue with the can’t connect troubleshooting guide. If only a few sites are affected, check which routing rule matches those sites rather than importing the entire subscription again.