The system proxy determines whether apps that follow system settings send requests to v2rayN; routing rules determine whether those requests go through a node or connect directly. Aimed at desktop users who have already imported nodes, this guide uses v2rayN 7.x on Windows to cover everyday traffic routing, temporary checks, and restoring direct connections. It also compares browser and command-line traffic paths for the same destination.
The system proxy controls the entry point; routing rules control the exit
Select “Set system proxy automatically” from the tray menu and v2rayN will configure the system proxy, directing apps that support and follow it to the local proxy. Browsers usually read this setting, but in-app proxy settings, browser extensions, and system proxy exclusions can change how individual requests are routed. Terminal tools may not use the system proxy at all; they may rely only on their own settings or environment variables.
- App traffic does not reach the local proxy: Those requests are not controlled by these routing rules. Switching from “Bypass China” to “Global” will not make a program that does not use the system proxy start routing through a node.
- App traffic reaches the local proxy: The core uses the current configuration to choose a proxy outbound, direct outbound, or another outbound. When a direct rule matches, the app still connects to the local proxy; the core simply connects to the destination directly instead of using a remote node.
- An app still uses a node after the system proxy is disabled: First check whether the app has a local proxy configured explicitly, then check whether TUN is enabled. TUN provides a separate traffic entry point; clearing the system proxy does not turn it off.
“Do not change the system proxy” does not mean “clear the system proxy.” The former leaves the existing settings untouched. To check how an app connects without using the system proxy, inspect the system’s current proxy status.
When to use Global, Bypass China, or restore direct connections
System proxy on + Bypass China
RecommendedTraffic follows the active rule set: requests matching direct rules for mainland China domains, IP ranges, and similar targets bypass the node; other requests follow subsequent rules or the default outbound. The domain suffix alone does not tell you whether a request will connect directly. A single page’s main site, login API, and static assets may use different outbounds.
Best for: everyday access to both local services and sites that require a node
System proxy on + Global
Use a global routing setup that primarily routes traffic through the proxy outbound. It applies only to traffic that reaches the core and is governed by that setup. To check whether a destination is going direct because of a routing rule, keep the node fixed and temporarily switch to Global. With a custom configuration, also check for direct or block exceptions.
Best for: briefly checking whether a destination works through a node
Clear the system proxy + restore direct connections
Select “Clear system proxy,” then confirm that the app has no local proxy configured explicitly and TUN is off. This restores direct connections from the app to its destination, unlike sending requests through the core and matching a direct rule. If the device originally used an organization-provided proxy or auto-configuration script, restore those settings rather than disabling everything.
Best for: comparing with your original network setup or restoring your organization’s network configuration
Bottom line: use Global for comparison, then adjust specific rules
Keep the node and destination URL fixed, and change only the routing setup. If the destination works with Global but not with Bypass China, check which outbound is used for that destination and its dependent domains. Don’t immediately switch nodes or leave Global enabled permanently.
Set up and verify traffic routing on Windows
These steps use the common v2rayN 7.x interface. Routing preset names and port layouts may vary between minor versions, especially when migrating an older configuration. In the main window, open “Settings” → “Parameter settings” and check the current local listening port before choosing an address for the test commands.
Record the original settings
Open Windows “Settings” → “Network & Internet” → “Proxy” and note the existing manual proxy, setup script, and exceptions. During testing, turn off TUN and keep one known-working node selected so you don’t change multiple variables at once.
Choose a routing setup
In the v2rayN main window, open “Settings” → “Routing settings” and review the rules in the “Bypass China” preset. Then select that preset from “Routing” in the tray menu. If you use a custom preset, note its active name and the outbound label for the target rule so you don’t mistake a similarly named preset for the built-in one.
Set the system proxy
Right-click the v2rayN tray icon and select “System proxy” → “Set system proxy automatically.” Return to the Windows “Proxy” page and confirm that the manual proxy address and port match the local listener. If the settings revert, first check whether an organization policy or another program manages them.
Retest with the same destination
Use a browser that follows the system proxy to open the URL you want to test, then change only “Routing” to “Global” and try again. Start a new connection if possible to avoid reusing a session established before the change. If core access logs are enabled, check the destination domain and outbound against the request time. A page loading or a lower latency alone does not confirm which route was used.
Troubleshooting differences between browser and terminal results
In Windows Command Prompt, use the commands below to compare access to the same destination. This example assumes 127.0.0.1:10808 accepts HTTP proxy requests. If the port listens only for SOCKS, verify the inbound type first; an HTTP handshake failure does not mean the node is disconnected. Keep TUN off during testing.
curl.exe -v --noproxy "" --proxy http://127.0.0.1:10808 --connect-timeout 10 --max-time 20 https://v2rayapi.com/
curl.exe -v --noproxy "*" --connect-timeout 10 --max-time 20 https://v2rayapi.com/
- Use the first command to verify the local entry point:
--noproxy ""preventsNO_PROXYin the environment from bypassing the explicitly specified proxy for the test destination. If you see a connection to127.0.0.1and aCONNECTrequest, the request reached the local HTTP proxy. This still does not confirm that the core selected a remote node. - Use the second command as a direct-connection comparison:
--noproxy "*"makes this request bypass curl’s proxy. It’s normal if both commands succeed: that means the destination is reachable through both entry points, not that they use the same outbound route. - If the local port refuses the connection, check that it’s listening first: Confirm the core is running and the port matches the configuration. If the local connection is established but the tunnel or destination request fails, check the core logs for outbound errors, domain resolution issues, or node connection problems. The 10- and 20-second values in the commands are test timeouts, not speed benchmarks.
Common issues after switching proxy modes
Why does the terminal connect directly even with Global selected?
Global is a routing setup; it does not configure an entry point for the terminal. First use the explicit proxy command above to verify the local listener, then check whether the tool supports specifying a proxy or reading proxy environment variables. Don’t change a browser configuration that’s already working just because a tool ignores the system proxy.
Why does the home page load, but login keeps spinning with Bypass China?
Open the browser developer tools’ “Network” panel and retry the login. Find the destination domain for the failed request, then check its outbound. If it’s a routing issue, put the exact-match rule in your custom setup before any broader rule that could match first. Change one rule at a time and retest the login request.
Why is the browser still using the local port after I clear the system proxy?
Check the manual proxy and setup script on the Windows “Proxy” page, then review the browser’s own proxy settings and extensions. If the local port still appears in connection records, check whether the browser explicitly specifies that address, close existing connections, and retry. If the port no longer appears but traffic still exits differently than expected, check the TUN status.