Initial setup About 10 minutes
Getting Started with v2rayN and v2rayNG
Import a subscription, choose a proxy mode, connect, then check the traffic with a new request.
Before you start, get a valid subscription URL and make sure you can browse the web on your current network. Haven’t installed a client yet? Choose an installer on the client downloads page, then return to step one.
Import a subscription
Make sure you have a client subscription URL, not a provider login page, account page, or share link for a single server. A subscription URL retrieves a list of servers. Adding a group only saves the URL; you must update it to load the servers. The URL may contain account credentials, so paste it directly into the client. Don’t share it in chat messages, support tickets, or public screenshots.
v2rayN: Add a subscription group
Open the main window and go to “Subscription Group” → “Subscription Group Settings” from the top menu, then click “Add.” Enter a recognizable name under “Alias,” paste the full subscription URL into “Optional Address,” and save. Field names vary slightly by version; make sure the URL goes in the subscription address field, not the alias. Back in the main window, open the “Subscription Group” menu and select “Update All Subscriptions.” If you don’t want to refresh other groups, select the new group and choose the option to update the current subscription instead. When the update finishes, switch to the new group and confirm that servers appear in the list.
v2rayNG: Save the URL and update the list
Open “Subscription Group Settings” from the top-left menu and tap the plus sign in the top-right corner. Enter a group name under “Remarks,” paste the subscription URL into the address field, then tap the confirmation button in the top-right corner to save. Return to the server list, open the top-right menu, and select “Update Subscription.” When the update finishes, switch to the group and check that servers appear. The plus sign on the Android main screen can also import a single server. If it opens options such as QR code or clipboard import, return to the side menu and open Subscription Group Settings instead.
If the server list is empty
First, check that you selected the group you just added, not an older one. Then open its edit screen and verify the URL, especially any parameters at the end; make sure you didn’t paste the accompanying instructions too. If the update times out, check that your network is working, then review the update message or logs. If it says the URL is unauthorized, expired, or returned data that couldn’t be parsed, check the subscription source and make sure the URL is valid and in a format the client supports. A failed subscription download is different from a failed server connection. If the list is empty, fix the download issue first; there’s no need to change proxy modes yet.
Choose a proxy mode
Decide how app traffic will reach the client before connecting. Proxy mode determines how traffic enters the client; routing rules determine whether it is proxied, connected directly, or blocked after that. For your first test, keep the existing default routes. Don’t add rules or change DNS. That way, if something goes wrong, you can first determine whether the app is using the proxy or whether a routing rule sent the request to a different outbound route.
v2rayN: Test with the system proxy first
Find the system proxy options in the main window or tray menu and make sure “Enable TUN Mode” is off. After selecting a server in the next step, choose “Automatically Configure System Proxy.” This sends requests from apps that follow the system proxy settings to the local proxy, making it a good first test with a regular web browser. If your browser has its own proxy settings or an extension that overrides them, make sure it uses the system settings. Otherwise, you may not be testing v2rayN’s system proxy.
If the app you want to test doesn’t follow the system proxy, test TUN separately after the browser test works. Before switching, clear the system proxy settings applied by the client, then enable TUN so you can distinguish between the two traffic-capture methods. For details about TUN permissions, virtual network adapters, and OS differences, see the complete setup guide. You don’t need both modes enabled for your first connection test.
v2rayNG: Keep the default VPN app scope
Android doesn’t use the desktop tray-menu workflow. If your version lets you choose between VPN mode and proxy-only mode, choose VPN mode for this test. If the main screen is the VPN start screen, leave the default settings as they are. In Settings, make sure per-app proxy rules don’t exclude your test browser. If you’ve set up an app list before, note the existing settings, temporarily disable app filtering, and restore it after the test. Disconnect any other active VPN before starting v2rayNG; otherwise, Android may reject the new connection or replace the existing session.
For terms like “system proxy,” “TUN,” and “per-app proxy,” see the quick reference. For this step, choose one way to route traffic: start with the system proxy on desktop or VPN on Android. Next, select a server and connect without changing transport settings or routing rules.
Connect
Choose a server from the group you just updated. If the group has several servers, pick one for your first test and note its name. Don’t switch servers and modes while refreshing the page. Treat speed test results only as a clue: a successful test doesn’t prove that your everyday app traffic is being proxied.
v2rayN: Set the active server and configure the system proxy
Right-click the server you want in the list, select “Set as active server,” and confirm that it’s now the active one. Then open the v2rayN menu in the system tray and choose “Automatically Configure System Proxy.” Some versions offer the same settings in the main window. Check the status and runtime logs on the main screen. If you see an error starting the core, reading the configuration, or binding a local port, fix that first, then open your browser. Selecting a server in the list doesn’t make it the active server. Before retrying, confirm which server is in use.
If you’ve just closed another proxy app but still see repeated port-in-use errors, don’t force-quit processes you don’t recognize. Make sure the other app has exited rather than being minimized to the tray, then restart the client you’re testing. If the startup logs show no errors but your browser still can’t connect, keep the current configuration and continue to the verification step. A page failing to load doesn’t prove that the core failed to start.
v2rayNG: Select a server and approve the VPN request
Tap the server you want in the list and check that the selection indicator moves to it. Then tap the round Start button on the main screen. The first time you connect, Android usually displays a system VPN connection request. Confirm it’s from the v2rayNG session you just started, then tap “OK.” Return to the main screen and check whether the button now lets you stop the connection. You can also check the system VPN status to see whether a session is active. The VPN icon in the status bar only means a VPN session is running on your device; it doesn’t confirm that the server responded.
If the client immediately returns to a disconnected state after you tap Start, check whether you denied the system request or another VPN is still running, then look for a clear error in the client logs. When switching servers, if your version doesn’t restart the connection automatically, stop it first, select the new server, and start again. Change one thing at a time so you can tell whether the issue is authorization, the server, or the traffic-capture method.
Check that it works
Check the route with a new request
Keep the server and proxy mode you selected. Open your test browser and visit a site that should use the proxy under your current routing rules and is suitable for testing. Don’t use an old tab as proof: the page may be cached or the browser may be reusing an existing connection. Note the approximate time, then check the client logs for that period or see whether traffic counters have increased. If the logs show the request matched a proxy outbound and the page loads, you’ve confirmed both that the request reached the client and that it took the expected route.
If your current log level doesn’t show outbound routes, increased traffic is only a clue; by itself, it can’t prove that a particular webpage went through the proxy. You can also check a trusted service that reports your public IP, as long as your rules should route it through the proxy. Compare the results before and after connecting, and check them against your routing settings. If a site is supposed to connect directly, an unchanged IP or a direct-connection log isn’t a problem. And a successful test for one site doesn’t mean every app uses the same outbound route.
Connected, but websites won’t load
First, check whether the browser is sending requests to the client. On desktop, make sure “Automatically Configure System Proxy” is still enabled and the browser uses the system proxy. On Android, check that the VPN is still connected and that per-app settings haven’t excluded the test browser. If the logs show no sign of the request, troubleshoot this entry point before changing servers. If the request reached the client, check whether it matched a direct route, was blocked by a rule, or failed after being sent through the proxy.
If the logs show a connection timeout, keep the same proxy mode and test destination, and try a different server. If several servers fail, check your network connection and subscription status. For handshake errors, check that the device’s date, time, and time zone are correct, and make sure the subscription is up to date. Don’t work around the error by disabling certificate verification. If a desktop browser works but other apps don’t, check whether those apps use the system proxy. If v2rayNG works in the foreground but disconnects in the background, check Android’s battery settings. For troubleshooting by error type, see How to troubleshoot v2rayN runtime logs.
Disconnect and restore your settings
After testing on desktop, choose “Clear System Proxy” from the tray menu. If you switched to TUN, turn it off as well. On Android, return to v2rayNG and tap Stop, then confirm the system VPN session has ended. Send a new, ordinary web request and check that your network is back to the expected state. If your device was already using a work proxy or one configured by another app, restore the settings you noted before testing. Don’t assume the cleared settings match your original configuration.
The subscription group contains servers, the client is running, and a test request used the expected outbound route. That’s all you need for initial setup. For custom routing, per-app proxy settings, and background operation, see the complete setup guide.