Just imported a subscription into v2rayN and not sure whether to enable the system proxy or choose Global mode? Start with this: the system proxy determines whether an app's requests reach the core; routing rules determine where they go next. The browser, terminal, and local network examples below show how to choose and verify your setup.
System proxy and routing mode are separate settings
When you set the system proxy from the v2rayN tray menu, the client adds its local proxy address to your system proxy settings. Only apps that read and use that setting send requests to the local proxy port. Browsers often use it, but extensions or browser-specific settings can override it. Terminal tools may use a different configuration—or none at all.
Routing rules take effect only after a request reaches the local core. They decide whether it goes through a proxy outbound, connects directly, or is blocked. Here, “direct” means the core connects to the destination itself; it does not mean the browser bypassed the core from the start. The results may look the same in a browser, but troubleshooting requires checking these paths separately.
- System proxy on, Global routing selected: Ordinary requests that reach the core usually go through the proxy. Apps that don't use the system proxy won't be routed through it automatically.
- System proxy off, proxy address configured manually in the app: As long as the local core is listening, the app can still send requests to it, and the selected routing rules still apply.
- Need to capture apps that ignore the system proxy? First check whether the app supports its own proxy settings. TUN is a separate way to capture traffic, not the same as Global routing; what it captures also depends on interface routes and exclusions.
Choosing between Global, bypass-China, and custom routing
Bypass China
RecommendedCommon presets send requests matching mainland China domain or IP rules to a direct outbound; most other requests go through the proxy. Check whether the preset has separate private-network rules before assuming local network addresses will connect directly.
Best for: everyday browsing when you want mainland Chinese sites to connect directly while keeping a proxy available for other traffic
Global routing
Routes ordinary requests that reach the core through the proxy. This is useful for a quick check of whether a destination is reachable through your proxy. The configuration may still include exceptions, such as private-network addresses, so review the active rules before switching.
Best for: briefly testing a fixed proxy exit or troubleshooting existing routing rules
Custom routing
Route internal domains, specific services, or address ranges separately, then explicitly set a default outbound for everything else. The more rules you add, the more important it is to document exceptions so a preset change doesn't undo your intended routing.
Best for: routing internal services and external APIs through different exits, with specific test targets
Change one setting at a time when troubleshooting
Use the same app to visit the same URL, keeping the same node and connection method, and change only the routing mode from Bypass China to Global. If the result changes, check which rule matched the destination. Don't switch nodes at the same time, or you won't know whether routing or the node caused the difference.
“Bypass China” uses routing data and matching conditions to choose an outbound for each request. A page's main domain may connect directly while its images, login flow, or API use other domains. If a page loads but sign-in spins indefinitely, find the failed request's hostname in the browser's Network panel and check its outbound route instead of testing only the address-bar domain.
Browser works, terminal doesn't: verify the proxy connection first
In v2rayN, open Settings → Parameter Settings and check the local listening port and supported inbound protocols. Field names may vary by version. The examples below assume local 10808 accepts SOCKS5 and use the same HTTPS destination for both requests. In Windows PowerShell, replace curl with curl.exe.
curl --noproxy "*" -v -I https://example.com/
curl --noproxy "" --proxy socks5h://127.0.0.1:10808 -v -I https://example.com/
- First, check the result without an application-level proxy. The first command ignores curl's proxy settings and shows the current network path for comparison. If TUN is still capturing traffic, this does not mean the request connected directly to the internet. To test a path that bypasses the core, turn off TUN as well.
- Next, check whether the local proxy is reachable. The second command explicitly sets a proxy and clears the proxy exclusion list for this request.
socks5hsends the destination hostname to the proxy to resolve instead of having curl resolve it first. If the output says it can't connect to127.0.0.1:10808, check that the core is running and the port is correct. If TCP connects but the SOCKS handshake fails, check the inbound protocol. - Only then check the actual outbound route. Getting an HTTP status code from the second command doesn't prove the request went through a proxy node. Check the core logs around the request time and look for the destination hostname. If the current logs show outbound tags, verify whether the route was proxy or direct. A connection result alone doesn't prove that a particular routing rule matched.
If an explicitly proxied request works but your usual command doesn't, check whether the tool has its own proxy options, reads environment variables, or excludes the destination. For development and troubleshooting, start with a one-off command. Once you've confirmed you need the proxy regularly, configure it in the relevant tool to avoid affecting other tasks in the same terminal session.
For custom rules, add exceptions before the fallback
Suppose your team needs internal services to connect directly and a particular external API to use the proxy. Check the routing configuration currently enabled in v2rayN before adding rules; don't append them after a rule with a broad match. In configurations that evaluate rules in order and choose an outbound on a match, an earlier broad condition can prevent later exceptions from ever taking effect.
- List the actual destinations first. Record internal service domains and IP ranges separately. If a program connects to a device by IP, a domain rule won't match that request. If it connects by domain, whether an IP rule can match depends on the core's DNS resolution and routing strategy.
- Put specific exceptions before broad rules. Add internal destinations that must connect directly first, followed by external APIs that must use the proxy. Confirm that the outbound tags referenced by the rules exist; the display names shown in a preset interface may not match the tags in the configuration.
- Set an explicit fallback for unmatched traffic. Confirm whether remaining requests should follow the original preset through the proxy or connect directly—don't guess. After saving and applying the rules, open new connections to test one direct destination, one proxied destination, and one destination without a specific rule. Existing connections may be reused, so refreshing a page might not create a new one.
Three common issues after switching modes
Why isn't my terminal using the proxy in Global mode?
Use the explicit proxy command above to confirm the terminal can connect to the local core. If it works, configure the proxy protocol supported by the tool you actually use and check its own exclusion list. Global mode doesn't configure the terminal for you.
Why can't I open my router's admin page after switching to Bypass China?
First, test the device's local network IP to see whether the problem is limited to its admin hostname. If you want the browser to connect directly, add the device address to the proxy exclusions used by the browser or system. If the request should still go through the core, check whether that IP matches a private-network direct rule. If TUN is on, check its routes and exclusions separately.
After I quit v2rayN, no websites load. Is the routing mode wrong?
Open your system proxy settings and check for a leftover address pointing to a local listening port. Then check whether the browser has its own proxy configured. If you didn't previously use a system proxy, remove the leftover setting; if you used a workplace proxy, restore its original configuration. Then retry with a new connection. The local core has exited, so changing the routing preset won't fix an entry point that still points to a closed port.