V2Ray Client Setup Guide
From importing a subscription to verifying the connection. Start with one subscription, one node, and one browser, then adjust the routing scope.
Import a Subscription: Save the URL, Then Update the Nodes
Before you begin, copy the subscription URL for your client from your provider’s dashboard, and make sure the client opens normally. If you haven’t installed it yet, choose the right version on the client downloads page. A subscription URL retrieves a set of node configurations; it isn’t a server address for a single node or your provider’s login page. It may contain credentials that grant access to configuration data, so paste it only into a client you trust. Hide the URL and QR code in recordings or screenshots.
v2rayN for desktop: Open the “Subscription Group” menu in the main window and select “Subscription Group Settings.” Add a group. Give it a recognizable name, such as a short version of the provider’s name, and paste the full subscription URL into the address field. Save, return to the main window, and select the group you just created. From the “Subscription Group” menu, choose the option to update the current subscription. If this is your first setup and no working proxy is available on your computer, choose “Update without proxy” if the menu offers that option. When the update finishes, stay in the group’s list and check that the new nodes belong to it.
v2rayNG for Android: Open the main menu and go to “Subscription Group Settings,” then tap the add button. Enter a group name in the remarks or name field, paste the subscription URL into the address field, and tap Save. Return to the main screen and select the group. Open the more options menu in the top-right corner and tap “Update subscription.” Wait for the nodes to appear before continuing. Seeing the group name on the settings page only confirms that the URL was saved. Nodes from that group in the main list confirm that the update returned configurations the client could read.
If the list is still empty, check whether you selected the wrong group, the update failed, or the response contained data the client couldn’t read. First confirm which group is selected, then check the update message. If it reports a connection timeout, check your network and make sure you copied the full URL. If it reports an unsupported format, return to your provider’s page and confirm that the URL is intended for your client. Don’t paste a webpage link or a single-node link into the subscription field. If an update to an existing group failed, its old nodes may still be listed, so an unempty list doesn’t prove the latest update succeeded. Once you’ve confirmed the result, keep one group for the tests that follow.
Choose a Proxy Mode: Decide Which Requests Reach the Client
The subscription list tells you which nodes are available; the proxy mode determines which apps send requests to the client. After a request reaches the client, routing rules decide whether it connects directly, goes through a node, or gets blocked. Enabling the system proxy doesn’t mean every app uses it, and a page loading in your browser doesn’t prove the request went through a node. For your first test, keep the traffic entry method and test app consistent, or it’ll be hard to tell whether a problem lies with traffic capture or routing.
v2rayN for desktop: Find the tray icon and open the system proxy menu. Look for options such as “Set system proxy automatically” and “Clear system proxy.” For this test, use the system proxy, but don’t configure it for a node that isn’t running yet. First confirm the active node and core status in the next step. The test browser should use the system proxy settings. If it has its own proxy extension, pause the extension or switch to a browser that follows the system settings. Otherwise, the browser may keep using a different route even when the system proxy toggle works as expected.
v2rayNG for Android: For your first test, use the standard VPN service mode. If settings include a service mode option, make sure it isn’t set to proxy mode, which only lets apps connect manually to a local port. Then check per-app proxy settings. If you don’t have a specific reason to filter apps, turn off per-app filtering for now. If you keep it enabled, make sure the test browser is allowed and hasn’t been excluded. Per-app settings determine which apps send traffic to the client; they don’t mean every request from those apps will go through a node.
For this test, keep the client’s existing routing and DNS settings. Don’t enable TUN on desktop, import extra rules, or change DNS at the same time. With default routing, the same browser may use different outbound routes for different sites; that can mean the rules are working as intended. Once you can reproduce a basic connection, see routing rules and DNS settings for more options. When you’re ready, return to the node list and choose a node for this test.
Connect: Check the Active Node and Traffic Capture
Choose a configuration marked as available by your provider from the subscription group you just updated. For your first test, there’s no need to benchmark every node or change protocol or transport settings. Note the node name and connection start time so you can distinguish this session from earlier log entries. If the list contains multiple entries with the same name, check which group each belongs to so you don’t select an older configuration by mistake.
v2rayN for desktop: Return to the server list in the main window. Right-click the node and set it as the active server. Clicking a row may only select it; that’s not the same as setting it as active. Confirm that the current server indicator has changed, then check the runtime information in the window. If configuration loading or the listener fails, fix the startup issue before enabling the system proxy. Once the core is running normally, choose “Set system proxy automatically” from the tray menu and open the browser you’ll use for testing. The client should now receive the browser’s requests, but you’ll still need to verify the route beyond your device.
v2rayNG for Android: Tap the node in the main list and confirm the selection mark is beside the intended entry, then tap Connect at the bottom. The first time you enable it, Android will usually show a VPN connection request. Make sure the request comes from the client you just used, then allow it to establish the service. Wait for the button state to change and check the system status area or the client’s runtime message. If another VPN service is already running on the device, check whether you can pause it. For work devices with configurations controlled by an administrator, follow your organization’s device policies.
The system proxy being enabled on desktop or a service status appearing on Android are signs that traffic capture is set up locally, not proof that requests are reaching their destination. If the button switches back off immediately or the log reports an error on startup, keep the current settings and check the first error. If another process is using the local listening port, check whether another client is running at the same time. If only one node times out, try another node without changing the mode. Once the connection stays up, make a new browser request.
Verify the Connection: Compare Requests, Routing, and Results
For your first check, ask two questions: Did the request reach the client, and where did the routing rules send it? Open the browser you checked earlier and visit a test site you can normally access. Make a new request rather than relying on an already-open tab or cached page. Note the domain and time, then check the client logs or runtime information for entries recorded after that request. Browsers often request icons, images, and other resources at the same time, so don’t mistake a nearby log entry for the homepage request if the domain is different.
If your client version and log settings show an outbound tag for each request, find the entry matching the test domain. direct usually means a direct-connection rule matched; proxy usually means the request was assigned to a proxy outbound. The exact meaning depends on the outbound names in your client configuration. A tag shows the routing decision, not whether the remote server returned a response. To verify traffic through a node, use a test destination that should go through the proxy under your current rules, confirm that the page loads, and check that the corresponding request has no connection errors.
If the default logs don’t show individual outbound requests, you can use a trusted IP lookup site as a secondary check. With the connection on and then off, make a new request to the same site in the same browser. This only works if your current rules are expected to route that site through the proxy. A changed IP can suggest that the route changed; the same IP alone doesn’t prove the connection failed. The site may be reached directly, both routes may use the same exit IP, or the lookup may have reused an old result. When troubleshooting, use visible request records and routing settings first to explain what you observe.
If the browser can’t open a page and there’s no matching log entry, first check whether the current log level records requests. Then check that your desktop browser uses the system proxy, or that the test browser isn’t excluded on Android. If the request appears in the logs but keeps timing out, try a known-working node in the same mode. Check DNS settings only if the logs explicitly report a domain resolution failure. Change one setting at a time and retry the same destination so you can identify what changed the result.
When you’re done testing, disconnect if you don’t plan to keep the connection on. On desktop, choose “Clear system proxy” from the tray menu before exiting the client. On Android, tap Connect again to stop the service. Then make a new browser request to confirm that regular network access is restored. If your desktop’s proxy settings were configured by your organization or set up manually, restore the previous settings rather than assuming that clearing the proxy is right for every setup.