v2rayN Setup Guide

Step 1: Import a Subscription

First, identify what you have. A subscription URL, usually provided by your service, lets the client retrieve a set of server configurations. A share link describes a single server and commonly starts with vmess://, vless://, trojan://, or ss://. Use the right import option for each type. Don’t paste a subscription URL into a single-server address field or remove parameters from the end of the URL.

Save the URL in a Subscription Group

Open v2rayN, click Subscription Group in the top menu, then open Subscription Group Settings or the equivalent management window. Add a group and enter a name you’ll recognize, such as “Everyday use,” in the remarks field. Paste the full subscription URL into the address field. Check for spaces, line breaks, or copied instructions at either end, then save. The group name is for local reference only and doesn’t change the server configuration.

Return to the main window and update the group you just added from the Subscription Group menu. If you haven’t connected yet and the menu offers an option to update without using a proxy, try that first. Use the proxy option only if the subscription URL requires an existing proxy and that connection is working. After the update, server entries should appear in the list. If another group is selected, switch to the new one to see them.

In v2rayNG, open Subscription Group Settings from the sidebar, tap Add, and enter the remarks and subscription URL. Save, return to the main screen, and use the menu to update the subscription. Once server cards appear, continue to mode selection. Saving a URL alone doesn’t confirm that its contents were retrieved; check the update result and the entries in the list.

Have a Share Link? Import It from the Clipboard

Copy the complete share link. In v2rayN, open the Server menu at the top and select Import share links from clipboard. After importing, check that the list shows the server type, remarks, and port. In v2rayNG, choose Import from clipboard from the Add menu. This method is for individual server configurations. Subscription updates won’t maintain entries imported this way, so follow the provider’s instructions if you need to replace one.

If an update fails, check whether the URL has expired or needs to be retrieved again, and make sure your device’s date and time are correct. If the update succeeds but no entries appear, check the selected group, subscription limits, and service expiration. If the URL opens a webpage instead of returning a configuration, copy the subscription link again from the provider’s site; don’t try to import a login page. For more details, see installation, setup, and troubleshooting help.

Once the server list is ready, don’t keep running speed tests. First, make sure you understand how apps send traffic to the client; otherwise, a working server may still leave your browser connecting directly.

Step 2: Choose a Proxy Mode

Two v2rayN settings are easy to confuse: System Proxy and Routing. System Proxy changes the operating system’s proxy entry point, directing apps that follow it to a local listening port. Routing determines whether traffic is sent direct, proxied, or blocked after it enters the core. These are separate controls. For an initial setup, try Auto Configure System Proxy with Bypass Mainland China, and leave TUN disabled for now.

Set the App’s Proxy Entry Point, Then Choose a Route

At the bottom of the v2rayN main window, find System Proxy and select Auto Configure System Proxy. This is the right starting point if you want your browser to follow the system settings. If you have a browser proxy extension installed, set it to use the system proxy or temporarily disable its proxy controls so it doesn’t keep pointing to an old port. Some apps have their own network settings and won’t use the system proxy automatically.

Next, open the Routing selector at the bottom and choose Bypass Mainland China. This preset typically sends traffic related to mainland China directly and handles other traffic according to its rules. The actual behavior depends on the current rule set and order. Global generally sends traffic that enters the core through the proxy; use it for brief comparison tests. Direct primarily uses your local network. Global routing does not mean every app on your device is covered.

Check the Port Instead of Copying a Number from Another Guide

Open Parameter Settings from the Settings menu at the top and check the local listening address and port. The interface may show 10808 or a different value, depending on the version and your changes; use the settings on your device. If you configure an app’s proxy manually, the address is usually 127.0.0.1, and the port and proxy type must match the client. For initial setup on a single device, leave LAN connections disabled.

v2rayNG usually connects through the system VPN interface; you don’t need to look for the desktop Auto Configure System Proxy menu. Open its routing settings and choose a preset that suits your needs. For the first setup, leave DNS and other advanced options unchanged. The system will prompt you to establish the interface when you tap Connect in the next step. The desktop system proxy and Android VPN are different entry points; you still need to verify that the server works.

Once you’ve finished this step, note the routing mode you chose and make sure no other network tool is also changing the system proxy. The complete guide covers rule order, domain policies, and when to use TUN. You don’t need to adjust these settings before your first connection.

Step 3: Activate a Server Connection

Return to the v2rayN server list and choose an entry from a known source that hasn’t expired. Right-click it and select Set as active server, or the equivalent option in your version. Don’t confuse a highlighted row with the active server indicator: clicking a row may only select it for editing and may not switch your current outbound connection. After switching, check the active indicator and the runtime information in the window.

