First-time setupAbout 10 minutes
v2rayN / v2rayNG Subscription and Proxy Guide
First, get the servers from your subscription to appear in the list. Then send a browser request through the expected outbound route. You can check the result of each step in the client.
Before you begin, have a valid subscription URL ready and make sure the client opens normally. Not installed yet? Choose a client from the Download Center.
01 · Subscription
Import and Update a Subscription
First, identify what you have. Providers usually label a URL starting with https:// as a subscription URL; the client uses it to fetch a list of servers. A link starting with vmess:// or vless:// is a single-server share link. Import it from the main screen using an option such as “Import from clipboard” instead of entering it in the subscription URL field. The steps below use a URL subscription. Copy only the URL itself—no quotation marks, line breaks, or extra text. Any parameters at the end are part of the URL.
v2rayN for Desktop: Add a Group, Then Update
Open “Subscription Group” in the top menu, then select “Subscription Group Settings” and click “Add.” Enter a name that identifies the source, paste the subscription URL, and save. Return to the main window, open “Subscription Group” again, and choose the option shown in your version to update the current subscription or all subscriptions. For initial setup, if the subscription site is directly reachable, you can choose an update option that does not use the proxy. When the update finishes, select the group you created and check the server list. Seeing the group name only confirms that the URL was saved; servers in the list confirm that configuration was fetched.
v2rayNG for Android: Add a Subscription from the Navigation Drawer
Open the menu in the upper-left corner of the main screen and select “Subscription Group Settings.” Tap the plus sign in the upper-right corner, enter a remark and the subscription URL, then tap the checkmark to save. Return to the configuration list, open the menu in the upper-right corner, and select “Update subscription” or the equivalent option. When the update finishes, open the relevant group and check its entries. If the list already contains other servers, confirm the group name so you don't mistake older entries for the newly fetched ones.
If an update fails, check whether the URL could not be reached or the content was fetched but could not be parsed. For a connection failure, check that you copied the full URL, that it is still valid, and that your current network can reach it. If parsing fails, ask the provider to confirm that the content is in a format supported by your client, not a web login page. Don't post your subscription URL in public chats or screenshots when troubleshooting. Once servers appear in the list, decide which apps should send traffic through the local proxy.
02 · Mode
Choose a Proxy Mode and Routing
Two client settings are easy to confuse: traffic capture determines which apps hand their traffic to the client, while routing rules determine whether captured traffic uses the proxy, connects directly, or goes through another outbound route. Setting the route to “Global” won't make an app that ignores the system proxy use the proxy automatically. Conversely, even after traffic enters the client, routing rules can send some of it directly to its destination.
v2rayN for Desktop: Start with the System Proxy
Find “System Proxy” in the tray menu and check for an option such as “Set system proxy automatically.” Enable it after selecting a server in the next step. This is a good starting point for testing with a browser that follows the system proxy settings by default. If your browser has an extension that manages proxies separately, make sure it is set to use the system settings, or use a browser without such an extension. Leave TUN off for the first test to avoid changing both the system proxy and network routing at once; otherwise, it can be hard to tell which layer caused a problem.
v2rayNG for Android: Make Sure the Browser Is Included
On Android, the usual connection method uses the system VPN interface, so there is no need to copy the desktop tray settings. If per-app proxying is enabled in the client, check that your test browser isn't excluded or missing from an allowlist of apps. If another app is already providing a VPN connection, check whether you can switch connections. On a managed device, don't disable a connection required for work.
On either platform, decide what you want to test before choosing a route. If the client offers “Global” routing, you can use it temporarily for a single initial test to reduce the number of variables. If you keep your existing routing rules, choose a test destination that should use the proxy under those rules and note the expected result. Routing menus and preset names vary between versions; if you can't find an exact match, don't rush to edit configuration files. For details on system proxy settings, global routing, and when to use TUN, see the Help Center.
03 · Connect
Select a Server and Connect
Return to the group you just updated and select a server you recognize and expect to work. Change only one variable at this point: the server. Don't switch servers while enabling TUN or changing routing rules. Otherwise, even if you find a working combination, you won't know which layer caused the problem. If the client supports server testing, save that comparison for after a real-world test fails; there's no need to test the entire group first.
v2rayN for Desktop: Set the Active Server, Then Enable the System Proxy
Select the server you want in the list, open the right-click menu, and choose “Set as active server” or the equivalent option. Make sure the active marker or status area shows the server you selected; a highlight on the row alone may only indicate where the cursor is. Next, open “System Proxy” from the tray and select the automatic configuration option you found in the previous step. Return to the main window and check the log for a core startup failure or a message that the local listening port is already in use.
v2rayNG for Android: Tap Start and Approve the VPN Request
Select your chosen entry in the configuration list and make sure the selection marker is on the right server, then tap Start on the main screen. The first time you connect, Android may show a VPN connection request. Confirm that it comes from the client you just opened, then approve it. Return to the client and check that the button changes to a stop option. Some devices also show a VPN icon in the status bar, but that only confirms that Android has established the traffic capture interface; it doesn't mean the remote server is forwarding traffic successfully.
If the client stops immediately after startup, address the first clear error it reports instead of repeatedly trying to connect. For example, if the desktop client reports that a port is in use, check whether another instance of the same client is running or another proxy app is listening on that port. If you dismissed the Android permission request, tap Start again, read the prompt, then decide whether to approve it. If there are no immediate startup errors, move on and test with a real request.
04 · Verify
Verify the Proxy with a Real Request
Using the browser you checked in the previous step, open a test page that should use the proxy under your current routing rules and that normally loads for you. Try a new private browsing window to avoid mistaking an already loaded page for a successful test. Make sure the window isn't using an extension that manages proxy settings separately. Note the destination domain and the time you visited it, then check the client logs. During the test, visit only the pages you need so background requests don't clutter the results.
Match the Page Result to the Logs
If logs are available, find the entry for the destination at the time you noted and check whether it used the expected outbound route. The test is successful only if the page loads and the matching request appears in the logs. If the logs show a direct connection, an open webpage doesn't count as a successful proxy test; first check whether the destination matched a direct-connection rule. If there is no log entry, don't assume the server is faulty: access logging may be disabled, or the browser may not be using the traffic capture method.
To compare results, temporarily clear the system proxy set by the desktop client, or tap Stop in the Android client, then retry the same URL in the same browser and restore your test settings afterward. If available, compare the results using a trusted public IP lookup page. The visible IP can be the same in both cases without indicating a failure—for example, the proxy and your device may share an exit IP. Server latency tests and system icons are only clues; matching the outbound route for the actual request is more conclusive.
After the Browser Test, Check the Apps You Actually Use
If the browser passes but a terminal or another app still bypasses the proxy, check whether that program reads the system proxy settings, has its own proxy settings, or is excluded from traffic capture. Conversely, if the logs show that a request used the proxy but it repeatedly times out, keep the routing rules and test URL unchanged and try another server from the subscription. Troubleshoot these cases separately: the first is about whether traffic reaches the client; the second is about whether the client can forward it.
If you temporarily changed routing rules for the test, restore your usual split-routing setup afterward and verify it again using the same method. To disconnect, first clear the system proxy set by the desktop client, then exit; on Android, tap Stop in the client. For device-specific setup, permissions, TUN, or routing details, see the All-Platform Guide. If the result doesn't match what you expect at a particular step, check the Help Center for that symptom.