v2rayN Interface Guide: Servers, Subscriptions, Logs & Settings

At a glance

This guide is for users who have opened v2rayN but aren't sure how selecting a node differs from making it active. Follow the main window from server list to subscription groups, system proxy, logs, and settings, then use the connection checks at the end. Menu labels are based on common Chinese names in the Windows desktop interface. Locations may differ across versions and desktop or WPF builds, so follow the labels shown in your own version.

Server list: selecting a row doesn’t activate a node

The server list in the middle of the main window stores your connection profiles. Rows typically show a remark, protocol, address, port, subscription group, and latency or speed after a test. VMess and VLESS are connection protocols; v2rayN is the client that manages profiles and launches a core. They’re different parts of the setup. A node appearing in the list only means its profile is saved—not that the server is online.

Clicking a row usually just selects it so you can use its context menu. To connect, right-click the row, choose “Set as active server,” and confirm the active indicator has moved to the intended node. Some versions let you switch with a double-click, but row numbers and highlight colors aren’t reliable across every version.

Interface item	What it means	What to watch for
Remark and address	The remark helps identify a profile; the address determines where it connects	Similar names don’t mean identical connection settings. Check the subscription group before editing.
Port	The port the remote server listens on, such as 443	Don’t substitute your local proxy port. Port 443 alone doesn’t mean TLS is enabled.
Real connection latency test	How long it takes to reach the test target through the node	Results depend on the test address and current network conditions; they aren’t a direct measure of download speed.
Edit and delete	Change or remove a node profile saved locally	A later subscription update may recreate the node. Don’t rely on a temporary edit as a permanent setting.

Start by testing a small number of nodes with a real connection test, then set an active server once results are in. If a row shows -1 or a timeout, it means this test didn’t succeed—not necessarily that the account is invalid. Check the network and test target used, then look for connection errors in the logs before switching nodes.

Subscription groups: organize sources and switch views

Subscription groups keep nodes from different sources separate. Switching groups in the main window usually changes only the list on display; it doesn’t automatically change the server in use. If you’ve switched groups but your exit IP hasn’t changed, check the active-server indicator first instead of repeatedly updating the subscription.

Open group settings

From the main menu, choose “Subscription Group” → “Subscription Group Settings.” If your version has a group management button, it opens the same window.
Save the address

Add a group, enter a remark that identifies its source, paste the full subscription URL into the address field, and save. Don’t paste a webpage title or the provider’s homepage address.
Update subscriptions

Return to the “Subscription Group” menu and choose “Update All Subscriptions (without proxy).” If your network can’t reach the subscription URL and you already have a working node, try the corresponding update option “through proxy.”
Verify the source

Switch to the new group and confirm its nodes and remarks appear. Test a node, then set it as the active server. An “Update complete” message alone doesn’t mean the proxy is working.

System proxy and routing: how traffic enters and exits

The active server selects the node profile used for proxy connections. The system proxy determines whether apps that follow system settings send requests to the local proxy, while routing rules decide whether those requests go direct or through the proxy. Check all three separately. Selecting a node doesn’t mean an app is using it, and enabling the system proxy won’t affect every program.

What to check for each connection method

System proxy

From “System Proxy” at the bottom of the main window or in the tray menu, choose “Auto-configure system proxy.”
A good starting point for testing a browser that follows system proxy settings.
If the browser has its own proxy extension, check whether it overrides system settings.

TUN mode

Routes traffic through a virtual network interface, useful when you need to capture a wider range of traffic.
It involves permissions, a virtual network adapter, and routing. The system proxy toggle alone won’t tell you whether it’s working.
For initial troubleshooting, establish a baseline with the system proxy, then check TUN separately.

Get one connection method working before adding another. Changing the system proxy, TUN, and routing at the same time makes it harder to pinpoint the cause of a problem.

Routing mode names can vary by version or preset. Don’t rely on a dropdown’s position; confirm which rules are selected. To test split routing, visit one destination expected to go direct and another expected to use the proxy, then check the route labels in the access logs. See the configuration reference for detailed rules; you don’t need to write a config by hand just to understand the main window.

Log panel: tell startup failures from request failures

The log panel at the bottom shows client activity and core runtime information. The client updates subscriptions, saves settings, and starts the process; the core handles actual network connections. So “subscription updated successfully” and “proxy request succeeded” are different events. Note what you were doing and when—updating a subscription, switching nodes, or opening a webpage—then check the logs from that time.

