V2Ray Setup Guide
Use one subscription, one node, and one test page to complete your initial setup: import the subscription, choose a proxy mode, connect to a node, and verify where your traffic goes. Before you begin, make sure the client is installed, you have a valid subscription URL, and your device can access the internet. If you haven't installed a client yet, choose a package for your device on the client download page.
01 Prepare a node
Import a subscription and update the node list
First, make sure you have a subscription URL—not an account sign-in page or a single-node share link starting with vless:// or vmess://. A subscription URL lets the client fetch a group of configurations. Import a single-node link from the client's clipboard import option instead; you don't need to create a subscription group for it. When copying the URL, keep the full path and any parameters after the question mark, and remove accidental spaces or line breaks. Subscription URLs may contain access credentials, so don't include them in public screenshots.
v2rayN: Add a subscription group
Open the Subscription Group menu in the main window and select Subscription Group Settings, then add a group. Enter a recognizable name in the remarks field and paste the subscription URL into the address field. Save, then return to the main window. Select the new group and choose Update current subscription from the Subscription Group menu. The node connection isn't set up yet. If your current network can reach the subscription URL, choose an update option that doesn't use the proxy. This avoids relying on a proxy that isn't running yet to fetch your nodes.
v2rayNG: Save the URL and update manually
Open the side menu from the main screen, go to Subscription Group Settings, and tap the plus icon in the top-right corner. Enter a remark and the subscription URL, then tap the checkmark in the top-right to save. Return to the configuration list, switch to the group you added, and open the more menu in the top-right. Select Update subscription. Seeing the group name only confirms that the URL was saved; nodes must appear in the group for the update to have retrieved usable configurations.
If the list is still empty after the update, first check which group is selected, then review the update message. For a request timeout, try loading a regular webpage on the same network to rule out a device connection issue. If the message says access is unauthorized, check with your subscription provider that the URL is still valid. For a format error, make sure you haven't entered a webpage URL or a single-node link by mistake. Don't create duplicate groups. If the cause is still unclear, follow the subscription update troubleshooting guide. Once nodes appear, move on to the next step; there's no need to change server settings yet.
02 Choose a traffic path
Choose a proxy connection method and routing mode
These are two separate settings: the connection method determines whether an app's requests can reach the client; the routing mode determines whether requests that reach the core go through the proxy, connect directly, or get blocked. Setting a system proxy doesn't mean every app will use it. Choosing global proxy routing won't redirect traffic that never reached the core in the first place. For the first test, route one app's requests through the client and send one test destination through the proxy.
v2rayN: Start with the system proxy; leave TUN off
Find System Proxy in the status bar at the bottom of the main window or in the tray menu. Note where Set system proxy automatically is, but wait until you've selected a node before enabling it. Keep TUN off for now, and choose a browser that uses the system proxy settings for your test. If a browser extension or the app itself specifies another proxy, disable that setting temporarily. Otherwise, even if the status bar shows that the system proxy is enabled, the browser may be using a different route.
v2rayNG: Start in VPN mode; include all apps
Open Settings from the side menu. If your version has a Running mode option, choose VPN mode for the first test. If VPN mode is already the default, leave it as is. Keep per-app proxying off so the test browser isn't excluded. If another VPN is running on your device, confirm you can switch before disconnecting it. When you connect, check which app the system actually authorizes; the VPN icon alone doesn't tell you which client is running.
Next, check routing. In v2rayN, use the routing selector in the bottom status bar to see the active rule set. In v2rayNG, check the routing options in Settings. If the client offers global proxy routing, you can select it temporarily for comparison. If you keep the split-routing rules, choose a test site that those rules should send through the proxy. A site matched by a direct-connection rule may show the same exit as before, even when the system proxy is enabled. For the first test, don't change routing, DNS, and node settings all at once. Verify the connection method and node first, then adjust your everyday routing with the beginner-to-advanced guide.
03 Start the service
Connect to a node and confirm the service is running
Choose a node from the subscription group and note its remark so you can compare it with the active configuration. If you run a latency test first, use the result as a guide when choosing a node—but a successful test only means that probe received a response; it doesn't confirm access from an app. A node appearing in the list, or a row highlighting when tapped, also doesn't mean the proxy service is running.
v2rayN: Set the active server, then enable the system proxy
Right-click the selected node and choose Set as active server, or the equivalent option. Check the active configuration shown in the main window to confirm it matches the node you chose, then look in the logs for core startup or listener errors. If the core starts without errors, select Set system proxy automatically from the status bar or tray menu. Keep the default listener settings for now; don't change the port at the same time. If the logs report that the port is already in use, follow the local port conflict troubleshooting guide to identify the process using it, then restart the client and check that the error is gone.
v2rayNG: Select a configuration, then connect
Return to the node list on the main screen, select the configuration you want, and check that it's marked as selected. Then tap the Connect button at the bottom. The first time you start the VPN, the system will ask for permission to connect; check the app name and approve. Wait for the button to change to a stop control, then confirm that the system shows the VPN as active. If the button quickly returns to its disconnected state, reopen the client logs and check the startup error. If you previously denied system permission, tap Connect again and approve the request.
Once the connection stays up and the logs show no startup errors, continue to the next step. This confirms that the local service is running, not that the remote node is necessarily reachable. Don't change the server address, port, and transport settings from the subscription just to fix one timeout. Retry the test in the next step first. If only this node fails, switch to another node in the same group to compare one variable at a time.
04 Check the actual outbound route
Check that the proxy is working
Compare the same page before and after connecting
Choose a trusted HTTPS IP-check page that should go through the proxy based on the routing mode you selected in the previous step. If you didn't record the result before connecting, temporarily undo the system proxy changes you made for this test, or tap Stop in v2rayNG, and make sure no other proxy is handling the request. Open the page in your test browser and note the public IP address it shows. Then reconnect as described in the previous step and make a new request in the same browser on the same network. Don't switch between Wi-Fi and mobile data during the test or rely on an old page from the previous check.
If the expected proxy exit appears after connecting, the browser request is using the proxy as intended. Next, test the app you actually plan to use. A working browser test doesn't guarantee that other apps will work: desktop apps may ignore the system proxy, and Android apps may be excluded when per-app proxying is enabled. If you only plan to proxy some sites, also test a destination that should connect directly. This helps confirm that you haven't mistaken access to every destination for a successful proxy connection.
If the exit IP is unchanged or requests time out, use the logs to narrow it down
Watch the client logs while reloading the test page. If the current log shows request details and the test destination uses a direct outbound, go back to step two and check the routing rules. If the destination uses the proxy outbound but times out, try another node in the same group first. If the logs show startup messages only, the absence of request entries doesn't prove that the app failed to reach the client. Check whether the browser follows the system proxy, or whether v2rayNG established the Android VPN, then review the per-app settings. If two nodes both report a domain resolution error, note the domain and time, then follow the DNS troubleshooting steps in FAQ.
After a successful test, switch back to your usual split-routing setup if you temporarily enabled global proxy routing, then test one destination that should use the proxy and one that should connect directly. When you're done, restore the system proxy settings managed by v2rayN to their previous state, or tap Stop in v2rayNG. If something goes wrong later, note where the problem starts: an empty list points to the subscription, startup failures to the logs, and a working connection with misrouted traffic to the connection method or routing settings. If you come across an unfamiliar rule name, check the glossary instead of redoing the whole setup.