v2rayN and v2rayNG Setup Guide
Start with a subscription URL: import nodes, choose which apps to proxy, then test access to confirm the proxy is working.
If you have the client installed and a subscription URL ready, you can complete the initial setup in about 10 minutes. If you haven't installed it yet, choose the right installer on the client downloads page. Before you begin, note your device's current proxy settings. If the device is managed by your organization, check that you're allowed to change them. Where possible, keep the same network throughout the test. Avoid changing nodes, routing, and DNS at the same time; otherwise, even if access is restored, it can be hard to tell which change made the difference.
Step 1: Import a subscription
A subscription URL fetches a list of nodes. It is not a client download link, and it may not be the service's account sign-in page. On the service's website, choose a subscription format compatible with your client, then copy the full URL. It may contain an account identifier or access token, so treat it like a password. Don't post it in public forums or show the URL, subscription details, or QR code in screenshots.
Add a subscription group in v2rayN
Open the main window, go to “Subscription Group,” then open “Subscription Group Settings.” Choose Add, enter a recognizable name in the alias or remarks field, and paste the copied link into the URL field. Save, return to the main window, and select the new group. From the subscription menu, choose Update Current Subscription. If you already have other groups, don't update them all yet; updating just this group makes it easier to tell whether this URL works.
Seeing the group tab after saving means the URL was added, not that the nodes have been downloaded. When the update finishes, new entries should appear in the node list. If the update reports success but the list is empty, check that the right group is selected and review the list filters. Then check the message area for parsing errors or notices about skipped incompatible entries. There's no need to create another group with the same name.
Add and update a subscription in v2rayNG
Open “Subscription Group Settings” from the side menu, tap Add, enter a remark and subscription URL, then save and return to the main screen. Open the menu in the top-right corner and choose “Update Subscription.” If your version supports updating individual groups, select the one you just added. Wait for the update to finish, then check the group for nodes. If the service provided a single-node share link, use the client's import feature for that link instead of adding it as a subscription URL.
If no entries appear, check that you copied the entire URL, including its ending, didn't add spaces, and didn't paste the service's information page instead of a subscription URL. If the update says access is unauthorized, check your subscription status with the service. If it times out, first make sure your network can reach the service, then check whether its instructions recommend a particular update method. Once nodes appear, stay in that group, choose a node the service says is compatible with your client, and continue.
Step 2: Choose a proxy mode
Two settings matter here: proxy coverage determines which apps send requests to the client; routing rules determine whether those requests use a proxy node, connect directly, or get blocked. Enabling the system proxy does not route every app on your device through a node. Setting the route to global also won't cover apps that bypass the client. For your first setup, test with one app and expand coverage only after confirming the connection works.
Test with the system proxy on desktop
Find “System Proxy” in the v2rayN status bar or tray menu. Before changing it, note its current setting—especially if your device already relies on a manual proxy or an automatic configuration script. Use a browser that follows the system proxy for your test. If the browser has an extension that manages its own proxy, check whether it overrides the system settings. If the extension points to a different proxy, test requests may never reach v2rayN, even when the client is running normally.
For a first-time setup, keep the client's current default route. Don't enable both virtual network adapter mode and the system proxy just to see what happens, and don't change the whole device's network settings to get one app working. Command-line tools and apps with their own network settings may ignore the system proxy, so their results alone can't tell you whether the browser connection is working.
Make sure the test app is covered on Android
Check whether per-app proxy is enabled in v2rayNG settings. If it's off, you can leave it that way for now. If it's on, check whether the list means “proxy only selected apps” or “bypass selected apps.” In the first mode, add your test browser to the list; in the second, make sure it's not on the bypass list. The checkboxes mean opposite things in these modes, so don't judge by whether an app is checked.
If another VPN is already active on the device, check whether you can pause it. The system usually can't keep two connections of the same type active at once, and switching may disrupt network access for apps using the existing connection. Once you've chosen the proxy scope, leave DNS and routing unchanged. To learn why the default route may send some requests direct, see the JSON config guide after completing your first test.
Step 3: Start the connection
Return to the node list and select the node you chose for testing. Note that selecting a row and setting it as the active configuration may be separate actions. If an older configuration was already there, clicking a row may only move the selection; the client could still be using the previous node. Before connecting, check the active-item indicator, status bar name, or configuration name on the connection screen.
v2rayN: Start the core, then set the system proxy
Right-click the node and set it as the active server, then check the status or log area. In some versions, changing the active item automatically restarts the core. If the interface says the core isn't running, use that version's start or restart option. Make sure there are no immediate errors, such as the core exiting, a configuration failing to load, or a port already being in use. Then open the “System Proxy” menu and choose “Auto Configure System Proxy” or the equivalent option to send requests from apps that follow system settings to the client.
If the client reports that a port is in use, don't keep trying random ports. First check whether the client is running twice or another local proxy is still active. If you need to change the listening port, make sure the system proxy set by the client and any manually configured app addresses use the new port too. If startup fails, deal with the earliest specific error in the logs first. Changing routing won't make a core that's failed to listen start accepting requests.
v2rayNG: Connect and approve the VPN prompt
Select the node you want on the main screen, then tap Connect. The first time you connect, Android may show a VPN permission prompt. Check that it names the client you just opened before approving it. Denying permission won't delete imported nodes, but the client can't route traffic in this mode without it. If no prompt appears and the status doesn't change, check the app for startup errors, then see whether an existing connection can't be replaced or device management restrictions apply.
A “Started” message or VPN icon in the status bar means the local service is running; it doesn't prove the remote node is reachable. Don't switch nodes repeatedly or treat one speed test as proof that every app can connect. Keep the same node, network, and test app, then check access directly.
Step 4: Test that it works
In the browser you chose in Step 2, open a test page you're authorized to access and that should use the proxy under your current routing rules. Don't rely on a tab that's been open for a while: an existing connection, browser cache, or offline page can make it look as though access still works. Open a fresh tab and load a page you haven't visited, noting the time you made the request. If the page is expected to connect directly, loading it successfully only proves that the direct connection works.
Return to the client and check for a new request around the same time. The details shown vary by client and log level; if the logs show an outbound tag, check whether the request used the proxy or connected directly. Verification is complete only when the local service is running, the test app's request appears in the client, the page loads, and the evidence shows it used the expected outbound. If the logs don't show the outbound, don't assume traffic went through the proxy just because the status says “Connected.”
Page won't load? Check whether the request reaches the client
If there's no matching request in the logs, go back to proxy mode settings. Check whether the browser follows the system proxy, whether the desktop system proxy points to the running client, and whether Android per-app rules exclude the browser. Also check whether the current log level records requests at all. Only suspect proxy coverage first if the logs should show requests under the current settings and still show nothing.
If the request reaches the client but its outbound is direct, check whether an existing routing rule matches the destination before switching nodes. If the request is sent through the proxy but the logs show a timeout or handshake failure, confirm the node and subscription are still valid, then test another compatible node in the same group against the same page. If only one domain reports a DNS error while other tests work, note the error and route in use, then see the DNS configuration guide. Avoid changing several DNS options at once.
Finish testing and restore your original settings
If you're only trying it out, restore the system proxy state you noted before starting, then exit the client. If the system proxy was originally off, clear the proxy settings added during this test. If you stop only the core but leave the system proxy pointing at a local port, the browser may keep sending requests to a service that's no longer running. On Android, disconnect in the client and confirm the system VPN is off. If you paused another connection before testing, restore it the way it was managed originally.
If the test works and you plan to keep using the client, note the current group, active node, and proxy scope—but don't include them in public screenshots. If a subscription update causes problems later, first check whether the active configuration is still there, then repeat the test with the same app and method. Comparing results under the same conditions makes it easier to spot what's changed than reinstalling the client or resetting everything each time.