First Connection · 4-Step Setup
v2rayN and v2rayNG Setup Guide
From subscription URL to browser test, start by routing one app as expected. Allow about 10 minutes for the initial setup once you have the client and subscription URL ready.
01 Import
Import and Update a Subscription
First, make sure you have a subscription URL from a trusted source—not a provider’s login page or a single share link beginning with vmess:// or vless://. Subscription URLs usually start with https:// and fetch a set of configurations when updated. Import a single share link from the client’s “Import from clipboard” option; it adds just one configuration. Copy the entire subscription URL, including any parameters after the question mark. Subscription URLs may contain access credentials, so don’t paste the original URL into public posts or screenshots when troubleshooting.
v2rayN Desktop: Add a Subscription Group
Open the main window, find “Subscription group” in the top menu, then choose “Subscription group settings” and click Add. Enter a recognizable name for the group, paste the URL into the optional URL or subscription address field, save, and return to the main window. You may see only a new group at this point—that’s expected. Saving the URL and fetching nodes are separate steps. Select the group you just created, open the “Subscription group” menu, and update the current subscription. If the client offers an option to update without using the proxy and you don’t yet have a working proxy connection, you can use it.
v2rayNG for Android: Save, Then Update from the List
Open the menu in the upper-left corner, go to “Subscription group settings,” tap Add, enter a name and URL, then save. Return to the main screen and choose “Update subscription” from the upper-right menu. If you can filter by group, switch to the one you just created. Once the update finishes, find the nodes from your provider in the list; don’t mistake previously imported entries for the latest results. For your first setup, note the name of an easy-to-identify node so you can confirm you’re testing with the same one as you adjust settings.
If the update reports success but no nodes appear, switch to All groups first to check whether a filter is hiding them. If the update failed, check that the URL was copied in full, your regular internet connection works, and the subscription is still valid. If the client says the content can’t be parsed, check that the subscription format provided by the source is compatible with the client. Don’t change the system proxy yet: proxy settings can’t fix an invalid URL. Wait until nodes appear in the intended group before deciding which apps to route through the client.
02 Mode
Choose a Proxy Mode and Apps
Keep two questions separate when configuring the client: will an app’s requests reach the client, and, once there, will they go direct, through a proxy, or be blocked? The system proxy on desktop and per-app proxy settings on Android mainly determine the first; the client’s routing rules determine the second. Enabling the system proxy does not guarantee that every request will use the selected node. To keep your first test simple, choose a browser you normally use and leave the client’s default routing rules unchanged.
v2rayN Desktop: Start with the System Proxy
Find the v2rayN icon in the system tray and open its menu. Make sure you can see “System proxy” and “Set system proxy automatically.” You’ll enable them in the next step; for now, note the system’s current proxy settings. If a manual proxy or auto-config script is already set, record the original settings so you can restore them later. For your first test, don’t enable TUN or enter a local proxy port in the browser. Use a browser that normally follows the system proxy. If the browser or an extension has its own proxy settings, make sure they won’t override the system settings for this test. On a managed work device, leave network settings as required by your organization.
v2rayNG for Android: Check Which Apps Are Included
A standard connection through the graphical interface uses Android’s VPN service to route traffic from the apps in scope. Open Settings in the sidebar and find “Per-app proxy.” If it’s off, you can leave it that way for your first test. If it’s already on, check whether it proxies only selected apps or bypasses selected apps. In the first mode, add your browser to the list; in the second, make sure the browser isn’t excluded. Then return to the node list. If another app is already using the VPN service, check whether it can be paused before proceeding. Don’t replace it without knowing what it does.
Don’t assume the system proxy means all traffic is routed through the proxy, and don’t switch to global routing just to make a test page load. For the initial setup, confirm that the test browser reaches the client and that its requests are handled as expected. To learn about rule order and how the default outbound relates to outboundTag, see the configuration reference after your first test. For now, return to the group you updated, select a node, and connect.
03 Connect
Connect to the Selected Node
Choose one node from the subscription group you just updated to test. Use only one to start; changing routing, ports, and nodes at the same time makes it hard to pinpoint a problem. Latency tests can help you compare nodes, but a check mark, a latency reading, or a “selected” label doesn’t replace testing in a browser. First make sure the client starts normally, then check the browser’s requests.
v2rayN Desktop: Set the Active Server, Then Enable the System Proxy
In the main window’s node list, right-click the selected node and choose “Set as active server” or the equivalent option. Make sure the active indicator appears on that row. Check the runtime log for errors such as a failed core startup, unreadable configuration, or a port already in use. The active server is the node the client will try to use; it doesn’t ensure that the browser is sending traffic to the client. Once the core starts normally, open “System proxy” in the tray menu and choose “Set system proxy automatically.” Check that the menu reflects the new selection.
If the log reports that a port is already in use, check whether you started the client more than once or whether another known network tool is using the same port. You can close a duplicate instance you recognize, then return to the main window and activate the node again. Don’t change the port at random. If the interface marks the node as active but the log continues to show that the core failed to start, troubleshoot the reported error first rather than repeatedly toggling the system proxy. That would only send app requests to a local service that may not be listening.
v2rayNG for Android: Start the VPN Service
Return to the main screen, tap the node you noted earlier, and make sure the selection indicator is on the right one. Then tap Connect in the lower-right corner. The first time you connect, Android will usually show a VPN connection request. Allow it only after confirming it came from the client you just opened. Then check that the Connect button changes to a stop control and that Android shows the VPN is active. If you denied the request, the client can’t establish this VPN session. Return to the main screen and connect again; tapping the node again won’t grant the system permission.
A change in the Connect button’s state only means the local service has started; it doesn’t guarantee the remote node is reachable. If the service stops immediately, check the client’s current log or error notification and note the type of error. The same approach applies on desktop and Android: keep the selected node and proxy mode unchanged, then use the same browser for the next test. Changing nodes is useful only after you have a result to compare.
04 Verify
Verify the Proxy Connection
Send a New Request You Can Match in the Logs
In the browser you confirmed is within the proxy scope, open a familiar test page you’re allowed to access. Don’t rely on a tab that was already open; it may be showing cached content. Open a private window if you like, enter the address again, and note roughly when you sent the request. Then check the client logs for activity at the same time. If your client version and logging settings record requests, look for the matching destination domain and outbound tag. A page loading only confirms that the browser received content; seeing the request use the expected outbound is the result you’re checking for.
If the log shows direct, that may be exactly what the current rules require. If it shows proxy, confirm that it’s the proxy outbound used by your configuration rather than relying on the label alone. If you understand how the lookup service works, you can also compare the address shown by the same exit-IP lookup site before and after connecting. Keep in mind that the lookup site is subject to routing rules too: an unchanged address doesn’t prove all traffic bypassed the proxy, and a changed address doesn’t prove every app follows the same route. If the logs don’t record request details, don’t treat a missing entry as proof of a direct connection.
Troubleshoot Based on What You See
If the page loads but you can’t tell whether the browser’s request reached the client, revisit proxy mode and app scope. On desktop, check the system proxy status in the tray and the browser’s own settings; on Android, check the per-app list. If the log shows the browser request but the outbound isn’t what you expected, check whether the test destination matches an existing direct rule before changing nodes. If the request reaches the proxy outbound but repeatedly times out, keep the browser, URL, and routing rules unchanged, and compare with another node from the same subscription. If startup errors occur with both nodes, return to connecting to a node and check the local service.
Finish Testing and Restore Your Settings
Your first test is complete when you can match a new browser request to the result shown in the client. If this was a temporary test, restore the previous proxy settings in v2rayN. Choose “Clear system proxy” from the tray only if no proxy was configured beforehand. Make sure apps no longer point to the local port used for this test, then exit the client. In v2rayNG, return to the main screen, tap Stop, and confirm that the VPN session has ended. You can keep the existing groups and nodes for next time. To refresh the node list, go to import and update a subscription; there’s no need to add the URL again each time.