System Proxy Not Working? Troubleshoot Browser and Terminal Proxy Settings

Browser traffic uses the proxy, but terminal traffic doesn’t—or neither works? Check browser extensions, system settings, and environment variables separately.

At a glance

For users who have started v2rayN but see different results in their browser and terminal. First use curl to connect directly to the local proxy and confirm the port and protocol work. Then check how the browser selects a proxy and which environment variables the terminal process uses. Windows examples show how to check listening ports; the same curl tests work on macOS and Linux.

Local listener: Find the port your app connects to

App requestProxy selectionLocal listenerRouting matchOutbound connection

The system proxy provides a proxy address to apps that read system settings; it does not automatically route every process. An app may use the system settings, its own proxy configuration, or connect directly. The core routes traffic only after a request reaches v2rayN, deciding whether to send it through a proxy outbound or a direct outbound. So “the app connected to the local port” and “the request used a proxy outbound” are two different conclusions.

10808
Example mixed-proxy listener port
443
Example HTTPS destination port
15 seconds
Total timeout per test

In v2rayN, open Settings → Parameter settings and check the local listening ports. If your version shows separate HTTP and SOCKS ports, note each one separately. Test both protocols on the same port only if it is explicitly configured as a mixed listener. The examples below use 127.0.0.1:10808. Replace it with your actual settings, and run the tests in the same system environment as v2rayN.

Check the listener in Windows PowerShell. If the only result is ::1, that entry is for the IPv6 loopback address; it does not confirm that 127.0.0.1 is available. If multiple processes are returned or you changed the port, verify the process ID and port to identify the owner. Don’t assume a listener belongs to the v2rayN core based on the port number alone.

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

Explicit proxy test: Use curl as a baseline

These commands use common options available in curl 8.x. Run curl --version first to confirm that you’re invoking curl. On Windows, run the three commands below in Command Prompt to avoid PowerShell environments that treat curl as an alias or drop empty strings when passing arguments. On macOS and Linux, run them in a standard terminal.

curl --disable -v --max-time 15 --noproxy "" --proxy http://127.0.0.1:10808 https://example.com/
curl --disable -v --max-time 15 --noproxy "" --proxy socks5h://127.0.0.1:10808 https://example.com/
curl --disable -v --max-time 15 --noproxy "*" https://example.com/

The first two commands test HTTP and SOCKS, respectively; run only the one that matches your listener type. --disable comes first to skip curl’s default configuration file. --noproxy "" clears the destination exclusion list for this request. The third command tells curl not to use an application-level proxy as a baseline. If other software intercepts traffic at the system level, this command cannot prove that packets ultimately went directly to the destination.

For an HTTPS destination, an HTTP proxy first receives CONNECT example.com:443. A 200 Connection established response only confirms that the tunnel was created; check the subsequent TLS handshake and destination response too. socks5h passes the destination hostname to the SOCKS proxy for resolution; it is not equivalent to socks5, which has curl resolve the hostname first. If the results differ, record the difference rather than changing the port, routing, and DNS settings all at once.

Bottom line: Use an explicit proxy to narrow down the problem

If the explicit command gets a response from the destination but a regular command in the same terminal fails, first check how that command selects a proxy. If the request can’t connect to the local listener, verify the address, port, and listening process first; there’s no need to change browser settings yet.

Browser: Separate extension settings from system settings

  1. Disable proxy extensions

    Temporarily disable extensions with proxy controls on the extensions management page for the current browser profile. Don’t rely on the extension icon alone: domain-matching rules may route different sites in different ways. If your browser is managed by an organization, check for locked settings first.

  2. Check which proxy the browser uses

    In Firefox, open Settings → General → Network Settings → Settings… to see the current proxy configuration. To test the system proxy, select Use system proxy settings. To test a manual configuration, enter the address and port for the corresponding listener type. Don’t enter a SOCKS port in the HTTP proxy field.

  3. Check the system proxy

    In Windows, open Settings → Network & Internet → Proxy. If System proxy in the v2rayN tray menu is set to Automatically configure system proxy, check the address, port, and exceptions actually set on the system page. If you use a configuration script, check whether it routes the destination domain directly.

  4. Test the same URL again

    Return to the same browser profile, reload the URL tested with curl, and check the v2rayN logs for the request time and destination domain. If you need to re-enable a proxy extension, enable just one at a time and test the same destination. This keeps changes to system settings and extension rules separate.

If the browser opens a page but you can’t find the corresponding request in the v2rayN logs, first check whether the current log level records connections, then rule out cached content and existing connections. An open page doesn’t prove that the browser used the system proxy: the request may have connected directly to the destination or used the browser’s own manual proxy settings.

Terminal: Check which variables the process reads

Even when a browser uses the system settings, command-line tools may rely only on their own configuration or environment variables. For curl, HTTPS destinations typically use https_proxy; if there’s no applicable protocol-specific variable, curl may fall back to all_proxy. Use no_proxy to exclude destinations. For HTTP destinations, curl’s proxy variable must be lowercase http_proxy. Don’t assume this rule applies to every tool.

Check the variables in the terminal where the error occurs, not in a different window. The commands below list only variable names, so you won’t accidentally copy proxy addresses that may contain credentials into a support ticket.

# Windows PowerShell
Get-ChildItem Env: | Where-Object {
  $_.Name -match '^(http_proxy|https_proxy|all_proxy|no_proxy)$'
} | Select-Object -ExpandProperty Name
# macOS or Linux: Run in a standard POSIX-compatible shell
env | cut -d= -f1 | grep -Ei '^(http_proxy|https_proxy|all_proxy|no_proxy)$'

Common errors: Pinpoint the stage that failed

Error: curl: (7) Failed to connect to 127.0.0.1 port 10808

Cause: curl couldn’t establish a TCP connection to the example local port. What to do: Check for a listener on the same address and port. Then confirm that the v2rayN core is running and that the command is running in the same system environment.

Error: curl: (56) CONNECT tunnel failed, response 407

Cause: The HTTP proxy response indicates that authentication is required. What to do: Confirm that curl connected to the expected proxy. If it reached an outdated proxy address, fix the proxy configuration. If authentication is required, configure it using that proxy’s supported authentication method.

Error: curl: (6) Could not resolve host: example.com

Cause: The request failed when curl tried to resolve the destination hostname. What to do: Check the verbose output first to see whether an exclusion rule sent the request directly or whether curl is using a SOCKS mode that resolves the hostname locally.

If both the browser and explicit curl connect to the local port but still can’t reach the same destination, search the v2rayN logs for the destination domain at the time of the test. Check the local inbound connection, routing match, and outbound connection in that order, then inspect the matching rule or error. Changing browser extensions usually won’t fix an outbound connection failure.

For each retest, record three results: whether the explicit proxy received a response, which proxy settings the browser used, and whether the original terminal can reproduce the issue. Change one thing at a time. Once the problem is gone, restore any temporarily disabled extensions or settings changed for testing, then retry the original failing operation.

Download v2rayN