v2rayN Setup Guide: From Subscription Import to Connection Verification

Import the Subscription and Update the Server List

First, copy the subscription URL from the provider’s management page. Do not remove parameters manually or share the link on a public page. A complete subscription URL may contain a long path and query parameters; copying only the visible portion can make updates fail. If the clipboard adds spaces before or after the URL, check both ends after pasting it into the client and remove any extra whitespace.

v2rayN Desktop Instructions

Open the v2rayN main window, find the “Subscription Groups” or “Subscription” entry in the top menu, and open the subscription group settings. Choose “Add” or “New Subscription Group,” enter an easy-to-recognize name such as “Daily Subscription,” and paste the complete URL into the subscription URL field. The name is only used for local identification and does not change the server configuration.

After saving the group, return to the main window, open the “Subscription Groups” menu again, and choose “Update All Subscriptions,” or update the newly created group individually. During the update, the status bar or log area shows the request and parsing process. When it finishes, the server list should contain multiple configurations, usually with columns for remarks, address, port, protocol, and transport. Once the list appears, do not repeat the update several times; proceed to mode selection.

v2rayNG Android Instructions

Open v2rayNG and go to “Subscription Group Settings” from the top-right menu on the main screen. Tap the add button, enter a group name, paste the subscription URL, make sure the group is enabled, and save it. Return to the main screen and choose “Update Subscription” from the menu. When the update finishes, the server configurations appear in the main list. If the screen is still empty, check that the displayed group is the one you just added.

Some subscriptions create multiple groups by region or purpose. For first-time use, keep the default display settings and skip keyword filtering. An incorrect filter can hide every successfully parsed server, making the subscription look empty. If you need to manage multiple URLs, read Subscription Groups and Server Filtering after the basic connection works.

Once the server list appears, step one is complete. The client has saved the server configurations, but it has not yet determined which connections should use the proxy, and it has not started forwarding traffic. Choose a proxy mode next so an unsuitable mode does not make a working setup appear broken.

Choose Rule-Based Routing or Global Proxy Mode

The proxy mode determines which requests are handled by the current server. Common options include rule-based routing, global proxy, and direct connection. They may appear as “Rules,” “Global,” and “Direct,” or under a “Routing” or “Preset Rules” menu. For first-time setup, rule-based routing is recommended: common local sites stay direct while other requests follow the rules into the proxy, balancing access and local connectivity for everyday use.

Rule-Based Routing for Everyday Use

In v2rayN, open the “Routing” menu and choose a preset whose meaning is based on rules or bypassing local addresses. Then check the routing status at the bottom of the window and confirm it is not set to “Global Direct.” Rules are usually matched from top to bottom. For example, geoip:private handles private network addresses, while geosite:cn handles the corresponding domain set; unmatched requests are sent to the proxy outbound. No rule editing is needed for first-time use—choose one of the client’s preset routing schemes.

In v2rayNG, open Settings or Routing Settings, choose a preset rules mode, and return to the main screen. Android saves routing settings separately from the connect button, so you still need to return to the main screen and start the connection after changing the mode. If the app also offers “Per-App Proxy,” keep its default setting during initial setup; it limits specific apps and is not required for a basic connection.

Use Global Proxy for Short Tests

Global proxy sends all applicable requests through the current server. It is useful for checking whether a webpage problem is caused by routing rules and for briefly testing the connection path. If a target is unreachable in rule mode but works in global mode, the server is generally reachable; check domain rules, IP rules, or DNS resolution instead of repeatedly replacing the subscription.

Global mode does not mean the client has taken over every connection on the device. v2rayN on desktop usually also requires “System Proxy” to be enabled so browsers and apps that follow the operating system proxy settings use the client. For programs that ignore system proxy settings, consider TUN mode. TUN involves a virtual network interface, permissions, and DNS behavior, so leave it disabled during basic setup and see the TUN Mode section for details.

Confirm the System Proxy Status

v2rayN users can open the client menu from the system tray and choose “Auto Configure System Proxy” or a similarly named enable option. After enabling it, the tray status and the bottom of the main window usually indicate that the system proxy is on. If the menu also offers “Clear System Proxy,” do not choose it before connecting. Before exiting the client, restore the system proxy state so other apps do not keep pointing to a local port that is no longer running after the next startup.

When v2rayNG starts a connection, it requests permission to establish a system VPN connection. A system confirmation dialog appears the first time; after approval, a connection indicator appears in the status bar. This creates the traffic entry point on the device, while the server actually used is still determined by the active configuration selected in the main list.

After choosing a mode, the client knows how to handle traffic but still needs an active server. Next, select a configuration from the subscription list and watch the core startup status. This is a basic connection check; do not treat latency alone as the deciding factor.

Select a Server and Start the Connection

