On Windows, browsers and terminals don’t necessarily use the same proxy settings. First, use PowerShell to check that v2rayN is listening locally, then point curl directly at that port. Once the direct request succeeds, check browser extensions and Windows proxy settings for browser issues, and environment variables and tool-specific settings for terminal issues. Keep the node, routing rules, and destination URL unchanged during testing so you can isolate the cause.
Check that v2rayN is listening locally
System proxy settings tell apps where to send requests; routing rules determine how the core handles them. Seeing “Set system proxy automatically” in the tray only confirms that the mode is selected. It doesn’t prove that Windows settings were applied, that a port is listening, or that the request to your destination is using a proxy outbound. When troubleshooting the standard system proxy, note the current TUN status and temporarily turn TUN off if it’s enabled. Otherwise, an app that ignores the system proxy may still reach the destination, making the results harder to interpret.
Check the local listener details in the status bar at the bottom of the v2rayN main window. To review the configuration, open “Settings” → “Parameter Settings” and check the core’s basic settings. Field names and port assignments vary by version. The example below assumes the local listener supports HTTP at 127.0.0.1:10808. If the status bar shows different HTTP and SOCKS ports, use the HTTP port in the commands.
Test-NetConnection -ComputerName 127.0.0.1 -Port 10808
curl.exe -v --max-time 15 --noproxy "" --proxy http://127.0.0.1:10808 https://example.com/
TcpTestSucceeded : False: First check for a typo in the port and look in the v2rayN logs for core startup or listener errors. Browser extensions and terminal variables can’t make a port work if nothing is listening on it.TcpTestSucceeded : True: This only confirms that a process accepted the TCP connection. If curl connects but can’t complete the HTTP CONNECT request, check which process is listening, the inbound protocol, and the core logs.- If curl connects to the local port, completes CONNECT, and receives a response from the destination, the request went through the local HTTP proxy. Routing rules may have sent it direct or through a proxy outbound; the webpage response alone can’t tell you which.
Browser checks: Windows settings and extensions
If a direct proxy request works but the browser doesn’t, first use the system settings as a baseline. Edge and Chrome usually follow the system proxy, but extensions, startup flags, and organization policies can change how they connect. Don’t assume an extension is ruled out just because the issue persists in an Incognito or InPrivate window: extensions allowed in private browsing can still control the proxy.
- In the v2rayN tray menu, select “System Proxy” → “Set system proxy automatically.” Then open Windows “Settings” → “Network & internet” → “Proxy” and check that the manual proxy address and port match the current HTTP-capable listener. Also check whether “Use setup script” points to an outdated configuration. Note the original values before changing anything. Ask your administrator to check settings managed by your organization.
- Temporarily disable proxy-switching extensions in the browser’s extension manager, then open a new window and visit the same URL. If it works, re-enable extensions one at a time. If the problem returns when you enable one, check whether it’s using an outdated port, script, or direct-connection rule.
- In Firefox, go to “Settings” → “General” → “Network Settings” → “Settings” and select “Use system proxy settings” as a comparison. If it was set to “No proxy” or “Manual proxy configuration,” changing the Windows proxy toggle won’t override that selection.
- If only a few domains behave differently, check Windows proxy exclusions, extension matching rules, and v2rayN routing separately. The first two can keep requests from reaching the local proxy; core routing only applies after a request arrives.
If an explicit proxy request works but the browser fails, check how the browser selects its proxy first.
Fix the proxy address used by the extension or browser, then retest the same URL. Switching nodes adds another variable and won’t fix an outdated port still configured in the browser.
Terminal checks: compare explicit proxy options with environment variables
A browser that can load websites doesn’t mean command-line tools will use the Windows system proxy. The commands below call curl.exe explicitly, rather than relying on how PowerShell resolves the name curl. Replace the example port with the one v2rayN is actually using, and run the commands in a new PowerShell window to avoid overwriting variables in your regular session.
Get-ChildItem Env: | Where-Object Name -Match '^(HTTP_PROXY|HTTPS_PROXY|ALL_PROXY|NO_PROXY)$'
$env:HTTPS_PROXY = 'http://127.0.0.1:10808'
curl.exe -v --max-time 15 --noproxy "" https://example.com/
curl.exe -v --max-time 15 https://example.com/
HTTPS_PROXYapplies to HTTPS destinations; it doesn’t mean the local proxy itself must use HTTPS. In this example, curl connects to the local proxy over HTTP, then uses CONNECT to establish a tunnel and negotiate TLS with the destination site.- If only the first request uses the local port, check
NO_PROXY. The empty--noproxyargument disables destination exclusions for this comparison; the second command keeps the exclusions in your environment. Don’t clear internal network exceptions required by your organization just to test one domain. - A terminal that’s already open won’t automatically pick up environment variables set by another process afterward. These assignments affect only the current PowerShell session and the child processes it starts. Close the test window to discard this temporary configuration.
- If curl works but the original tool still fails, check that tool’s proxy options and configuration precedence. Tools don’t necessarily recognize the same environment variables. Also, don’t assume that
127.0.0.1in WSL, a container, or a remote session refers to the Windows host.
Identify the failing connection stage from the error
“Can’t connect” can mean anything from failing to resolve a proxy address to failing to connect to the local port or validate the destination certificate. Save curl’s verbose output alongside v2rayN logs from the same time, then check how far the request got. Remove subscription URLs, credentials, and proxy authorization headers before sharing logs.
curl: (5) Could not resolve proxy: proxy.invalid
Cause: curl can’t resolve the hostname of the currently selected proxy. Fix: Check the explicit proxy options, environment variables, and curl configuration for an outdated address, then test again using the actual local loopback address and port.
curl: (60) SSL certificate problem: unable to get local issuer certificate
Cause: curl can’t validate the peer’s certificate chain using its current trust store. Fix: Check whether the failure occurs before or after CONNECT, then verify the relevant proxy or destination certificate chain and the trust store used by curl. Keep certificate verification enabled.
After making changes, test both the browser and the original terminal tool; don’t rely on a single successful curl request. If the problem persists, note whether the browser uses system settings, the address curl actually connects to, whether CONNECT succeeds, and whether the core logs show a matching request. This helps distinguish an app using the wrong proxy from a local listener issue or a failure after the request reaches the core.