QUICKSTART / FIRST-TIME SETUP

v2rayN and v2rayNG Setup Guide

From subscription URL to connection test. If the client is installed and your subscription is ready, allow about 10 minutes for a first run. There’s no need to adjust DNS or routing rules in advance.

STEP 01 / SUBSCRIPTION

Import a subscription

Start with the full URL provided by your subscription provider. A subscription URL retrieves a set of configurations; it is not a link to the provider’s account dashboard. Keep any query parameters at the end of the URL when copying it—don’t copy just the domain. Subscription URLs may contain access credentials, so hide the entire URL in screenshots or logs you share for support. Don’t paste it into an unfamiliar conversion website.

v2rayN: Add and update a subscription group

In the main window, open “Subscription Group → Subscription Group Settings” and add a group. Enter a recognizable name in the remarks field, paste the subscription URL into the address field, and save. Back in the main window, switch to the group you just added. From the “Subscription Group” menu, choose the command to update the current subscription. If you don’t have a working proxy yet and the menu offers both “Update via proxy” and “Update without proxy,” choose “Update without proxy” if your current network can reach the subscription service directly. When the update finishes, check the group’s configuration list.

v2rayNG: Save a subscription URL from the side menu

Open the menu in the top-left corner, go to “Subscription Group Settings,” and tap the plus button. Enter a remark and subscription URL, then tap the save icon in the top-right corner. Return to the configuration list, select the relevant group, and choose “Update subscription” from the more menu in the top-right corner. If the list is still empty after saving, make sure you’ve run the update. Saving a group only stores the URL; it doesn’t fetch configurations. Menu labels may vary slightly between client versions. Look for the group settings and update subscription actions.

Before continuing: The list should show one or more named configurations. If you see a network error, check that your current network is working, then verify the URL and subscription validity in the client. If the update reports success but no configurations appear, make sure you’re viewing the group you updated and check the subscription format with your provider. Don’t repeatedly add the same URL after one failed attempt. Once configurations appear, choose one marked as available by your provider. Next, decide which apps should send requests through the client.

STEP 02 / PROXY MODE

Choose a proxy mode

For the first test, use just one way to route traffic through the client. Proxy mode determines how app requests reach the client; routing rules determine whether requests are proxied or sent directly once they arrive. These are separate settings. Even with the system proxy or VPN enabled, requests matching a direct-connection rule may still go out over your local network. Leave your existing routing and DNS settings unchanged for now to avoid changing multiple variables at once.

v2rayN: Test a browser with the system proxy

Find “System Proxy” in the tray menu. For this test, use “Automatically configure system proxy,” but wait until the next step to confirm the active configuration and core status before enabling it. Test with a browser that follows the system proxy. If your browser has a proxy set through an extension or its own settings, note the current settings and switch to a browser that clearly follows the system proxy. Otherwise, even if a webpage opens, it may be hard to tell which proxy was actually used.

Keep TUN off during testing. The system proxy works for apps that support it, but not every app uses system settings. If the browser test succeeds but a particular app still bypasses the proxy, check that app’s network settings before reinstalling the client. To learn how TUN handles traffic, see advanced configuration.

v2rayNG: Turn off per-app proxy for the first test

Open “Settings” from the side menu and check “Per-app proxy.” Leave it off for the first test so the test browser isn’t excluded by the app list. If your phone already has proxy rules you need to keep, don’t change them; test with an app you know is included in the VPN instead. When you adjust the app list later, check the “Bypass mode” setting first: with bypass enabled, checked apps are excluded; with bypass disabled, checked apps are included.

Before continuing: On desktop, make sure you’ll test with the system proxy. On Android, confirm the test app is included in the VPN’s scope. If another VPN service is running on the device, check whether it can be paused. For connections managed by a work profile or device policy, follow your administrator’s instructions rather than removing restrictions yourself. Next, start the configuration you selected; there’s no need to edit server fields.

STEP 03 / CONNECT

Connect

Before connecting, use your chosen browser to open a page that normally works and record the baseline. If you plan to compare your public IP address, note the result from a trusted IP lookup site now. Keep the network unchanged: don’t switch from Wi-Fi to mobile data right after recording the baseline, or any change in your outbound address could be caused by the network switch rather than the client.

v2rayN: Set the active configuration, then enable the system proxy

Return to the configuration list, right-click the configuration you selected, and choose “Set as active server” or the equivalent command in your version. Selecting a row doesn’t make it the active configuration. Make sure the active indicator moves to the right item, then check the log area at the bottom of the main window for repeated core startup failures or local port conflicts. Next, open “System Proxy → Automatically configure system proxy” from the tray menu. If the tray icon is hidden in the system’s overflow area, open that area to find the client icon.

If the core reports a port conflict, stop other proxy programs on your device that you no longer use, then check whether the active configuration starts normally. Don’t terminate processes you don’t recognize. If the system already had a manually configured proxy, note its settings. When testing is done, choose “Clear system proxy” from the same tray menu, then restore the previous settings if needed. Don’t assume that closing the client will restore the proxy settings that were in place before.

v2rayNG: Approve Android’s VPN connection request

Select your chosen item in the configuration list on the main screen and make sure the active indicator is on the right configuration. Then tap the round Start button. The first time you connect, Android will show a VPN connection request. Check that the prompt names v2rayNG, then tap “OK.” After approval, the button on the main screen should change state. Your phone may also show a VPN indicator in the status bar or notification area, depending on the system.

If the connection doesn’t stay active after you tap the button, check whether permission was canceled, another VPN is in use, or the configuration failed to start. A VPN indicator doesn’t prove the remote server is reachable; it only means the system VPN session is established. Once the client shows that it’s running, stay on the same network and test with a real request.

STEP 04 / VERIFY

Test the connection

Return to the browser you used for the baseline, open a new tab, and visit the same test service. Don’t rely on a page that was already loaded—the browser may show a cached copy. If you’re comparing public IP addresses, use the same lookup service and address type, then refresh the result. An expected change in your outbound address can help confirm that this request used the proxy, but it doesn’t prove that every app on the device uses the same route.

If the address hasn’t changed, first check whether the browser is included in the proxy’s scope, then see whether the test destination matched a direct-connection rule. Open the client’s “Logs,” note when you made the request, and look for a matching destination and outbound connection. The information shown depends on the log level. An outbound record can help distinguish proxied traffic from a direct connection, but an empty log alone doesn’t prove that the connection failed. If the result is still unclear, don’t change DNS, routing, and the active configuration all at once; you won’t be able to tell which change affected the next test.

Narrow down request failures by symptom

If the test page won’t open either before or after connecting, try another page that normally works to check your basic network connection. If it only fails after connecting, first check whether the client received the test request. If not, check the system proxy, any browser-specific proxy settings, or the Android per-app list. If the logs show requests that keep timing out, keep the same mode and test another known-working configuration from the same subscription. If you see a name resolution error, note the domain and check your DNS settings; don’t diagnose a DNS problem from a single timeout.

The client’s latency test can help you screen configurations, but a successful probe doesn’t guarantee that an app can connect. Use a new request from the target app as the final test. If the issue occurs in just one app while the browser test succeeds, check the app’s own proxy behavior or its per-app scope first. For background on VpnService, routing, or domain policies, see the quick reference. For specific issues such as failed subscription updates or disconnects after granting permission, see troubleshooting.