V2Ray Setup Guide
Once you have a client and subscription URL, follow the steps in order: import, choose a mode, connect, and test. Start with one app; adjust routing only after it works.
Step 1: Import a subscription
Get a subscription URL from your service provider. This is usually a link that updates your server list, not the provider's login page or a share link for a single server. If you only have a single-server share link, use the client's server import option instead of entering it as a subscription URL. Haven't installed a client yet? Visit Get a client to choose an installer for your device, then continue from the main screen.
v2rayN: Save a group, then update the list
In the main window, click Subscription Group at the top, then open Subscription Group Settings and choose to add a group. Enter an easy-to-recognize name, paste the full URL into Optional Address or the subscription URL field in your version, make sure updates are enabled, and save. Seeing the group name in the main window only confirms that the URL was saved. The server list may still be empty, which doesn't necessarily mean the import failed.
Select the group you just created, open Subscription Group, and choose Update Subscription for that group. If the menu offers updates with or without a proxy, choose the no-proxy option for your first setup, before connecting. Wait for the update to finish, then check the current list for server entries. Don't just check for old servers under All: the new entries must appear in the group you saved.
v2rayNG: Update a saved group from the menu
Open the main menu, go to Subscription group settings, tap Add, enter a name and subscription URL, then save and return to the server list. Open the overflow menu in the top-right corner of the main screen and choose Update subscription or the equivalent group update command. When the update finishes, select the group you just added and check its entries. If a search term or group filter is still active, clear it first and make sure you're viewing the new group.
If the update fails, check the client's message, then open the group settings and make sure the URL is complete. Check for a trailing space or a missing parameter after the question mark. If the error mentions authorization or an invalid response format, confirm with your provider that the URL is still valid and the subscription format is supported by the client. Don't post the full URL in a public support ticket or screenshot; its parameters may be tied to your account. Once the group has server entries, continue to the next step. You don't need to test every server first.
Step 2: Choose a proxy mode
Choose the app you'll use to test the connection. On desktop, start with a browser that uses the system proxy settings. On Android, use your usual browser. Proxy mode determines how app traffic enters the client; routing rules determine where requests go after they enter. These are separate settings: the connection can work even if an app ignores the system proxy or a domain is set to bypass the proxy.
Desktop: Start with the system proxy; leave TUN off
At the bottom of the v2rayN main window, find System Proxy and TUN Mode. For your first test, leave TUN off. When you connect, set System Proxy to Automatically configure system proxy. If you previously configured a proxy manually, note the existing settings before making changes. Don't overwrite settings if you're unsure what they're for; follow your administrator's instructions on a managed device. Keep your existing routing rules for the first test. Changing the system proxy, rules, and DNS at the same time makes it hard to identify the cause of a problem.
The system proxy works for apps that use the operating system's network settings; it doesn't route all traffic from your computer through the client. If your browser has its own proxy settings, make sure it's set to use the system proxy. To route apps that don't use it, see TUN mode setup. Don't enable both routing methods for this test, and you don't need elevated permissions just to test a browser.
Android: Start with a standard VPN connection
In v2rayNG, start a standard VPN connection using the button on the main screen. You'll handle the first-time permission prompt in the next step. If you've enabled per-app proxying in Settings, make sure your test browser isn't excluded. If you're unsure whether the app list is set to include or exclude apps, turn per-app proxying off for now and restore it after the test works. Also check that another VPN isn't already using the connection. If you need to keep a work VPN connected, don't disconnect it just to run this test.
Step 3: Select a server and connect
Return to the group you just updated and choose a server your provider marks as available and that suits your current network. A highlighted row only means the server is selected; it doesn't necessarily mean the active connection has switched to it. Check the active configuration, not just the highlighted row. There's no need to test every server—start by getting one connection through the full setup.
v2rayN: Set the active server
Right-click the server you want and choose Set as active server. Then open System Proxy at the bottom and select Automatically configure system proxy. Check that the active server and status bar in the main window match your selection. If you're unsure whether the new configuration has loaded, check the logs for a new startup message. If they clearly show a startup failure, read the error instead of repeatedly clicking Restart service.
If the logs say a local port is already in use, check whether the client is open more than once or another proxy app is running. Only close programs you're sure you can stop, then try again. If the configuration won't load, return to the original group and make sure you've selected an entry from the group you just updated. If another entry in the same group starts successfully but this one consistently reports a configuration error, ask your provider to check that server entry. There's no need to change routing or DNS for the whole group first.
v2rayNG: Select a server and approve the connection
Tap the server you want in the list and make sure the selection indicator moves to that row. Then tap Start at the bottom of the main screen. The first time you use the VPN connection, Android displays a system prompt. Make sure it's from the client you just opened, approve it, then return to the main screen and wait for the button to show that it's running. A VPN icon in the status bar means Android has established the VPN connection, but it doesn't prove that the remote server is reachable.
If the client stops right after you start it, check whether you dismissed the system prompt, another VPN is active, or an error appeared. Stay on the same network during the test. Don't switch between Wi-Fi and mobile data while connecting; otherwise, a network change could cause the error in the logs. Once the client is running, open the app you want to test.
Step 4: Test your connection
Test two things separately: whether the client can send a request through the selected server, and whether the app's traffic follows the expected route. First, check whether the client is still reporting errors. On desktop, if the menu offers Test real connection latency, run it once for the selected server. A successful test only shows that the client's own test request completed; it doesn't mean your browser is using the system proxy. A failed test could also be caused by the test address or your current network, so test an app as well.
In the browser you chose earlier, open a page that should be routed through the proxy under your current rules and that you're authorized to access. Make a new request. Don't count a tab that was open before you connected; it may be showing cached content. If you use an IP lookup site to check your exit address, first make sure its domain matches a proxy rule. If the rules send it direct, an unchanged address is expected. If the client provides request logs, check them at the time of your test to see whether the request appears and whether it used a direct or proxy outbound. Simply checking whether the page loads won't tell you which route it took.
Use the results to choose what to check next
| What you see | Check first | Next step |
|---|---|---|
| Both the client test and browser request fail | Basic network access, active server, and startup logs | Stay on the same network, switch to one other server, and repeat the same request. |
| The client test succeeds, but the browser doesn't use the proxy as expected | System proxy settings on desktop or per-app proxy settings on Android | Confirm browser traffic reaches the client, then check which routing rule matches the domain. |
| Only some domains fail | DNS resolution and outbound rules for the failing domains | Keep the working configuration and troubleshoot only the domains that fail. |
If switching servers fixes the same request, keep the working server, note when the problem occurred and what error you saw, then contact your provider. If all servers behave the same way, don't keep importing the same subscription. First check that your basic network works when the client is disconnected, then check the routing setup. Check routing rules only if the app's traffic reaches the client but takes the wrong route. If the logs clearly show a DNS resolution failure, see DNS settings.
After a successful test, keep the settings that worked. If you add per-app rules, change routing, or enable TUN, change one thing at a time and retest the same app and page. When you're done, clear the automatic proxy configuration you enabled in v2rayN under System Proxy. Restore your previous proxy settings if needed, then exit the client. In v2rayNG, tap the running button to disconnect and make sure the app shows that it's stopped. If a problem comes up later, you can start troubleshooting from the last configuration that worked.