In v2rayN, the system proxy determines whether an app sends requests to the local proxy; the routing preset determines whether intercepted requests go direct or through the proxy. For everyday browsing, start with the system proxy and bypass-China rules. Use global routing temporarily for troubleshooting. For work and development, account for intranet exceptions, app-specific proxy settings, and DNS. This guide breaks down both settings and provides repeatable checks.
System Proxy and Routing Presets: Two Separate Settings
In v2rayN, the system proxy switch controls how traffic enters the proxy. Windows apps that use the system proxy settings send applicable requests to v2rayN's local listening address. Apps that ignore those settings may still connect directly. Turning on the system proxy does not route every network connection on the computer through the proxy.
Routing rules in the Xray or V2Ray core control where traffic exits. Once a request reaches the core, it matches rules based on criteria such as domain, destination IP, and port, then goes through a proxy, direct connection, or blocked route. “Global” and “bypass China” are usually routing presets, not alternative names for the system proxy switch.
Check v2rayN's actual listening port under “Settings” → “Parameter Settings,” where the local listener is configured. Different versions may use a mixed port or different field names. The 127.0.0.1:10809 value in this guide is a clearly labeled test example, not a default for every installation.
How Global, Bypass China, and Blacklist Routing Handle Traffic
V2Ray routing preset names are shortcuts provided by the client; actual behavior depends on the rules and their order. The table below describes common rule intentions. Custom rules, intranet exceptions, and blocking rules can change the result. In particular, check that “blacklist” means only destinations on the proxy list use the proxy while everything else connects directly.
| Preset | Typical rule behavior | When no rule matches | Main limitation |
|---|---|---|---|
| Global | Send all intercepted traffic to the proxy by default | Usually proxied | Doesn't capture apps whose traffic never reaches the core |
| Bypass China | Connect to domains or IPs in mainland China directly; proxy the rest | Usually proxied | Depends on the rule set, DNS results, and match order |
| Blacklist | Proxy destinations on the specified list | Usually direct | New domains may be inaccessible if they aren't listed |
Xray usually evaluates routing rules in order; the first match determines the outbound. If a broad proxy rule matches a company intranet domain, a later direct rule won't override it. Put intranet exceptions before broader rules. If no rule matches, check the configured default outbound rather than relying on the preset name alone.
How to check: find out what happens to unmatched requests
When choosing a preset in v2rayN, check the fallback behavior first. A proxy fallback suits browsing that needs broad proxy coverage; a direct fallback suits setups where only a few specific destinations should use the proxy. Then make sure intranet exceptions come first.
Choosing a Setup for Browsing, Work, and Troubleshooting
For everyday browsing with v2rayN, start with “Set system proxy automatically” plus bypass-China rules. Browsers that follow the system proxy connect to the local proxy first, then traffic is routed by the rules: mainland China sites usually connect directly, while other destinations usually use the current node. This isn't the best choice for every setup, but it's easy to understand and verify.
System Proxy + Bypass China
RecommendedCommon services in mainland China stay on a direct connection, while other intercepted requests follow the routing rules. If a domain is misclassified, add a specific rule first instead of expanding traffic capture right away.
Best for: everyday browsing and using services in and outside mainland China
System Proxy + Global Routing
Remove regional classification as a variable when checking whether routing rules are preventing access to a destination. Once testing is complete, restore your usual preset so intranet and local services aren't inadvertently sent to a remote proxy.
Best for: brief troubleshooting or browsing that needs a consistent proxy exit
Selective Capture + Blacklist
Only destinations explicitly listed use the proxy; all other requests connect directly. A site may depend on several domains for static assets and APIs, so check those together when maintaining the list.
Best for: work environments where only a few services need a proxy and direct connections are preferred
Global routing in V2Ray doesn't guarantee that every site will show the same region. Sites may infer location from account region, browser location permissions, cached data, and exit IP; different nodes may also use different exits. If location still varies after switching to global routing, check the request's exit and the site's own location signals separately rather than assuming the system proxy has failed.
v2rayN Setup: Configure Traffic Capture, Then Routing
Menu names in v2rayN vary by interface version. On Windows, the taskbar notification area is a common place to find the controls. Change one setting at a time and reconnect to the same destination. Simply refreshing a page that reuses an existing connection may not show the true effect of a routing change.
- Check the node and core. Select an imported configuration in the main window and set it as the active server. Check the log to confirm that it started successfully. A subscription is a source for updating configurations, not a traffic exit; the exit depends on the active node and its outbound configuration.
- Note the local listener. Open “Settings” → “Parameter Settings” and check the listening address, port, and supported proxy types. If the proxy is only for this computer, keep it bound to the loopback address; don't expose it to the local network just to connect a browser.
- Turn on the system proxy. Right-click the tray icon and choose “System Proxy” → “Set system proxy automatically.” Then open Windows “Settings” → “Network & Internet” → “Proxy” and confirm that the proxy address matches the local listener.
- Choose a routing preset. In the tray “Routing” menu or the routing selector in the main window, choose the bypass-China rules. Some versions label this option “Bypass mainland China IPs” or similar; check the rules themselves as well.
- Test, then restore your settings. Visit one destination expected to connect directly and another expected to use the proxy. For troubleshooting, switch temporarily to global routing, then restore your usual preset. Before stopping, use “System Proxy” → “Clear system proxy” to remove the settings written by v2rayN.
In v2rayN, “Clear system proxy” does not stop the core. Developer tools configured with a local proxy address may still connect to a listening port. Conversely, quitting the client while leaving a system proxy pointed at an inactive local address can prevent apps that follow that setting from connecting. On managed devices, proxy settings may be controlled by policy; note the existing settings and follow your organization's requirements before making changes.
Work and Development: Other Ways to Route Traffic
v2rayN's system proxy doesn't replace the proxy settings in each development tool. Command-line tools may read environment variables or require their own arguments. Browser-specific proxy settings or extensions can also override the system settings. When troubleshooting, first identify the local address the tool connects to, then check routing.
Setup Checklist: Test Work Browsing and Development Tools Separately
Work Browsing
- Use the system proxy to capture traffic and start with bypass-China rules.
- Add company intranet domains and required private subnets as direct-connection exceptions.
- Check both the system proxy bypass list and the core's direct-routing rules.
- When the company VPN is active, recheck DNS and intranet routing.
Command-Line and Development Tools
- Set the local proxy explicitly in each tool rather than relying on implicit settings.
- Test with a single command before making environment variables persistent.
- Exclude loopback services and development environment addresses from the proxy when needed.
- Record the port and proxy type; distinguish HTTP from SOCKS.
Both environments can share a node configuration while using different ways to capture traffic. Confirm that requests reach the core before interpreting the routing result.
If v2rayN is confirmed to provide an HTTP proxy at 127.0.0.1:10809, run this one-time test in Windows Terminal. If the actual port differs, update the command first. This only checks whether this HTTPS request can be made through the local proxy; it doesn't prove that the destination uses the remote node's exit.
curl.exe --proxy http://127.0.0.1:10809 --connect-timeout 10 --max-time 30 --head https://example.com/If Xray access logging is enabled, use it to check which outbound handled the request. An HTTP status code means the server responded. If the local connection is refused, check the port and listener first. If the local proxy connects but the request times out, check the node connection, DNS, and routing. Don't treat these as the same failure.
v2rayNG VPN Mode Differs from a Desktop System Proxy
On Android, v2rayNG usually captures traffic through the system VPN interface and passes it to Xray. The first time the service starts, it asks for VPN permission. This differs from the way Windows writes an HTTP proxy to the system settings. App-based routing also affects which traffic is captured: excluded apps won't start using the proxy just because global routing is selected.
- Check which apps are captured first. In v2rayNG “Settings,” check the per-app options to see whether the app proxies selected apps or bypasses selected apps. Option names vary by version, so follow the descriptions in your current interface.
- Then check the routing rules. In “Settings,” find the routing options and check whether direct-connection rules for mainland China domains or IPs are enabled. Don't assume desktop preset names are fixed menu labels on Android.
- Handle VPN conflicts separately. In typical Android use, only one VPN service can be active at a time. If the company VPN and v2rayNG compete for the VPN connection, first check which service Android is currently connected to.
- Check the DNS path too. Check how the app resolves domains and how the client handles and forwards DNS requests. Global routing doesn't mean every DNS request automatically goes through the remote server.
v2flyNG uses the V2Fly core; check its interface and supported settings against the version you're running. Protocols such as VMess and VLESS describe how the client communicates with the remote server. They don't determine whether an app uses the system proxy or replace routing rules. Changing protocols won't fix a request that never reached the client.
Troubleshooting: Trace the Traffic Path
Why does the terminal still connect directly with global routing enabled?
Global routing in v2rayN only handles captured traffic. First test with the explicit proxy command using curl.exe above. If that works, check the terminal tool's proxy arguments or environment variables; there's no need to change the node first.
What if company intranet sites stop working with bypass-China routing?
In v2rayN, check both the system proxy bypass list and the core's direct-routing rules. Add the actual intranet domains in the right place and confirm that intranet DNS is reachable. A private IP address alone doesn't guarantee that the domain will resolve correctly.
Why does a site load in blacklist mode but fail at login?
The V2Ray proxy list may cover only the main site, leaving login APIs or resource domains on a direct connection. Use the browser developer tools Network panel to find the failing domains, check the logs, add the appropriate rules, and try logging in again.
Why can't the browser connect after I close the client?
After v2rayN exits, a system proxy pointing to a local port may remain active. Open Windows “Settings” → “Network & Internet” → “Proxy” and check for settings left behind by this session. You can also reopen the client and choose “Clear system proxy.” Restore organization-managed settings according to the original policy.
Global routing works, but bypass-China doesn't. Is the node broken?
If the result changes when you switch only the routing preset in v2rayN, using the same traffic-capture setup, check for differences in rules or DNS resolution first. See which outbound matches the destination and check its domain classification and custom rule order. If needed, add a specific rule for that destination, then restore your usual preset and test again.
Troubleshooting Order: Capture, Resolve, Match, Exit
With both v2rayN and v2rayNG, first confirm that the request reaches the client, then check how the domain resolves, which routing rule matches, and finally which outbound is used. Change one setting at a time and establish a new connection; this makes the cause easier to find than switching nodes, enabling global routing, and changing capture settings all at once.