Check the listening port first, then find out which side is bypassing the proxy

Start by separating two questions: did the request reach Clash, and if so, did it match a direct route or a proxy route? The system proxy setting provides an address and port to apps that choose to use it; it does not take over every process's connections. A browser loading a webpage does not prove that the terminal is using the proxy. Likewise, an unchanged public IP alone does not prove that the request never reached Clash.

  1. Check the active configuration. In the client, check the listening address and port for the enabled configuration rather than relying on outdated values in the subscription file. Local client settings may override the subscription's port. The examples below use 127.0.0.1:7890. If the active mixed port is 7897, use 7897 in both system settings and test commands.
  2. Check which proxy protocol the port supports. In mihomo, mixed-port accepts both HTTP and SOCKS5 proxy requests, port is the HTTP proxy port, and socks-port is the SOCKS proxy port. external-controller is for the control API, not proxy traffic.
  3. Use the same test request on both sides. Visit the same HTTPS domain from your browser and terminal, such as example.com. Open the client's connection log while making the requests. Short-lived requests may disappear quickly from the live list; if request logs are available, search by domain and time.

Browser troubleshooting: system proxy, extensions, and custom settings

Check which proxy settings the browser is actually using

In Windows 11, go to Settings → Network & internet → Proxy and check the address and port under Manual proxy setup. If you're using a setup script, verify its URL and the proxy decision it returns for your test domain. A PAC file can proxy only certain domains, so enabling the script does not mean every request will be forwarded.

Chrome and Edge typically use the system proxy, but extensions, startup flags, and management policies can change the active settings. Firefox can also use a separate proxy configuration: go to Settings → General → Network Settings → Settings… and select Use system proxy settings to follow the system. Check that No proxy or an outdated manual configuration hasn't been selected instead. On managed devices, ask your administrator to check the policy; don't change settings deployed by your organization.

Disable extensions and retest with a new connection

  1. Record the current settings, then temporarily disable extensions that switch proxies, changing one thing at a time. Incognito mode is only a quick first check: extensions allowed to run in incognito can still affect the results, and opening an incognito window does not disable the system proxy or management policies.
  2. Quit the browser completely, then reopen it. Open Developer Tools, select the Network panel, check Disable cache, and leave the panel open while visiting the test domain. This helps rule out cached pages and reused connections.
  3. If the client logs connections, check the rule matched for the domain and the final outbound. If requests for only certain domains don't appear, check the system proxy bypass list, PAC direct-connection rules, and the browser's own proxy bypass settings. Don't rush to reinstall the client.

Terminal troubleshooting: use curl to connect directly to the local proxy

Don't change configuration files or global environment variables yet. Run the command below to test a single request. -q must be the first option to skip the default curl configuration file. --noproxy "" temporarily clears the bypass list for this request so existing NO_PROXY settings don't interfere. In Windows PowerShell, use curl.exe to avoid invoking the command with the same name in Windows PowerShell 5.1.

curl -q -v --connect-timeout 5 --max-time 15 --noproxy "" \
  --proxy http://127.0.0.1:7890 https://example.com/

The command above is for shells such as Bash and Zsh. Older versions of PowerShell may not pass an empty argument to external programs as expected. In Windows, run this one-line version in Command Prompt:

curl.exe -q -v --connect-timeout 5 --max-time 15 --noproxy "" --proxy http://127.0.0.1:7890 https://example.com/
  • Connection refused when connecting to 127.0.0.1:7890: The request hasn't reached the routing rules. Check that the client is running, the active configuration has this listening port enabled, and the command and client are on the same network.
  • Connected to the local port, but CONNECT example.com:443 fails: First make sure you're using an HTTP or mixed port. Then check the client's logs for destination resolution, the outbound selected by the rules, and the upstream connection. If you get 407, check whether the local proxy requires authentication.
  • You see 200 Connection established, followed by a TLS error: The HTTP proxy tunnel is established; the failure occurs during the next handshake. Check the system clock, certificate trust, and client logs. Don't disable certificate verification to prove the proxy works.

The proxy URL is http://127.0.0.1:7890 because curl uses the HTTP proxy protocol to connect to the local proxy. The destination is still https://example.com/; curl creates a tunnel with CONNECT. If you only have a SOCKS port, such as 7891, change the proxy argument to --proxy socks5h://127.0.0.1:7891 so the proxy resolves the destination hostname.

Terminal environment variables: test with a command before keeping them

Bash and Zsh: set variables for a single command

http_proxy=http://127.0.0.1:7890 \
>https_proxy=http://127.0.0.1:7890 \
>no_proxy=localhost,127.0.0.1 \
>curl -q -v --connect-timeout 5 --max-time 15 https://example.com/

These assignments apply only to this curl command and won't change the environment for later commands in the current shell. For HTTP URLs, curl accepts only lowercase http_proxy; don't set only uppercase HTTP_PROXY. Choose the https_proxy variable based on the URL's protocol, but set its value to a protocol supported by your local proxy. ALL_PROXY can be used as a fallback when a proxy isn't set for the relevant protocol.

PowerShell: test in a temporary window

$env:http_proxy = 'http://127.0.0.1:7890'
$env:https_proxy = 'http://127.0.0.1:7890'
$env:no_proxy = 'localhost,127.0.0.1'
curl.exe -q -v --connect-timeout 5 --max-time 15 https://example.com/

Open a temporary PowerShell window and run the command there. The variables apply only to that PowerShell process and any child processes it starts; closing the window ends the test. Windows environment variable names are case-insensitive, so there's no need to set both cases. If curl connects when you pass --proxy explicitly but doesn't try the local port when using variables, check whether no_proxy matches the destination domain—for example, whether it's set to *.

Requests reach Clash: check rules, policy groups, and outbound routes

Find the same request in the client's connection log. Check the matched rule first, then the final outbound. In rule mode, rules are usually evaluated in configuration order, and the first match determines which outbound or policy group handles the request. A DIRECT match means the traffic reached the client but was routed directly. A policy group match doesn't necessarily mean traffic went through a proxy node—the group's current selection may itself be DIRECT.

What you seeWhat to check next
Explicit curl command appears in the log; browser request doesn'tCheck the browser's proxy source, extensions, and domain exceptions.
Explicit curl command appears in the log; environment-variable test doesn'tCheck the current process's variables, no_proxy, and the tool's own proxy settings.
Both requests appear in the log, but match DIRECTCheck the first rule matching the domain and the policy group's current selection.
Both requests appear in the log; connection still times out after selecting a nodeUse the client log to distinguish a DNS resolution failure from an upstream connection failure, then test another available node in the same group.

To compare public egress IPs, make two new requests to the same IP lookup service and check each request's rule and outbound in the connection log. Don't compare results from different domains: the IP lookup domain may match a direct rule, while the service domain you're troubleshooting matches a proxy rule. Avoid enabling TUN as a shortcut during troubleshooting. TUN can capture traffic that matches its configuration at the network layer, making tools that ignore the system proxy appear in the connection log, but that doesn't prove they read the environment variables.