At a glance

For cases where v2rayN is set to use the system proxy on Windows, but your browser still connects directly, pages won't load, or terminal commands can't access the network. First, test the local proxy with an explicit request. Then check the browser's proxy settings and the terminal's environment variables. Finally, test the same destination to determine whether the app bypassed the proxy, the local listener failed, or the outbound connection had an issue.

Check the local proxy first

The system proxy is a setting for apps to use, not a switch that redirects all traffic. Apps may follow system settings, use an extension or their own rules, or rely on a separate networking library. Even when a request reaches v2rayN's local listener, the core can still route it directly or through a proxy. So a page loading, an unchanged public IP, or the system proxy being enabled does not, on its own, show which route a request took.

App requestProxy selectionLocal listenerRoute matchOutbound connection
10808
SOCKS port often found in older configurations
10809
HTTP port used in this example
10 sec
Maximum test duration

In v2rayN, open Settings → Parameter Settings and check the local inbound port. The interface varies by version and configuration. If it shows a mixed port, use that port to test the HTTP proxy; don't try to calculate it by adding one to the SOCKS port. Run the commands below on the same Windows PC as v2rayN. If the actual HTTP or mixed port isn't 10809, replace the example port with the correct one.

curl.exe --verbose --max-time 10 --noproxy "" --proxy http://127.0.0.1:10809 https://example.com/

This explicitly selects the local HTTP proxy and temporarily clears the bypass list for this request. The destination uses HTTPS, but the local proxy address still starts with http://: HTTPS describes the destination connection, while HTTP describes how to communicate with the local proxy. To inspect the details, first confirm the connection goes to the expected port on 127.0.0.1. Then confirm that CONNECT was sent to the proxy and received a successful response. Finally, check that the destination returned an HTTP response. The 10-second limit is a test timeout, not a measured latency.

Browser: check which proxy settings are actually in use

  1. Check the system proxy address

    On Windows 11, open Settings → Network & internet → Proxy. If you plan to use a manual proxy, check that the address and port under Manual proxy setup match v2rayN's HTTP or mixed inbound. If you use a script, note the address under Use setup script and follow the PAC troubleshooting steps below. Don't change settings managed by your organization.

  2. Temporarily disable proxy extensions

    Open your browser's extensions page and temporarily disable extensions that switch proxies or route traffic by domain. Then reload the destination in the same browser profile. Don't rely on an incognito window as your only comparison: extensions can be allowed to run in incognito mode. If the issue goes away, re-enable extensions one at a time to find which one overrides the system settings.

  3. Check browser settings

    Chrome and Edge usually use the system proxy, but extensions, policies, or launch arguments can override it. Firefox lets you configure the connection independently under Settings → General → Network Settings → Settings. To use the system configuration, make sure Use system proxy settings is selected—not No proxy or a different automatic configuration URL.

  4. Check bypass rules

    Check whether the destination host is on the manual proxy's bypass list or matches a DIRECT rule in the PAC script. Compare the domain, subdomains, and actual hostname after redirects before deciding whether the rule is expected. Intranet and local addresses may need to bypass the proxy; don't clear the entire list just to fix one domain.

PAC is an automatic configuration script that selects a proxy for an app. v2rayN routing splits traffic after it reaches the local listener. If PAC has already chosen a direct connection, changing core routing won't affect that request. Conversely, if the local log already shows the test connection, stop toggling browser extensions and check which outbound rule matches the destination.

Terminal: set proxy variables for the current session

PowerShell launches commands; it doesn't handle network traffic for every command. Whether a command-line tool uses the system proxy depends on its networking library and configuration. For example, curl.exe accepts http_proxy and https_proxy to specify a proxy; the latter can still point to an HTTP proxy address. In Windows PowerShell, use the full name curl.exe to avoid accidentally running a same-named alias.

$env:http_proxy = 'http://127.0.0.1:10809'
$env:https_proxy = 'http://127.0.0.1:10809'
curl.exe --verbose --max-time 10 https://example.com/

Bottom line: check app settings after an explicit proxy test succeeds

If the same destination works through an explicit proxy but fails in a browser or a regular command, first check which proxy the app actually selected and review its bypass rules. Don't start by re-importing your subscription or switching nodes.

Use the error to pinpoint the listener, handshake, or outbound connection

Error: curl: (7) Failed to connect

Cause: If verbose output points to the test port on 127.0.0.1, the connection hasn't reached the expected local proxy. Fix: Check the port and core status, then verify that the listening process belongs to the core used by the current client.

Error: curl: (28) Operation timed out

Cause: The request exceeded its time limit; the error code alone doesn't show where it stalled. Fix: Check where verbose output stops: connecting locally, waiting for a CONNECT response, or during the destination's TLS handshake. Then compare with the core logs from the same time.

You can check for a listening port from PowerShell. The command below checks for a TCP listener only; it doesn't prove that the listener supports HTTP proxying. If it returns a result, compare OwningProcess with the PID in Task Manager's Details tab. Don't terminate a process you don't recognize.

Get-NetTCPConnection -LocalPort 10809 -State Listen |
  Select-Object LocalAddress, LocalPort, OwningProcess

If the port accepts connections but the proxy handshake fails, first check whether you've entered a SOCKS-only port in the HTTP proxy settings. If the proxy establishes a tunnel but the destination returns a certificate error or an access restriction, check the destination certificate, system clock, or site response as appropriate. Don't disable certificate verification to hide the problem. If only one domain fails, test another permitted HTTPS destination on the same port and compare the routing results and failure stages. This is more useful than repeatedly toggling the system proxy.