First-time setup · about 10 minutes
v2rayN and v2rayNG Quick Start Guide
Import servers with a subscription, connect, then check whether your target app is using the proxy.
Before you begin, get a valid subscription URL. Haven’t installed a client yet? Choose a package for your device on the download page.
Import a subscription
First, make sure you copied the subscription URL provided by your service—not a sign-in page, account page, or single-server share link. A subscription URL retrieves a list of configurations, while a share link describes one server; each uses a different import option. Subscription URLs may contain account identifiers, so don’t include them in public screenshots or support requests. If you copied the URL from a chat message, check its beginning and end after pasting to make sure you haven’t included quotation marks, punctuation, or a line break.
v2rayN for desktop
Open the main window, go to “Subscription groups” > “Subscription group settings,” and add a subscription. Enter a recognizable name in the remarks field, paste the full URL, save, and return to the main window. Switch to the new group, then select “Update current group” from the “Subscription groups” menu. If you have multiple sources, update only the group you just added so you can confirm that the import worked.
v2rayNG for Android
Open the main menu, go to “Subscription group settings,” tap Add, enter the URL in the subscription address field, and save. Return to the configuration list, switch to the new group, then select “Update subscription” from the menu. Saving only stores the URL; servers appear after the update finishes. If you received a single-server share link, leave subscription settings and import it from the configuration list using the plus button and clipboard. You don’t need to update subscriptions for a share link.
When server entries appear in the new group, continue to the next step. If the group is still empty, first check that you’re viewing the right group, then review the update message: for a connection timeout, check that your device is online; if the URL is invalid or leads to a sign-in page, ask your provider whether the subscription is still active. If the update succeeds but the group remains empty, check whether search or group filters are hiding the entries. Don’t switch proxy modes back and forth—the system proxy and VPN can’t fix an empty configuration list. See the subscription group guide for group management and filters.
Choose a proxy mode
For your first test, route traffic from just one app through the client. Keep these two settings separate: system proxy, VPN, or TUN determines how traffic reaches the client; routing rules determine whether it’s proxied or sent directly. Enabling the system proxy doesn’t mean every app or site will use the remote server. Keep your existing routing rules for the first test, then adjust them as needed after you’ve verified the connection.
Desktop: test with the system proxy
Find “System proxy” at the bottom of the v2rayN window or in the tray menu. Options typically include “Set system proxy” and “Clear system proxy.” For your first test, use a browser that follows the system proxy, and select “Set system proxy” after choosing an active server in the next step. If your browser has its own proxy settings or an extension that controls network traffic, switch to a browser that follows system settings to avoid conflicts with the client.
You don’t need to enable TUN or switch routing to global mode for now. The system proxy is a good way to test with a browser first. If the browser works as expected but a desktop app doesn’t, the app may not use the system proxy. Check whether it has its own proxy settings, then decide whether to learn about TUN mode. Don’t enable both traffic entry methods during your first test.
Android: test with VPN mode
Check the operating mode in v2rayNG settings and select “VPN mode” if your version offers it. This mode uses the system VPN interface to capture app traffic. If you’ve set up per-app proxying, make sure your test app isn’t excluded. If the list allows only selected apps, add your test app. If another VPN is running, make sure you can pause it before starting v2rayNG. Don’t change a VPN managed by your organization or device policy just to run a test. For the difference between a local proxy, the VPN interface, and outbound rules, see the glossary.
Connect to a server
Return to the group you just imported and select a server to test. For your first connection, keep the configuration and network unchanged so you can trace any issues in the logs. A speed test reflects only a specific test request; it doesn’t guarantee that your target app can connect. You can verify the connection with a known-working configuration even if you haven’t run a speed test.
Desktop: set an active server and enable the system proxy
In the v2rayN server list, select an entry and use the right-click menu to set it as the active server. Simply selecting a row only moves the focus; check that the active indicator or status bar shows the server you chose. Then check the main window’s runtime information to make sure the core started successfully. If the log reports that a local port is already in use, check whether another client of the same type is running. Don’t send browser traffic through the system proxy if the core hasn’t started.
Once the local proxy is running, select “Set system proxy” from the tray or main window menu, then open your test browser. If the browser can’t load any pages, select “Clear system proxy” to restore the connection method you used before testing, then check the client’s startup log. If your device already uses a work or school system proxy, note its settings before testing and restore them afterward. Clearing the client’s settings won’t restore the original configuration.
Android: select a configuration and approve the system connection request
Select a server in the v2rayNG main list and make sure it’s highlighted, then tap the Connect button in the lower-right corner. The first time you use VPN mode, Android displays a connection request. Confirm that v2rayNG is the app named in the prompt, then allow the connection. A connected button or VPN status icon means the local service has started or the VPN interface is active; it doesn’t confirm that the remote server is reachable.
If the button quickly returns to the disconnected state, check the app log right away. First determine whether Android denied permission, the local service failed to start, or the remote server didn’t respond. If the connection is running normally, leave it on and continue. Switch to another known-working server only after identifying where the current configuration failed, and make sure the new selection takes effect.
Verify the connection
First test a request that should use the proxy, then test the app you actually want to use. In the browser you chose earlier, open an accessible page that should be proxied under your current rules, or use a trusted IP address lookup page for comparison. Make a fresh request rather than relying on a page that’s already open. Check the client log for the same time period. If it shows the request destination or outbound tag, confirm that it matches your test. Seeing the core start or a VPN icon doesn’t prove that the request used the proxy outbound.
Next, compare results with the proxy turned off. On desktop, clear the system proxy you enabled for the test; on Android, tap the Connect button to disconnect the VPN. Keep the same network and browser, request the same page again, and compare the result or exit IP. Then reconnect if needed. If the exit IP hasn’t changed, first check whether the rules sent the test address directly. Conversely, a changed exit IP only shows that the route for that request changed; it doesn’t mean every app uses the same route.
Browser and target app behave differently
If the browser works but the target app still has problems, first check whether the app uses the system proxy on desktop, or review the per-app proxy list and exclusions on Android. After making changes, close and reopen the target app and send a fresh request; some apps reuse existing connections. If both fail and the log shows that requests reached the client, use the earliest error in the log to guide your next check. DNS resolution failures and remote connection timeouts are different issues, so don’t change DNS, servers, and routing all at once.
When both the browser and target app behave as expected, you can keep this configuration. Note the subscription group, active server, and proxy mode you used. If a problem comes up later, check each stage in order: configuration in the list → local service running → request reaching the client → expected outbound selected. If only certain domains behave differently than expected, check the routing rule order. If the log points to a resolution failure, check DNS settings. When sharing logs, include only relevant errors and remove subscription URLs, server credentials, and other sensitive information.