Getting Started · First Connection
v2rayN Setup Guide
Go from a subscription URL to your first test request. Get one server working before adjusting routing.
Import a Subscription
Before you start, make sure the client opens normally and that you have a subscription URL you’re authorized to use. If you haven’t installed a client yet, choose one from the download page. Subscription URLs often contain access credentials. Copy the entire URL into the client, and don’t share the URL, screenshots containing it, or logs that include credentials. For your first setup, add just one group and give it a recognizable name. That makes it easy to confirm which subscription populated the list after an update.
v2rayN for Desktop: Save a Group, Then Update It
Open “Subscription Groups” in the main window, go to group settings, and choose Add. Paste the URL into the subscription URL field, enter a name, and save. Back in the main window, select the group you just created, then use the subscription menu to update the current group. If your network can access the subscription URL directly, choose the update option that doesn’t use a proxy; this avoids relying on a local proxy that isn’t running yet. When the refresh finishes, the list should show servers with the name you entered. Saving a group stores the URL; updating it fetches the subscription data.
v2rayNG for Android: Update, Then Return to the Server List
Open the menu in the top-left corner of the main screen and go to “Subscription Group Settings.” Tap Add, then enter a name and URL. Save, return to the server list, switch to the group you just created, and choose Update subscription from the top-right menu. When the update finishes, confirm that entries appear in that group. Don’t paste a subscription URL into the server address field for manually adding a server: the subscription URL fetches a list of configurations, while that field accepts the address of a single server.
If an update fails, first check whether the error occurred during the request or while parsing the response. For a timeout, confirm that the device can access the internet, then check with the subscription provider about the update method. For an unauthorized or invalid URL error, make sure you copied the full link and that it’s still valid. If the update finishes but the list is empty, clear any search or filter, then confirm you’re viewing the right group. Once servers appear, continue to the next step; you don’t need to run a latency test yet. A successful update only means the configuration was downloaded, not that its servers can connect.
Choose a Proxy Mode
First decide which app will send the test request. For your first setup, choose one browser; there’s no need to route traffic from every app on the device. The proxy mode determines whether requests are handed to the client. Routing rules then determine whether the client sends them through the proxy, connects directly, or blocks them. These are separate settings. Even with the system proxy enabled, requests that match a direct-connection rule won’t use the selected server, so choose a test destination that should be routed through the proxy under your current rules.
Desktop: Start with the System Proxy, Not TUN
Leave TUN turned off. Choose a browser that uses the system proxy settings for your test, then find an option such as “Set system proxy” in the client’s system tray or proxy menu. You’ll enable it after selecting an active server and confirming that the core has started. If your device already uses a work or school proxy, note the current settings first. On managed devices, keep the existing policy in place rather than overriding it for a test.
The system proxy only affects apps that follow that setting. Some browsers and extensions have their own proxy settings, which can override the system choice. Before testing, check whether your browser uses the system settings or a separate configuration. If you’re comfortable configuring a proxy in the app itself, check the client settings for the actual local listening address, port, and proxy type, then enter matching details in the app. Choose one connection method; don’t use a server address and port where the app expects a local proxy address.
Android: Use VPN Mode and Check App Filtering
In v2rayNG settings, confirm that VPN mode is enabled. If your version offers a service mode, make sure you haven’t selected a mode that only starts a local proxy. Check whether per-app proxying is enabled. For your first test, turn off app filtering if possible. If you need to keep it on, make sure the test browser is included in the allowlist or excluded from the blocklist, depending on which list mode is selected. Otherwise, Android may show the VPN as active even though the browser never sends requests to the client. Once the apps covered by the VPN are set, return to the server list and select an active server.
Select a Server and Connect
Choose a server from the group you just updated, using a recognizable name and one the subscription provider marks as available. Use this server for the entire test; if it fails, don’t change the group, proxy mode, and routing rules all at once. You only need to note the server name and your current network—not its address or credentials. If you test another server for comparison, keep the proxy mode and test destination the same.
Desktop: Set the Active Server and Check the Logs
In the v2rayN list, right-click the server you want and choose “Set as active server.” Check the list or status bar to confirm the active indicator has changed. This normally loads the selected configuration. Review the main window logs for errors such as a configuration parse failure, a core startup failure, or a local port binding error. Then enable the system proxy as planned, or use a test browser with the local proxy already configured. Clicking a row to highlight it doesn’t switch the core to that server; check the active indicator instead.
If enabling the system proxy stops even normally accessible websites from loading, turn it off to restore your usual connection, then check whether the proxy listener started. If the logs report that a port is in use, check whether another client or an old instance is already using it. Close any instance you don’t need. If you change the listening port, update the port entered in your app as well. Don’t keep switching remote servers while the core hasn’t started successfully.
Android: Select a Configuration and Approve the VPN Request
Tap the server you want in the v2rayNG configuration list and confirm it’s selected, then tap the connect button at the bottom. The first time you connect, Android will show a system connection request. Confirm it was initiated by the client you just opened, then allow the VPN connection. Check that the connect button shows a running state and review the system VPN status or client notification. If it quickly returns to disconnected, check the client logs for the startup error. If another VPN is active on the device, resolve the conflict first rather than repeatedly tapping Connect.
A running core in the desktop client or an active VPN status on Android means the local connection is ready. It doesn’t prove that a request has reached its destination through the proxy. Next, send a request from the test app you selected.
Test Whether the Proxy Works
In the browser you chose in the previous step, open a known working website that should use the proxy under your routing rules. If possible, choose a page you haven’t visited during this test, then refresh it to avoid seeing only a cached copy. Note the time and check the client’s connection status and logs. If access logging is enabled, look for the destination domain and confirm that any visible outbound identifier matches your expectations. A page loading by itself isn’t enough—it may have connected directly. Client traffic by itself isn’t enough either; it could come from another app.
Check the Exit IP with a Like-for-Like Comparison
You can use an exit IP lookup service you trust to compare results with the proxy off and on, using the same browser and network. Before comparing, make sure the lookup domain matches a proxy rule; otherwise, both requests may connect directly. If the exit IP changes as expected, cross-check it against the client logs from the same time. If it doesn’t change, don’t assume the server is unavailable. First confirm that the lookup request reached the client and wasn’t routed directly, then investigate the server. Don’t switch between Wi-Fi and mobile data during the test, or you won’t know what caused the IP change.
V2Ray Server Latency Tests and Troubleshooting
Latency tests in the client are useful for comparing servers, but they don’t replace testing with an app. Different test options measure different paths: some only check whether the server address and port are reachable, while others access a test URL through the proxy. A successful connectivity check doesn’t prove the protocol handshake or destination access will work; a failed test through the proxy may simply mean the test destination is unreachable. First get one path working with an app request, then compare servers using the same test and network for meaningful results.
If you can’t find the test request in the access logs, check how traffic reaches the client: on desktop, confirm the browser follows the system proxy; on Android, check that the VPN is still connected and the app is included in its scope. If the request appears but is marked direct, check which routing rule matched. If it’s clearly routed through the proxy but times out, try a second-choice server and change nothing else. For a DNS error, determine whether the test destination failed to resolve or the server’s hostname did; they occur at different stages of the connection. Recording the error type and time makes it easier to find the cause than changing DNS, routing, and servers all at once.
Finish Testing and Restore Your Network
For a quick test, turn off the system proxy you enabled, then exit the desktop client. If the device already had proxy settings, restore the original configuration. If you configured a proxy directly in an app, remove the test address and port there too. On Android, disconnect in the client, then confirm in system settings that the VPN has stopped. Finally, use the same browser to open a website that should connect directly and confirm that your regular network access is back. You’ve now verified all four steps: subscription update, server activation, app routing, and an actual request.