First-Time Setup · Four Steps
v2rayNG & v2rayN Setup Guide
Go from a subscription URL to a verifiable connection. Get one connection working first, then adjust routing and advanced settings.
Step 01
Import and Update a Subscription
Get a subscription URL from your service provider. It’s not an account login page, and it may not open as a regular webpage in a browser. A subscription URL may contain account credentials, so paste it only into your own client—never share it in a group chat, online converter, or public screenshot. Haven’t installed a client yet? Visit the client downloads page, install it, then come back here.
v2rayNG: Add a Subscription Group and Update It
Open the menu in the upper-left corner of the main screen and go to Subscription Group Settings. Tap + in the upper-right corner. Enter a name you’ll recognize in the remarks field, paste the full subscription URL into the address field, then tap the check mark in the upper-right corner to save. Return to the main screen, switch to the group you just created, open the upper-right menu, and choose Update Subscription. If the menu offers an update for the current group or all groups, choose the current group. When the update finishes, its nodes should appear in the list.
If you have only a single-node share link, use Import from Clipboard under + in the upper-right corner of the main screen. This imports one configuration, not a subscription group that updates regularly. Once you can see the configuration in the current list, move on to the next step; there’s no need to look for an update subscription button.
v2rayN: Save the Subscription Group, Then Fetch Its Nodes
In the main window, open Subscription Group → Subscription Group Settings, click Add, enter a name and subscription URL, then save. Back in the main window, select the group and choose Update from the Subscription Group menu. For a first-time setup, if your current network can reach the subscription URL, try updating without using a proxy. When the update finishes, the group’s nodes should appear in the main window’s node list. If you can see the group name but no nodes, the URL is usually saved but the nodes haven’t been fetched successfully.
Subscription Updated, but the List Is Still Empty
First, check which group is selected, then clear any search or filter. If the app reports an update failure, check for extra spaces at either end of the URL, make sure it wasn’t truncated when copied, and confirm the subscription is valid with your provider. If the update succeeds but the current group is empty, switch to the all-groups list to see whether the nodes were added to another group. Still can’t find them? Ask your provider whether the response uses a subscription format the client supports. Don’t add the same URL repeatedly, or old and new groups can get mixed up. Set up traffic routing only after at least one selectable node appears in the list.
Step 02
Choose a Proxy Mode
A subscription provides nodes to choose from; a proxy mode determines how apps send requests to the client. These are separate settings. For your first setup, choose just one traffic entry point: VPN mode on Android or system proxy on desktop. Leave routing as it is for now—don’t change the mode, rules, and DNS all at once. That way, if something goes wrong in the next step, you’ll know which layer to check first.
v2rayNG: Route App Traffic Through VPN Mode
Open Settings from the menu in the upper-left corner and find the VPN mode options. If your version lets you choose a service mode, select VPN mode. For the first test, keep the default app scope and don’t add per-app rules. If Per-App Proxy is already enabled, pause it for now or make sure the browser you’ll test isn’t excluded. Return to the node list when you’re done. The system VPN request appears when you tap Connect in the next step.
If another VPN service is running on your device, check whether you can pause it first. On a personal device, you can end the existing connection and start v2rayNG if you’re allowed to do so. On a device managed by your workplace or school, follow its policies. Both apps showing an enabled service switch doesn’t mean they can route the same app traffic at the same time.
v2rayN: Start by Testing the System Proxy
Open System Proxy at the bottom of the main window and find Automatically Configure System Proxy. For your first setup, note the current setting; you’ll enable the proxy after setting an active server in the next step. If TUN is already on, turn it off while testing the system proxy. The system proxy is a good first test with browsers that follow system proxy settings. Some apps use their own proxy settings or ignore the system settings, so results may differ between your browser and other apps.
There’s no need to switch routing to Global here. The system proxy or VPN mode determines how requests enter the client; routing rules determine which outbound handles them. If a webpage opens in your browser but another app doesn’t use the same route, first check whether that app’s traffic reaches the client. Don’t assume the node is broken. Once the basic test passes, see the advanced guide to configure TUN, per-app routing, or custom rules as needed.
Step 03
Select a Node and Connect
Return to the subscription group you just updated and choose a node you can identify for your first test. Make sure you haven’t selected a similarly named node from an older group. If the list shows latency test results, use them as a guide, but remember they reflect only that one test at that time—not whether every app or destination will connect later.
v2rayNG: Connect and Approve the System Request
Select a node on the main screen. Once it’s marked as selected, tap the round connect button in the lower-right corner. When starting a VPN for the first time, the system will usually show a connection request. Make sure v2rayNG is the app requesting access, then tap OK. After granting access, check that the button shows the client is running. You can also pull down the notification shade and look for its running notification. A system VPN icon confirms that the local service is up, but doesn’t prove the remote node is reachable.
If you accidentally cancel the system request, return to the main screen and tap Connect again. If the button switches to running and then changes back, check the client message or logs. Follow any permission prompts; if you see a configuration parsing error, update the subscription again and select a compatible node. Once the client stays running, keep it in the foreground for the next test. Check your system battery settings only if it disconnects when sent to the background.
v2rayN: Set an Active Server, Then Enable the System Proxy
Select the configuration you want in the node list, right-click it, and choose Set as active server. Check that the active marker moves to that row. After confirming the change, choose Automatically Configure System Proxy from the System Proxy menu at the bottom. Desktop clients usually don’t show the same VPN authorization dialog as Android. For this step, check the active server marker, system proxy status, and main window logs.
If the logs show that a local port is already in use, check whether another instance of the client or a different local proxy is running. Don’t change the remote port just to test the connection. If the logs say the configuration couldn’t be loaded, return to the correct group and select a node again. If there are no recurring startup errors, keep the current configuration and test it. Switching nodes may interrupt existing requests, so test with a newly opened page rather than relying on whether an old page keeps playing.
Step 04
Verify the Connection
There are two things to verify: whether the request reached the client, and whether routing sent it through the expected outbound. A webpage loading only means that request received a response. If the matching rule calls for a direct connection, a working page doesn’t prove that proxy traffic is working. Likewise, a running client is only the starting point—not a substitute for testing an actual request.
Make a Request You Can Match to the Logs
Open a new tab in a browser that follows system proxy settings, or in an Android browser that isn’t excluded by per-app rules. Visit a site you know is currently reachable. To test proxy routing, choose a destination that should use the proxy under your current routing rules. If you’re unsure how a rule will match, check the currently selected route in the client before choosing a test destination. Note roughly when you make the request, and don’t open several test pages at once. Once the page loads, refresh it to avoid relying on previously cached content.
Return to the client and check the logs for the few seconds around your test. If the current log level records access and outbound details, find the matching entry by time and destination domain. Check whether it used a direct or proxied connection and whether any connection errors occurred. Some versions don’t show access logs for individual requests by default, so no log entry doesn’t necessarily mean no traffic. You can first use the client’s built-in connectivity test, then compare the same destination with the connection on and off. Even if the built-in test succeeds, verify the app you actually plan to use.
Connected but Can’t Open Pages? Narrow It Down by Symptom
If the client starts but a new browser request doesn’t show up in the access logs, first check whether your log settings record access. Then check the traffic entry point. On desktop, confirm Automatically Configure System Proxy is selected and that the browser isn’t overriding the system proxy with its own settings. On Android, make sure the system VPN is still running and that per-app rules haven’t excluded the test app. If the browser works but one app doesn’t, check how that app’s traffic reaches the client; there’s no need to import the subscription again.
If the request reaches the client but uses an unexpected outbound, review the current routing rules and their order. If it uses the right outbound but keeps timing out, try another node from the same subscription without changing the network or test destination. If the new node works, make a note of the original one. If several nodes fail, check that the device has a stable network connection, that its system clock is accurate, and that the logs don’t show a DNS resolution error. Adjust DNS only when the symptoms point to a DNS issue. Change one thing at a time and repeat the same test so you can tell what made a difference.
Restore Your Original Traffic Settings After Testing
Your basic setup is complete once the app you plan to use can make requests reliably and routing behaves as expected. To disconnect, tap the connect button in v2rayNG. Before exiting v2rayN, restore the System Proxy setting you noted before testing. If your device normally uses a different system proxy configuration, restoring the original setting is better than clearing it. Confirm that apps can still connect the usual way after disconnecting. Next time, you can start by selecting a node and connecting.
For more troubleshooting, see the connected but can’t open webpages checklist. If you’re not sure how outbounds, routing, and DNS differ, start with the glossary. To manage multiple subscriptions or fine-tune traffic rules, read the advanced configuration guide.