Confirm the Active Server and Core Startup

v2rayN usually starts or reloads the core after you set an active server; there may not be a prominent Connect button. If the system proxy is enabled, apps that follow the system settings can now send requests to the local port. Check the main window’s log area or open the logs to see whether the latest startup produced errors. A minimized window or tray icon doesn’t mean the app has exited—or that the connection has been verified.

First, look for log messages about a port in use, configuration parsing failures, or the core failing to start. If there’s a port conflict, close duplicate client instances or the app using that port and try again. If you do need to change the port, update any apps you configured manually. For protocol or field incompatibilities, check which core the server requires and which one you selected. Don’t cycle through advanced settings at random.

In v2rayNG, tap a server card and check that the selection indicator is on the intended entry, then tap Connect on the main screen. The first time you connect, the system will ask to establish a VPN connection; approve the request and check the connection status in the client. If another connection is using the same type of interface, stop it before testing. A connection icon in the status bar confirms only that the interface is up, not that remote sites are reachable.

Use Speed Tests as a Guide, Not a Guarantee

If the list has several servers, use the client’s test feature to narrow them down, then set one as the active server. Test results mean different things: a TCP test checks whether a connection can be made to the target port; a real connection test more closely reflects an actual proxy request, but still reports only the result for its test target. A result with a number doesn’t guarantee that every website will open, and a timeout may be caused by the test target.

If a test times out, try another entry from the same subscription, changing only the server. If the second entry works, the issue is more likely with the original server or its route. If all entries fail, check your local network, device time, subscription validity, and any errors shared across the logs. Recording the step where the error occurs is more useful than repeatedly uninstalling and reinstalling the client.

Step 4: Test That the Connection Works

Open a browser that you know follows the system proxy, start a new tab, and visit a familiar HTTPS page that should be reachable. Don’t just refresh an existing page: cached content, existing connections, and background tabs can preserve the previous state. First check whether the page loads, then use the client logs to see whether the request entered the core and which route it took.

Cross-Check Access and Logs

With Bypass Mainland China routing, some pages connecting directly is expected and doesn’t mean the proxy isn’t working. Choose a site that should use the proxy under your current rules and make a new request. Check the logs for the corresponding domain or connection; what appears depends on the log level and version. If you temporarily increase the log detail for troubleshooting, restore the original setting afterward. Remove subscription, address, and account information before sharing logs.

You can also check your outbound IP on a reputable lookup site, but one lookup shows only the route used for that request. After switching servers, make a new request to compare. You don’t need to see a different IP every time, and a location label alone doesn’t tell you how good the connection is. Multiple servers may share an outbound IP, and lookup services can have outdated location data.

If the results are unclear, temporarily switch routing to Global. Keep the same server and browser, then try the same site again. If Global works but your original route doesn’t, check rule matching and DNS first. If both modes fail, revisit the core logs and app entry point. Restore your regular routing after the test; don’t leave a temporary comparison setting in place as your everyday configuration.

Troubleshoot One Failure Point at a Time

If your browser says the local proxy connection was refused, first confirm the client is still running, the local port is listening, and the browser isn’t pointed at an old port. If the request appears in the logs but then times out remotely, try another server or check its configuration. If only one app fails, check its own proxy settings. If only a few domains fail, check routing, DNS, and the destination site’s status.

v2rayNG users should also verify the connection by opening a webpage. If the system connection icon appears but pages won’t load, check the active server and client logs, then review routing. Before you get a first successful connection, avoid adding multiple DNS configurations, app-level routing rules, or other traffic interception settings. For more troubleshooting steps, see the Help Center. To understand what each setting does, read the Complete Guide to V2Ray, from Basics to Advanced Setup.

Disconnect After Testing and Prepare for Next Time

When you’re done on desktop, select Clear System Proxy in v2rayN before quitting. The app may restore the settings on a normal exit, but check that your browser can connect directly as expected. If webpages stop loading after you force-quit the process, check whether the system network settings still point to the local proxy port. With the local listener stopped, the browser can no longer connect to it.

On Android, tap Stop in v2rayNG to disconnect. Next time, check that the subscription is still valid and the correct server is active, then connect; you don’t need to import it again. Before routine subscription updates, keep track of where manually added entries came from and check that the active server is still in the list afterward. You’ve now checked all four parts: subscription, app entry point, core operation, and actual access. You can build on this setup with more detailed routing and TUN settings.