If switching to Global makes no difference in an app, first check whether the app is sending requests to v2rayN. If Global works but routing rules do not, check which rule matched the request. This guide covers system proxy settings in the Windows desktop client, choosing a routing preset, checking listening ports, and using the same destination to tell an inbound issue from an outbound one.
System proxy controls the entry point; routing rules control the exit
Selecting “Set system proxy” points Windows’ system proxy settings to v2rayN’s local listening address. Apps such as browsers that follow these settings send the relevant requests to the local proxy. Apps with manually configured proxies, command-line tools that read environment variables, and programs that ignore system proxy settings may take a different route. This setting is not the same as TUN and does not capture every connection on the device.
Routing rules only apply to connections that have already reached the core. Based on available information such as the inbound, destination domain, and IP address, a rule selects a proxy outbound, a direct outbound, or another outbound specified by the configuration. A proxy outbound typically uses the currently selected server configuration. A direct outbound is still handled by the core; it simply connects without a remote proxy server.
- System proxy off, Global routing selected: Apps without a separately configured proxy usually will not reach the core. Apps explicitly pointed at the local port can still connect.
- System proxy on, Direct routing selected: Apps that follow the system proxy may still connect to the local port. If you stop the core but leave the system proxy enabled, websites may still fail to load.
- System proxy on, routing rules enabled: Requests first reach the local proxy, then are routed according to their destinations. Checking your public IP once only shows which route that particular request took.
Choosing Global, Bypass LAN & China, or Direct
In the common v2rayN 7.x interface on Windows, open “System Proxy” from the tray icon’s right-click menu. Change the current route from the “Routing” dropdown at the bottom of the main window, and review the rules under “Settings” → “Routing Settings.” Names can vary between minor versions and imported configurations. If you cannot find a “Direct” preset, do not confuse it with “Clear System Proxy”—they are different actions.
Bypass LAN & China
RecommendedA common preset sends destinations matching LAN and mainland China rules directly, while other destinations follow the fallback rule, usually through the proxy. The actual outcome depends on destination details, rule order, and the rule set—not the language of the website interface. With a third-party configuration, check the direct-match conditions and the final fallback outbound first.
Best for: everyday split routing when you need to access both local services and sites that require a proxy.
Global
Typically sends requests that reach the core to the proxy outbound unless they match an earlier exception. Keeping the same server, temporarily switch to Global to compare it with split routing and narrow down the issue. This will not fix an app that ignores the system proxy or a local port that is not listening.
Best for: a short comparison test to the same destination, or apps that explicitly need all traffic to use the proxy outbound.
Direct
Sends requests that reach the core straight to their destinations, without a remote proxy. The local proxy hop remains in place, making this useful for comparison with the proxy outbound. To see what happens when an app bypasses v2rayN entirely, test separately without a proxy.
Best for: keeping the same local entry point while comparing reachability through a remote proxy versus a direct connection.
Check the listening port, then compare the same destination
In v2rayN, open “Settings” → “Settings Parameters” and check the local listening port and proxy type. Then review the main window log for startup failures or port-conflict messages. The addresses and ports below are common examples for local troubleshooting, not measurements of your current configuration. The two ports may not both be enabled, and one port may accept both HTTP and SOCKS requests.
Run these commands in Windows Command Prompt. The first sends this request without a proxy. The second explicitly uses the local HTTP proxy and clears the bypass list for this request. If the port configured for HTTP is not 10808, replace it with the actual port. When comparing results, use the same test URL without a token in both commands. If the site does not support HEAD requests, remove -I from both commands and try again.
curl.exe -q --noproxy "*" -I --max-time 15 https://example.com/
curl.exe -q --noproxy "" --proxy http://127.0.0.1:10808 -I --max-time 15 https://example.com/
- Connection to the local port is refused: Make sure the core is running, then check the port and listening address. If the log reports a port conflict, switch to an unused port and update any proxy address entered manually in your apps.
- The proxy tunnel is established, but the request then fails: A response from the local entry point does not mean the destination HTTPS request succeeded. Check for a proxy tunnel error, a destination TLS error, or a status code returned by the destination site. Do not mistake the proxy response
200 Connection establishedfor a page response of200 OK. - Explicit proxy works, but the browser still fails: In Windows, open “Settings” → “Network & internet” → “Proxy” and check the system proxy address. Also check whether the browser uses its own proxy settings. The second command tests the manually specified entry point, not whether the browser inherited the system settings.
Troubleshoot routing issues: keep the entry point and server fixed; change only the route
Retest with the same app, destination, and server configuration. Record the split-routing result first, then switch temporarily to Global. Start a new connection after each switch so the browser does not reuse an old one. If Global works but split routing does not, check rule matching and the actual outbound first. This result does not mean the subscription has expired, nor does it prove DNS is the only cause.
Troubleshooting steps for two common issues
Public sites work only in Global mode
- Open the current split-routing configuration under “Routing Settings” and check the domain rules, IP rules, and final fallback outbound.
- Check the core access log for the destination and outbound tag, if the current configuration records these fields. If the main page loads but images or sign-in fail, check the domains of the failed requests separately.
- The same destination may match different rules when it reaches the core as a domain name versus an IP address. Check which destination information the rules actually received before changing them.
LAN services become unreachable when the proxy is enabled
- First, try accessing a known local address and service port without a proxy. Confirm that this device is on a network that can reach the service.
- Check the system proxy’s bypass list. Requests to LAN destinations excluded by the app will not appear in the core log in the first place.
- If the request does reach the core, check whether the actual private IP address matches a direct rule and whether that rule appears before broader proxy rules.
First distinguish an app-level bypass from a direct route inside the core. Change only the layer causing the issue, then retest and restore any temporary settings.
FAQ: system proxy not working and no internet after exit
Why does the browser work while command-line tools still cannot connect?
Use the explicit proxy command above to test the local entry point. If it succeeds, check whether the original tool supports proxy options or reads environment variables such as HTTP_PROXY, HTTPS_PROXY, and NO_PROXY. The proxy type must match the port; do not enter a SOCKS-only port as an HTTP proxy.
Why do some apps still use the server after I turn off the system proxy?
Check whether the app has a manually configured local proxy, inherits environment variables from the terminal, or has TUN enabled in the client. Turning off one entry point does not disable the others. Start a new connection after making changes, and restart the app if needed before checking the logs again.
Web pages stop loading after I exit v2rayN. Should I change the routing rules first?
There is no need to change the routing rules first. Open the Windows “Proxy” settings and check whether the manual proxy still points to a local port that is no longer listening. If v2rayN left the setting behind, reopen the client, select “Clear System Proxy” from the tray menu, and then exit. If your device had a work proxy configured beforehand, restore its original settings—do not remove settings managed by your organization.
Does seeing a local exit IP in split-routing mode mean routing is broken?
Not necessarily. The IP lookup site itself may match a direct rule. Use the same lookup site, browser, and server to compare split routing with Global, then check the outbound record for that request. Other sites may still use different exits. If the destination is also unreachable without a proxy, start with the basic connection troubleshooting guide.