First Connection · 4 Setup Steps
v2rayN and v2rayNG Setup Guide
Go from importing a subscription to confirming that browser traffic uses the proxy. If you have the client and subscription ready, you can get one device connected in about 10 minutes, then fine-tune your routing rules.
Before you begin, get a subscription URL from a trusted provider and make sure your device can access the internet with the proxy off. Haven't installed a client yet? Download a client. Subscription URLs may contain access credentials. Don't post the full link in public forums, screenshots, or online testing tools.
Import and Update a Subscription
First, distinguish a subscription URL from an individual share link. A subscription URL retrieves and updates a group of server configurations; a share link imports just one. The steps below cover subscription URLs. If your provider gives you both a website link and a client subscription URL, copy the latter—not a login or information page.
v2rayN: Add a Subscription Group
Open the main window and go to Subscription Group > Subscription Group Settings, then click Add. Give the group a recognizable name and paste the full subscription URL into the address field. Make sure it has no trailing line break or stray spaces, then save. Back in the main window, select the new group and choose Update current subscription from the Subscription Group menu. If the app offers both proxied and direct updates, try a direct update first, provided the subscription URL is reachable on your current network.
After the update, switch to the new group in the main server list and confirm that server entries appear. Seeing only the group name means the URL was saved, not that the server list was retrieved. If you see old entries from another group, switch to the intended group before checking. Entries elsewhere in the list don't prove this update succeeded.
v2rayNG: Save, Return to the List, and Refresh
Open the side menu, go to Subscription Group Settings, tap Add, enter a name and subscription URL, then save. Return to the server list and look for Update subscription or Update subscription group in the top-right menu. When the update finishes, open the relevant group and check for new entries. If old and new configurations both appear, confirm the group name and choose a recommended server from the group you just imported.
If the update fails, check that the URL was copied in full and the subscription is still valid, then verify your device's date and time zone. If the error mentions a certificate or time, correct the system clock; don't disable certificate verification just to complete the import. If the update reports success but the group is empty, check that the provider returned a configuration the current client can read—not a login prompt or web page. For more specific causes, see Troubleshooting. Continue once the list contains available servers.
Choose a Proxy Connection Method and Routing Mode
The connection method determines which apps send requests to the client; the routing mode determines whether the client sends those requests direct or through the proxy. These are separate settings. For example, enabling the system proxy in v2rayN usually sends requests from browsers that follow system proxy settings to the client, but routing rules may still send a particular request direct. Conversely, global routing won't make apps that ignore the system proxy send their requests to the client.
v2rayN: Test Your Browser with the System Proxy
Find System Proxy in the tray menu and note the current setting. If a manual proxy or auto-configuration script is already set, record it so you can restore it after testing. Start with the system proxy; you don't need to enable TUN as well. Locate the option to automatically configure the system proxy, but wait to enable it until you've selected an active server in the next step. The browser you use for testing should follow system proxy settings. If it has its own proxy configured, the test may reflect that instead.
In the main window's routing options, if there's a preset labeled Global or Global Proxy, note the current selection and switch to it temporarily. For the first test, you just need to confirm that a proxied request can succeed; temporary global routing avoids a test domain accidentally matching a direct-route rule. If there's no such preset, keep the current routing mode and choose a test site that should clearly use the proxy. You don't need to write custom rules for the first connection.
v2rayNG: Check VPN Mode and App Coverage
In settings, make sure the app is using VPN service mode, not a mode that only provides a local proxy port. Then check whether per-app proxying is enabled. With an allowlist, the test browser must be included; with a blocklist, it must not be included. For the first test, just check this setting—you don't need to change permissions for other apps.
If your version offers global proxy or routing presets, note the current selection and choose a route for testing in the same way. If another VPN service is running on your device, don't mix up the status of the two services. Check whether you can pause the existing one before continuing. You should now know how the browser connects and which route the test request is expected to take. Next, start the connection.
Select a Server and Connect
v2rayN: Select an Active Server and Enable the System Proxy
In the target group, select the server you want to test, open its context menu, and choose an option such as Set as active server. Highlighting a row alone doesn't switch servers; confirm the active configuration indicator or server name in the status bar has changed. Then open the tray menu and choose Automatically configure system proxy under System Proxy. Return to the main window and check the logs for errors such as a core startup failure or a local listening port conflict.
If the logs report a port conflict, check for another client instance or proxy app running. Don't test multiple servers while changing ports in bulk. Resolve the local listening issue first, then retest the same server so you can identify what changed. A normal tray status only shows that the relevant settings were applied locally; it doesn't confirm that the remote server accepted a request.
v2rayNG: Start the VPN Service
Return to the server list, select an entry, and make sure the selection indicator is on the server you're testing. Tap Connect on the main screen. The first time, Android usually displays a VPN connection request. Confirm it comes from the client you just opened, then allow the connection. Wait for the button to show that the service is running, and check for a VPN icon or notification. If you denied permission, tap Connect again in the client; there's no need to reimport the subscription.
If the service stops immediately after starting, note the time and check the runtime log for the first error related to the shutdown. You can also disconnect and compare with another known-working server from the same subscription, changing only the server—not transport settings, routing, and DNS all at once. The Connect button and VPN icon show whether the local service has started. The request test in the next step will help distinguish a remote connection failure from a routing mismatch.
Verify the Proxy with a Real Request
Make a New Request and Check the Runtime Log
Leave the client running and open a new page in the browser you confirmed will use the proxy. Don't rely on an already-open tab: an old page may be cached, and an existing connection may keep using its previous network route. You can restart the browser, then visit a publicly accessible test page that doesn't require sign-in. Note roughly when you made the request, then check the client log for the same time.
If the log shows the request destination and routing result, find the entry for your test domain. A proxy outbound tag (for example, proxy) together with a successfully loaded page confirms that this request used the proxy as expected. A direct tag (for example, direct) with a page that loads only confirms the request went direct. Tag names depend on your configuration. If the current log level doesn't show outbound details, temporarily increase its verbosity, test again, then restore the original setting.
You can also use a trusted public IP lookup site as a secondary check: test once with the proxy stopped, then use the same browser and site after connecting. A changed IP can support the conclusion that your exit route changed, but an unchanged IP alone doesn't prove failure—especially if the request matched a direct-route rule or both routes share an exit IP. Don't treat a single speed test, button color, or system icon as proof.
Diagnose by Symptom, Then Restore Your Usual Settings
If the request isn't in the log, check the connection settings first: on desktop, make sure the browser follows the system proxy; on Android, confirm the VPN is still running and the browser isn't excluded. If the request reached the client but went direct, check whether the selected route matches your expectations. If a proxy outbound attempt timed out, failed to handshake, or hit a DNS error, note the first relevant error and its time, then troubleshoot by symptom in Troubleshooting. Before sharing logs, remove subscription URLs, credentials, and any browsing records you don't want to disclose.
After a successful first test, switch from temporary global routing back to your usual routing preset, then test one destination expected to go direct and another expected to use the proxy. Testing only the proxy route can miss a local service issue; testing only the direct route won't confirm the proxy works. For help with rule order, DNS, or TUN, see the Advanced guide. Change one setting at a time and keep a record of its original value so you can restore it.
If you were just trying it out, you can disconnect here. On desktop, restore the system proxy setting you recorded before starting, then quit the client. If no system proxy was configured originally, use the tray menu to clear the setting applied by the client. On Android, tap the connection button to stop the service and confirm the system VPN status clears. Finally, open a page that normally works without a proxy to make sure regular internet access is back.