Each row in the server list represents one connection configuration. A subscription may include protocols such as VMess, VLESS, Trojan, or Shadowsocks, and the client automatically uses the matching capabilities. For the first connection, do not manually change the address, port, transport, or TLS settings. These fields are generated by the subscription, and changing one can break the original combination.

Set an Active Server in v2rayN

Return to the v2rayN main window and click a row in the server list. Use the context menu to choose “Set as Active Server,” or use the corresponding shortcut shown by the client. The active row usually changes color, icon, or selection state, and the bottom of the window shows the current server remark. Confirm that the active server belongs to the subscription group you just updated, rather than an outdated configuration added manually in the past.

After setting the server, keep the client running and confirm that the system proxy from the previous step is enabled. v2rayN starts the local core and loads the current configuration. Open the log area; a normal startup may show configuration loading and the creation of a local listening port. If the same error repeats rapidly, the core is not running reliably. Read the error first instead of repeatedly toggling the system proxy.

Start the Connection in v2rayNG

Tap the target configuration in the v2rayNG main list to make it the selected item, then tap the connect button on the main screen. The first connection may display a system network permission prompt. Approve it, and the button state will change while the main screen shows a connected or running status. The app can remain in the background; it does not need to stay open on the main screen.

If the connection immediately returns to a disconnected state, reopen v2rayNG and check the error message. Common causes include an expired server configuration, a significant device time difference, an incomplete subscription update, or another VPN-type connection occupying the network interface. After addressing the cause, select the server again and start the connection once more.

How to Choose Your First Server

If the subscription offers multiple regions or groups, start with a nearby server whose plan or multiplier is suitable for everyday use. The client’s latency test can help eliminate configurations that cannot establish a connection at all, but it reflects a handshake at one moment and does not represent sustained download speed. For testing methods, multipliers, and region selection, see How to Choose V2Ray Nodes on the blog.

Do not change the server, mode, DNS, and TUN settings all at once. A safer sequence is to keep rule mode unchanged, switch the active server once, and then verify a webpage. If it fails, try another configuration from the same subscription. Only after both fail should you check the subscription and system proxy. Changing one condition at a time makes it easier to identify whether the issue is with the server, client, or local network.

A connect button showing a running state only means the client has started; it does not prove that every app is using the proxy as expected. The final step checks webpage access, client logs, and mode status together to confirm the configuration through an actual request.

Verify the Proxy and Complete Basic Troubleshooting

Close any test webpage tabs you already opened, then create a new browser window. This reduces the effect of old connections, cached data, and existing DNS results. Visit a familiar site that normally works directly, then visit the target site that requires the current proxy path. In rule-based routing mode, if both types of pages load normally, the basic routing and connection are likely working.

Check the Client Log

Watch the client log while opening the webpage. In v2rayN, check the log area at the bottom of the main window or open the log menu to view new connections; in v2rayNG, open the log page from the menu. When you refresh a page, new domains, target addresses, inbound, and outbound records indicate that the request reached the client. In the log, direct usually means the rule selected a direct connection, while proxy usually means the request entered the proxy outbound.

If the log shows no new entries at all, the problem is probably before the client. On desktop, first confirm that the system proxy is still enabled, then check whether the browser has its own proxy setting or uses a network mode that ignores system proxy settings. On Android, confirm that the system connection is still present and check whether only selected apps are allowed through the proxy. Restore the per-app scope to its default and test again.

When a Webpage Will Not Load, Check in This Order

First, check the active server. Confirm that the current server is still selected, the core has not exited, and try another configuration from the same subscription. Second, check the mode. If only a specific site fails in rule mode, briefly switch to global proxy and try again. If global mode works, inspect the routing rules instead of changing server parameters.

Third, check the subscription. Run one more subscription update and look for an expired URL, request failure, or empty parse result. After updating, remember to select the active server again, because some clients may revert to a default item when refreshing the list. Fourth, check the system time. Protocol handshakes and certificate validation depend on accurate time; an incorrect date, time zone, or automatic time setting can cause connection failures.

Fifth, check the local network. Switch networks and reconnect, or temporarily disable other network tools that may also control the system proxy. If the client log shows that the request arrived but connections keep timing out, try another server. If multiple servers behave the same way, see the subscription, DNS, permissions, and system proxy entries in Troubleshooting FAQ.

Everyday Actions After Verification

Once basic verification passes, remember three everyday entry points: update the subscription, switch the active server, and turn the connection on or off. Updating retrieves configurations changed by the provider; switching servers handles a temporarily unavailable configuration. When disconnecting, v2rayN on desktop should also clear the system proxy so the browser does not keep sending requests to a stopped local listening port.

If you only need basic webpage access, setup is complete here. To route more apps through the proxy, assign outbounds by domain, optimize DNS resolution, or filter multiple subscriptions, continue to the Advanced Configuration Guide. After adding each advanced setting, repeat the webpage and log checks in this section so you can identify which rule changed the connection result.