Import a subscription
Copy the full subscription URL from your service’s website. A subscription URL fetches a list of servers; it is not the same as a share link for a single server. If the site offers multiple URLs, choose the subscription format recommended for your client. Include all query parameters when copying—don’t copy just the domain. Subscription URLs may contain account-specific parameters, so don’t post the full URL in public comments or screenshots when troubleshooting.
v2rayN: Add a subscription group and update it
Open the main window, click Subscription Group on the toolbar, then open Subscription Group Settings. Add a group, give it a name that identifies its source, enter the URL in the subscription address field, and save. Back in the main window, select the group, then choose Update Current Subscription from the Subscription Group menu. If your version only offers an option to update all subscriptions, confirm the group is saved before updating. Wait for servers to appear in the list, and check that they belong to the group you just added.
v2rayNG: Save the URL and fetch servers
Open the side menu on the main screen and go to Subscription Group Settings. Tap the add button, enter a label, paste the subscription URL, and tap Save. Return to the server list and choose Update Subscription from the top-right menu. If group tabs appear above the list, switch to the group you just added to check the results. Don’t import a subscription URL as a single-server share link. Save it as a group first, then update it from the subscription menu.
The list is still empty after updating
Check the selected group and search field first. The servers may already be imported but hidden because the wrong group is selected or an old search term is still applied. If the list is still empty after clearing filters, return to the group settings and check that the URL was copied in full and the subscription is still valid. If the update fails, restore the network connection that was working on your device and try again. If parsing fails, check the subscription format provided by your service. Continue once at least one selectable server appears. A successful update only means the list was retrieved; it doesn’t confirm that a server is usable.
Choose a proxy mode
First, understand the two separate settings. The system proxy or system VPN determines whether an app’s requests reach the client. Routing rules determine whether requests that reach the client go through a proxy server, connect directly, or follow another rule. Setting a route doesn’t mean every app will use the client. Likewise, enabling the system proxy doesn’t mean every request will go through a remote server.
v2rayN: Check routing and the system proxy separately
First, check the current route in the main window’s status bar or tray menu. If there’s a proxy preset such as Global, you can temporarily select it for your first test. This routes test requests covered by the preset through the proxy, reducing interference from direct-connection rules. Split-routing presets such as Bypass mainland China may send some requests directly according to their rules. If you test with a site that matches a direct-connection rule, an unchanged exit IP may be expected. If your version doesn’t offer a relevant preset, keep the current routing and make sure the test address should match a proxy rule.
After choosing a route, find the System Proxy setting. Note where it is; you’ll enable Automatically Configure System Proxy after selecting an active server. Use a browser that follows system proxy settings for your test. If a browser extension manages proxy settings separately, note its current state and temporarily disable it so it doesn’t override the system settings.
v2rayNG: Make sure the test browser is covered
From the main screen, open the menu, go to Settings, and check the routing options available in your version. If per-app proxying is enabled, check what the app list means: some configurations proxy only selected apps, while others bypass the proxy for selected apps. Make sure the test browser is set to use the client. For your first test, keep the app scope simple. Don’t change the per-app list, routing, and DNS at the same time, or it’ll be hard to tell which change affected traffic.
To tell whether the client isn’t covering the app or a rule is routing a request directly, note the current mode. After connecting, change just one setting and test the same address again. For help understanding the fields, see the routing and inbound sections of the V2Ray Configuration Guide.
Connect to a server
For your first connection, choose one server from a trusted subscription. Prefer an entry marked as available by your service and easy to identify in the list. Note its label and group to avoid selecting a similarly named entry by mistake. Don’t change the protocol, port, or transport settings yet. First test the configuration supplied by the subscription, then adjust based on the results. If you compare servers later, change just one at a time and keep the same test browser and routing mode.
v2rayN: Set an active server, then enable the system proxy
Select the server you want to use from the list. Open its context menu and choose Set as Active Server or the equivalent option in your version. Then check the active indicator or status bar to make sure the server changed. Highlighting a row alone may not set it as the active server. Once confirmed, choose Automatically Configure System Proxy from the status bar or tray menu. This changes the system proxy settings so apps that follow them send requests to the client.
If the interface reports that the core failed to start, check the logs for the earliest specific error. If a local port is already in use, check whether another client or process is listening on the same port. Don’t mistake a local listener failure for a remote server timeout. To troubleshoot, follow how to find a process using a local port, and update any apps where you manually entered a proxy address.
v2rayNG: Select a server and approve the system request
Tap the server you want in the list and make sure the selection indicator is on the right row. Tap Connect on the main screen. The first time a system VPN request appears, confirm that it was initiated by v2rayNG, then approve it. If you cancel the request, return to the client and tap Connect again. If another VPN connection is active on your device, check whether you can pause it. Don’t interrupt a connection you need for work just to run this test.
A change in the Connect button or a VPN icon on your device only means the local service started or established a traffic-capture entry point. Neither confirms that the remote server is reachable. Leave the client running and continue to verification. If it disconnects immediately after starting, check the logs for the startup failure instead of repeatedly updating the subscription and changing the evidence.
Verify the proxy connection
Compare results in the same browser before and after connecting. Before routing the browser through the proxy, open a trusted IP lookup page and confirm it shows the public IP seen by that request, not your device’s local address. If you’re already connected, briefly disconnect to record a baseline: in v2rayN, temporarily turn off the system proxy setting you enabled for this test; in v2rayNG, temporarily stop the connection. Don’t remove any proxy settings that were already in place on your device. Restore them after the test.
Reconnect as described in step three, then open the same lookup page. Check the result from a fresh request rather than relying on a value left in an old tab. If the test request should use the proxy and the exit IP differs from the baseline, that browser request is using a different exit. Then open a site you actually need and check that the page and its resources load properly. A single test only verifies the current browser and request; it doesn’t prove that other apps or all websites use the same exit.
The page loads, but the exit IP hasn’t changed
First, check whether the test address matches a direct-connection rule. With split routing, an unchanged exit IP for a direct connection is expected. If the request should use the proxy, check the system proxy setting and browser extensions on desktop, or whether per-app settings exclude the test browser on Android. Change one setting and try again. If the client provides access logs, use the test time and destination domain to find the request and check which outbound it used. The request may not appear in the logs if the relevant logging isn’t enabled. On some networks, direct and proxied traffic can also share the same public IP, so don’t assume the connection failed based on an unchanged IP alone.
The page times out, or only terminal requests fail
First, compare with the result when disconnected from the proxy. If the page won’t load either way, try another site that normally works or troubleshoot the device’s network first. If it only times out while connected, check the logs to see whether the issue is a remote connection timeout, a DNS resolution failure, or a local listener failure. Once the local entry point is working, try another server in the same group. If that works, focus on the original server or its configuration; there’s no need to reimport the entire subscription.
If the browser works but terminal requests fail, don’t switch routing modes right away. Many command-line tools don’t automatically use the desktop system proxy. Check the tool’s proxy options or environment variables as described in its documentation. Old environment variables may also point the terminal to a previously used port. First check the address, port, and protocol the client is actually listening on, then follow this guide to troubleshooting proxy issues in browsers and terminals to test each separately.
Restore your usual settings and test again
If you temporarily used a global proxy preset for testing, switch back to your usual routing mode afterward. Test one address expected to connect directly and another expected to use the proxy, and confirm the results match the rules. If you were only testing, restore the original system proxy settings in v2rayN before exiting the client. In v2rayNG, tap Connect to stop the service, then restore your previous connection. Next time you use the same subscription, just confirm the active server and routing settings—you won’t need to import it again.