Quick startSubscription → Mode → Connect → Verify
v2rayN Setup Guide
Go from importing a subscription to verifying your connection. Use v2rayN on desktop and v2rayNG on Android. For your first setup, choose one node and one test app—there’s no need to write a config file by hand.
Import a subscription
Start with a subscription URL from a source you trust. It gives the client access to a list of nodes; it’s not a provider’s login page or a link for sharing a single node. Copy the entire URL, including any parameters after the question mark. Don’t post it in forums or include it in troubleshooting screenshots. Add just one subscription for your first setup so it’s clear which group the update belongs to.
v2rayN for desktop: Add a group and update it
Open the main window and select Subscription Groups at the top, then open Subscription Group Settings. Add a group, paste the URL into the Optional URL or Subscription URL field, and enter a recognizable remark. Save, return to the main window, and select the group you just added. From the Subscription Groups menu, choose Update Current Subscription. If the only option is to update all subscriptions, select your group again afterward and check the results.
A remark in the group list only confirms that the URL was saved. The import is complete when the list shows node names and protocol types. If the update reports success but the list is empty, make sure you’re viewing the right group and haven’t left a search filter in place. If the update reports an error, check that you copied the full URL and that your current network can reach its source. Follow the error message to determine whether you need a new URL. Avoid repeatedly creating groups with the same name—it makes it harder to tell which one updated successfully.
v2rayNG for Android: Add a URL and refresh the list
Tap the menu in the upper-left corner of the main screen and open Subscription Group Settings. Tap the plus button to add a group, enter a remark and URL, then save. Return to the configuration list and choose Update Subscription from the more menu in the upper-right corner. When the refresh finishes, open the group you just created to check its entries. Adding a subscription and updating it are separate actions; saving the URL alone won’t make nodes appear in the list.
If you have a link for a single node, use the plus menu on the main screen to import a configuration from the clipboard. Don’t paste it into the subscription URL field. Individual node entries aren’t updated when you refresh subscriptions. Either way, make sure at least one entry is available to select before deciding which apps should use the client.
Choose a proxy mode
Keep two settings separate: system proxy or TUN determines which requests enter the client; routing rules determine which outbound handles them. Even with global proxy routing selected, apps not captured by the client won’t use the proxy automatically. For your first test, choose one app and one traffic-capture method, and leave your routing rules unchanged. This makes it easier to tell whether a failed test means the request never reached the client or reached it but went direct or hit a connection error.
System proxy on desktop: Start with one browser
Find System Proxy at the bottom of the v2rayN main window or in the tray menu. Look for options such as Set System Proxy and Clear System Proxy, and enable the former when you connect. Start with a browser that follows system proxy settings. If it has a proxy extension, make sure the extension isn’t overriding those settings. Enabling this mode won’t route traffic from desktop apps that have their own proxy settings or ignore the system proxy.
TUN on desktop: Capture traffic from apps that ignore the system proxy
If an app ignores the system proxy and you need its traffic routed through the client, consider enabling TUN in the main window. TUN routes traffic through a virtual network adapter and system routes, and may require system permission to start. Before switching modes for the first time, quit or pause other tools that change system routes. Don’t change TUN, system proxy, and routing rules all at once while troubleshooting. If TUN shuts down soon after you enable it, check the startup logs for permission errors or virtual adapter initialization failures.
VPN service on Android: Make sure the test app is included
v2rayNG captures traffic through Android’s VPN service, so you don’t need to enter a proxy address in the system network settings. If per-app proxying is enabled, check whether the selected list is an allowlist or a blocklist, then make sure the browser you’re testing isn’t excluded. If you haven’t changed the per-app settings, use the default scope for your first connection. For details on domain rules and default outbounds, see the outbounds section of the configuration reference; you don’t need to edit these fields to connect for the first time.
Connect to a node
Return to the subscription group and choose a node with a clear remark that’s currently available. Don’t assume a row is active just because it’s highlighted: confirm the active server in the desktop client or the selected configuration in the Android client. Test with one node at a time. If you switch nodes, check the status again and make a new request. Don’t use a page opened before the switch to judge whether the new connection works.
v2rayN for desktop: Set the active server and enable traffic routing
Right-click the node you want in the list and choose Set as Active Server or the equivalent menu item. Confirm the status area shows that node. The client usually applies the selected configuration; if the runtime log reports a startup failure, read the first relevant error instead of repeatedly toggling the system proxy. Once the client is running, set the system proxy or enable TUN and approve any system prompt, according to your choice in the previous step. Then check that the setting is still enabled.
If the system proxy is enabled but an app immediately reports a connection failure, check that v2rayN is still running and look for local port conflicts in the logs. Setting the active server, starting the core, and configuring the system proxy are separate actions. Changing system settings alone won’t establish a connection if the core isn’t listening. If the error persists, search the FAQ for the error message or a relevant keyword.
v2rayNG for Android: Select a node and approve the system prompt
Tap a node in the group and confirm it’s selected, then tap Connect on the main screen. The first time you connect, Android will show a VPN connection request. Make sure it comes from the client you’re using, then approve it as prompted. If another VPN service is already running, disconnect it before starting v2rayNG. After connection, the client updates its button or status, and Android usually displays a VPN indicator. This only confirms that the traffic-capture service started; it doesn’t prove the remote node or test app is working. Make an actual request in the next step.
Verify that it works
Open the browser you chose earlier and visit a known working site that should use the proxy under your current routing rules. Refresh the page manually to make a new request. Then open the client’s runtime logs and check the request time. If the logs show routing or outbound details, confirm that the connection used a proxy outbound rather than a direct outbound. A page loading successfully only shows that the site was reachable; if the request went direct, it doesn’t confirm that the proxy is working.
If the request doesn’t appear in the logs, first check that the browser follows system proxy settings or, on Android, isn’t excluded by per-app settings. Also make sure the log level isn’t filtering out relevant entries. If the request appears but goes direct, check whether the target domain matches a direct-routing rule. If the logs show a proxy outbound but requests repeatedly time out or fail during the handshake, keep the same traffic-capture method and test target, and try another node from the same subscription. Change one thing at a time to identify whether the difference comes from the node or a local setting.
Node latency tests: Understand what they measure
To compare candidate nodes, look for a latency test in the desktop node list’s right-click menu or the more menu on the Android main screen. If a Real Connection Latency test or similar option is available, use the same test method for each node. The result measures the time taken to reach that test target at that moment; it’s not download bandwidth and doesn’t reflect connection quality for every app. A timeout could also mean the test target is unreachable. Consider the app request and logs from the previous steps, rather than changing routing based on a single latency value.
Restore your traffic-capture settings after testing
If you enabled the system proxy on desktop, clear the proxy settings set by the client before quitting. If you had manual or organization-managed proxy settings before, restore them. If you enabled TUN, turn it off and make sure your usual apps are back to their expected network behavior. On Android, tap the Connect button to stop the service and confirm that the system VPN indicator disappears. Your first setup should now tell you which node connects, which app is being routed, and which outbound handled the test request. If problems remain, note the platform, traffic-capture method, time of the error, and a short log excerpt, then check the FAQ. Don’t include subscription URLs or node credentials.