Core exits immediately after startup: Find the first specific error during startup. Check config parsing, listener failures, and file paths before changing the remote node password.
Core is running, but webpages time out: Look for connection errors near the target address, then check the active node, remote port, and routing result.
Only one website fails: Compare its log entries with those for a working site, then check DNS, routing, or TLS settings instead of resetting everything at once.
No access logs appear: Check the log level and display toggle first. The app may also be bypassing the local proxy, so a quiet panel doesn’t prove the connection is working.

listen tcp 127.0.0.1:10808: bind: address already in use
dial tcp 203.0.113.10:443: i/o timeout
x509: certificate has expired or is not yet valid

The errors above are illustrative examples for identifying issue types, not logs from a real device. Wording varies by core and operating system. The first indicates that a local port is already in use; check whether the client is running twice. The second indicates a timeout connecting to a remote server; its example address is from a documentation-only network range. The third points to a certificate validity or system clock issue. Disabling certificate verification is not a standard fix.

The log level is usually under “Settings” → “Parameters” in the core-related section. Increase detail temporarily for diagnosis, then restore the usual level to avoid writing excessive logs. When sharing logs, keep the error type, timestamp, and relevant port; remove identity details and subscription tokens first.

Settings: check listening ports and local access first

In “Settings” → “Parameters,” start by checking local listening ports, whether LAN connections are allowed, the log level, and core options. Tabs may be called Basic Settings or Core Settings, depending on the interface. The Save button may or may not restart the core immediately. Return to the main window after making changes to confirm the new settings loaded; restart the client if needed.

For local use only

Listening address: 127.0.0.1
Example port: 10808
Allow LAN connections: Off
App connection: Set up HTTP or SOCKS according to the inbound type

The port is an example, not a fixed default for every version. Check Parameters and the startup logs.

For use by devices on your LAN

Listening scope: LAN connections must be allowed
Client address: Enter the LAN IP address of the computer running v2rayN
Port: Use the actual open proxy inbound port
Firewall scope: Allow access only on trusted networks where it’s needed

Other devices can’t connect to this computer using 127.0.0.1. Before enabling sharing, check the access scope and available authentication.

The same port number doesn’t mean the same protocol. Some versions use a mixed inbound; others listen separately for HTTP and SOCKS. Don’t copy adjacent port numbers from an older guide without checking. The three numbers below refer to different places, so first identify which end the error comes from.

10808

Example local proxy listening port

443

Example remote server port

127.0.0.1

Loopback address for this device only

Don’t switch core types just to get a “newer” version. A client’s ability to save a protocol profile doesn’t mean every core can use the same fields. Check core support especially for VLESS, Reality, or specific transport settings. After importing a subscription, start with the configuration supported by your client and adjust settings one at a time if a specific error appears.

Common questions and connection checks

Why does my browser still use the old exit IP after I select a node?

Right-click the node and choose “Set as active server,” then confirm the active indicator. Next, check “System Proxy” → “Auto-configure system proxy.” If the browser has its own proxy settings, set it to follow system settings and revisit an exit IP lookup page.

Why is the old node still in use after switching subscription groups?

Switching groups only filters the list. Open the target group, select a different node, and set it as the active server. If there are no usable nodes, update the subscription from the “Subscription Group” menu and check the update logs.

Why can’t I open websites even though the speed test shows a result?

A real connection test checks only its test target. First make sure the browser is using the local proxy, then check routing and logs for the site that fails. A latency result alone can’t rule out bandwidth, reachability, or DNS issues.

Why is the program still running after I close the main window?

The close action may be set to minimize the window to the system tray. Look for the v2rayN icon in the taskbar notification area. To stop the client, exit from the tray menu and check that the system proxy has been cleared.

After setup, verify everything in this order: confirm the subscription group contains nodes, select a node that passed a real connection test and set it as active, enable one connection method, then check access in a browser and verify the exit IP. Finally, review the log panel for that request. Change one thing at a time to identify whether the node, system proxy, or routing made the difference.

The server list lets you select a profile; it doesn’t prove the connection works.
Subscription groups organize sources; a successful update doesn’t mean network requests are succeeding.
Logs provide troubleshooting evidence; settings control local behavior.