For anyone who has opened v2rayN but isn't sure how selecting a server differs from setting it as active or enabling the system proxy. Follow the server list, subscription groups, proxy status, logs, and settings to trace a request from its configuration source to its destination—and find the right place to troubleshoot.
The four main areas of the v2rayN window
v2rayN is a desktop client that manages configurations; the core process handles connections. Seeing servers in the window doesn't mean the core has started successfully, and a running core doesn't mean your browser is using it. Keep configuration, runtime, and traffic routing separate to troubleshoot more effectively.
Control locations and labels vary between versions, including the desktop and classic editions. This guide uses the common Chinese-language interface on Windows. Menu names help you locate features; if a status-bar button is elsewhere, look for the same action in the tray menu. You don't need to switch versions just to match the screenshots.
- Top menu: Find options such as Server, Subscription Groups, and Settings to import, update, and adjust configurations.
- Groups and server list: Choose which configurations appear and which one is set as the active server.
- Status area: Check local listeners, system proxy, routing mode, and runtime status. Available fields vary by version.
- Logs or information panel: Check messages about core startup, connection failures, and configuration parsing—not a leaderboard of connection speeds.
Server list: check the columns and active indicator
Each row in the server list usually represents an outbound configuration, not an established connection. Clicking a row only selects it. To change the server in use, right-click the entry and choose “Set as active server.” Confirm that the active indicator changes, then check the logs for a configuration reload. Don't rely on row highlighting alone to confirm the switch.
| Common field | What it means | What to check |
|---|---|---|
| Alias or remarks | A display name that helps identify the entry | The name isn't a protocol parameter and doesn't confirm the server's actual location. |
| Address and port | The remote server's connection endpoint | This is not the local proxy port on your computer. |
| Type or protocol | For example, VMess or VLESS | The protocol, transport, and TLS settings must match the server. |
| Transport and security | For example, WebSocket, gRPC, or TLS | Not every version displays all details in the list. Open the edit window if needed. |
| Subscription group | The management group that contains the configuration | Used to filter and update entries; it doesn't enable automatic load balancing. |
| Latency and speed | Results from a particular test | Check the test type, time, and units before comparing values. |
A TCP connection test mainly checks whether the target port is reachable. A real-connection test also involves a proxy request and a test URL, so the two results aren't interchangeable. A blank latency field usually means the entry hasn't been tested yet. If a test times out, determine whether the target, server, or local core is unreachable. Speed results also depend on the test URL, network route, and current load; they aren't a guarantee of long-term performance.
Subscription groups: manage the source before updating
Subscription groups store configuration sources and update options. Creating a group doesn't fetch servers, and switching groups only filters the list. If the list suddenly looks empty, check the selected group and search filters before assuming the configurations are gone. Subscription URLs often contain access credentials, so don't include them in public screenshots or log attachments.
-
Open group settings
Go to Subscription Groups → Subscription Group Settings, then use the add option to create a group. Depending on the version, it may be labeled “Add” or shown as a plus sign.
-
Enter the subscription source
Enter a recognizable source name in Remarks and paste the full subscription URL into the address field. Check for leading or trailing spaces, then save.
-
Update the subscription
Return to the main window and choose Subscription Groups → Update current subscription (without proxy). If the source is only reachable through an existing proxy, choose the corresponding update-through-proxy option instead.
-
Check the import results
Switch to the new group and check the number of entries, remarks, and protocol types. Then set one entry as the active server. A successful update message doesn't mean every server is reachable.
Updating through a proxy depends on a working proxy connection. If no server is working yet, choosing this option can create a dependency loop. Conversely, repeatedly updating without a proxy won't help if the source can't be reached directly. First confirm the source URL is valid, then choose a retrieval method that can actually reach it.
System proxy, routing, and local ports
The system proxy determines whether an app sends requests to the client; routing determines which outbound path the client uses for those requests. So setting the route to global proxy mode won't automatically route traffic from an app that ignores the system proxy. TUN is a separate way to capture traffic, not the same as the system proxy toggle in the tray. You can leave it off while getting familiar with the interface.
Set system proxy
RecommendedRoutes traffic from apps that follow Windows system proxy settings through the local proxy endpoint. With an active server selected, this is a good first way to test whether your browser can connect.
Best for: First connection tests and desktop apps that use the system proxy.
Clear system proxy
Removes the system proxy setting; it doesn't delete servers or necessarily stop the core. Apps with a manually configured local proxy address may still connect through the core.
Best for: Temporarily restoring direct system connections or letting specific apps manage their own proxy settings.
Do not change system proxy
The client leaves the system proxy setting unchanged; it doesn't actively turn the proxy off. If the system already points to a local port, that setting may remain in place.
Best for: Users who need to keep their existing system proxy settings.
These three port numbers are examples to illustrate how the ports relate—not fixed defaults for every version or speed-test results. Before entering values, check the local listener settings under Settings → Settings and the startup logs. Some versions use a mixed listener that accepts different proxy protocols on a single port.
For example, when an app uses 127.0.0.1:10808, it connects to a listener on your computer—not to the remote 443 port in the server list. Also make sure the listener supports the HTTP or SOCKS protocol selected in the app. While troubleshooting, keep access limited to this computer; don't enable LAN access just to fix a browser issue.
Log panel: start with the first error
The information or log area at the bottom shows core activity. If it's collapsed, expand it first. Versions may separate application logs from core logs: subscription download failures usually relate to client management, while remote handshake failures are more likely to appear in core output. A high log level can hide routine connection entries, so an absence of new logs alone doesn't prove that no traffic reached the client.
- Reproduce the issue: Note the time, open a specific page, and try once to reduce background traffic.
- Check startup first: Confirm the core started and the local listener is active. Look for configuration parsing errors or port conflicts.
- Then check the connection: Find the destination address, outbound tag, and surrounding errors at the same time. Determine whether the failure occurred locally, during the remote connection, or at the TLS stage.
- Finally, review recent changes: Match the error to any recent server, routing, DNS, or listener changes. Revert one change at a time.
| Log term | Common meaning | Next step |
|---|---|---|
address already in use | Local listener address or port is already in use | Check whether the client is running more than once or another process is using the same port. |
connection refused | A connection to a target was refused | Check the destination address first to distinguish a local listener that isn't running from a remote service that isn't listening. |
timeout | A connection or read operation timed out | Use the surrounding log entries to determine whether the timeout affected DNS, the remote connection, or the test request. |
certificate | May involve a certificate or TLS verification error | Check the system time, server name, and server-side settings. Don't simply disable verification. |
What the tray menu and settings control
The v2rayN icon in the Windows notification area is handy for frequent actions such as restoring the main window, changing system proxy status, choosing a route, and exiting. Closing the window may only hide it, depending on your settings. To confirm that the client has exited, check the tray icon and whether its process is still running—not just whether a window appears on the taskbar.
For persistent changes, open Settings → Settings in the main window. Don't confuse the server edit window with the global settings window: the former changes a specific remote configuration; the latter affects shared settings such as local listeners and runtime behavior. Some versions have a separate Core Type Settings option; use the entry available in your version.
- Change servers: Set a different server as active in the server list; there's no need to change local listener ports.
- Change the proxy endpoint: In Settings, check the listener port, listening address, and LAN access option. After saving, check whether the core reloads successfully.
- Change where traffic goes: Check the current routing mode in the main window or tray, then review the specific rules in routing settings.
- Change the core: First confirm that it supports the server's protocol and transport settings. After switching, check the startup logs again; updating the core doesn't replace checking the configuration.
Common questions about the main window
Why am I still using the old route after clicking a server?
Selecting a row and setting it as the active server are separate actions. Right-click the target entry and choose “Set as active server,” then check the active indicator and the log reload time. Existing long-lived connections may not switch immediately, so start a new request to verify.
The list is empty after an update. Was my subscription deleted?
Clear the list's search filter, switch to the target group or all groups, and check the update message. If the returned content couldn't be parsed, check that the source is valid and reachable. Don't delete the group as a first step, or you may lose its existing settings.
Why won't my browser open sites even though latency looks fine?
A successful latency test only confirms that the specific test passed. First check the system proxy status in the tray, then confirm the browser uses the system proxy and the local listener port matches. Check the logs for new errors while you try to open the page.
Web pages stopped working after I exited. What should I check first?
In Windows, go to Settings → Network & Internet → Proxy and check whether the system still points to a local port whose listener has stopped. You can also restart the client, choose Clear system proxy, and then exit normally. There's no need to start by changing server settings.
For routine checks, follow the same order: confirm the subscription source, select an active server, check the system proxy and routing, make one request, then read the corresponding logs. Identify the layer causing the issue before changing settings. This makes it easier to preserve useful clues than changing ports, DNS, and core type all at once.