First Connection · Four Setup Steps

v2rayN Setup Guide

Import an existing subscription, choose a proxy mode, then check the connection with a real request. Allow about 10 minutes for the initial setup if the client is installed and your subscription is ready.

Step 1: Import a Subscription and Update the Server List

Open v2rayN and check that the server list is visible on the main screen. If the client isn’t installed yet, choose the right release package from the client download page. You’ll also need a subscription URL provided by your service provider or network administrator and authorized for use on this device. A subscription URL retrieves server configurations; it’s different from a share link for a single server. If you received a single-server link, use the client’s individual import option instead of saving it as a subscription group. Subscription URLs may contain account credentials, so redact the full address before sharing screenshots or logs.

In v2rayN’s top menu, open “Subscription Group” and select “Subscription Group Settings,” then click Add. Give the group a name that identifies its source and paste the full subscription URL into the address field. Keep the existing path and query parameters; remove only any accidental leading or trailing spaces, then save. Return to the main window and select the new group. An empty list at this point doesn’t mean saving failed: the group stores the source for retrieving configurations, but you still need to update it to load server entries.

From the “Subscription Group” menu, select Update current subscription. For a first-time setup, if your current network can reach the subscription URL, try the update option that doesn’t use a proxy. This avoids relying on a connection that hasn’t been set up yet. Once the update finishes, check that entries appear and verify the group name, server remarks, and protocol types. Updating only the current group makes it easier to distinguish new entries from existing manual configurations. Entries in the list only show that the client read recognizable configurations; they don’t confirm that the remote servers are reachable.

If the list is still empty, check the logs to see whether the request failed or completed without parsing any entries. In the first case, check that the URL is still valid and reachable from your current network. In the second, ask the provider to confirm that the response uses a subscription format supported by your client, rather than a login page or web instructions. A failed update to a group with existing entries may leave old entries visible, so check the log for the latest update. Once at least one entry is recognized, continue to proxy mode settings. See the glossary for definitions of key terms.

Step 2: Choose a Proxy Mode

For your first setup, establish a baseline with a browser that follows system proxy settings. In the v2rayN main window or tray menu, find the system proxy setting and select “Set system proxy automatically.” This tells the system to send requests from supported apps to the client’s local proxy. It doesn’t route all traffic from the device. Apps with their own proxy settings may continue using them, and running apps may need to be restarted to pick up the change.

Keep the client’s existing routing configuration for now. Don’t change routing, DNS, and server settings all at once just to test the connection. The system proxy determines how requests enter the client; routing determines which outbound route they take. A test destination may still connect directly if a routing rule says so, even when the system proxy is enabled. For the next check, use a test destination that should go through the proxy under your current rules. The system proxy toggle alone can’t tell you which route a request took.

If the app you want to use doesn’t follow system proxy settings, consider TUN mode. TUN captures traffic through a virtual network interface and covers more apps than the system proxy, but it also involves system permissions and routing changes. First, confirm that the system proxy test works and the server is reachable. Then clear the system proxy setting you enabled for this test, grant TUN permissions as prompted by the client, and test TUN separately. If your device has proxy or virtual network settings managed by your organization, confirm that changes are allowed and record the original values first. Switching modes doesn’t give you permission to overwrite those settings. If you lack permissions or an existing virtual interface conflicts, don’t keep toggling settings; restore the last working mode first.

On v2rayNG for Android, keep the default traffic coverage for the first test. If you’ve configured per-app proxying, make sure the browser you’re testing with isn’t excluded. This step determines how app traffic enters the client; next, you’ll choose the server to use. For details on protocols, transports, and security layers, see the protocol guide. There’s no need to change these settings before your first connection.

Step 3: Choose a Server and Connect

Return to the group you just updated and, if possible, choose a server the provider has explicitly marked as available. Select the entry, then use the right-click menu to set it as the active server. If your version supports setting the active server with a double-click, verify the status afterward. Highlighting a row only selects it in the list; it may not change the active configuration. Check the current server shown in the main window or status bar and make sure it matches your selection. If several entries have the same name, use the group and protocol type to tell them apart. There’s no need to edit their addresses or ports first.

After you switch the active server in v2rayN, the client usually loads its configuration. Check the logs for errors while the core reads the configuration or listens on the local port, then open your test destination in the prepared browser. A listening local port means the client can accept requests; the remote connection is usually attempted only when a request is routed through the proxy. Until the browser sends a request, startup logs don’t show that a remote connection succeeded.

In v2rayNG for Android, select an entry, then tap Connect on the main screen. When connecting for the first time, check that the system’s VPN request is from the client you just opened, then approve it as prompted. Once the connection button changes state or the VPN indicator appears, switch to your prepared browser and send a request. The system indicator means the local VPN is active; it doesn’t confirm a successful handshake with the remote server. If no traffic from the test app reaches the client, check whether the app is excluded from the traffic coverage instead of immediately switching server groups.

If a request fails, note the test time and the first related error, then check one likely cause. If the core reports that a local port is already in use, check whether another client instance or local service is listening; don’t terminate processes you don’t recognize. If the app request reaches the client but the remote connection keeps timing out, leave the mode and test destination unchanged and compare it with another authorized entry in the same group. If only one entry fails, first check whether it’s still available. If several entries fail at the same stage, use the troubleshooting sequence in the help center to check shared settings.

Step 4: Verify That the Proxy Is Working

During verification, distinguish three outcomes: the app sent a new request, the client routed it as expected, and the request received a response. In your browser, reopen a test page that should use the proxy under your current rules and is approved for testing; an already-open tab doesn’t count as a new request. If the page may be cached, use the browser’s developer tools Network panel to check whether a request was actually sent. Then check the client logs for the destination around the same time. If the logs show outbound routing, confirm whether the request used the proxy or connected directly, and check the page response to see whether it completed.

To confirm the exit address, use a diagnostic page provided by your service provider or a test service authorized by your network administrator that shows the request’s source. Use the same browser and destination for comparison where possible, and first make sure your existing routing rules don’t send the diagnostic destination directly. If the page loads but there’s no matching proxy entry in the logs, the request may have connected directly, or the current log level may not record individual requests. A successful page load alone isn’t enough to draw a conclusion. The exit address may also differ from the address listed for the server, so check it against the provider’s information for that connection.

If the logs show that a request reached the client but got no response, keep the proxy mode unchanged and check whether the error occurred during name resolution, connection establishment, or the protocol handshake. If the proxy test destination works but another app doesn’t use the proxy as expected, check whether it follows system proxy settings, has its own proxy configured, or is covered by TUN or Android’s traffic settings. Change one condition at a time and repeat the same test to identify whether the difference is caused by the app, mode, routing, or server. Latency tests can help narrow down server choices, but they don’t replace a real request from the app.

Keep the current configuration once the active server is correct, the test app’s request takes the expected route, and it receives a response. When you’re done, clear the system proxy setting you enabled for this test on desktop, or turn off TUN if you enabled it. If you had existing proxy settings, restore their recorded values before closing the client. On Android, return to v2rayNG and tap Disconnect, then confirm that the system VPN status updates. Finally, use the same browser to revisit a site that normally connects directly and check that network behavior matches what you saw before the setup.