Clash System Proxy Not Working? Fix Browser Extension Conflicts and Terminal Proxy Settings
Troubleshoot browser proxy extensions and system settings, then check terminal proxy variables and how command-line tools handle them.
Test the local proxy port first, then check app settings
The client’s System Proxy switch writes the operating system’s proxy settings; it does not route every process through Clash. Troubleshoot the two links separately: whether the app connects to a local proxy listener, and which outbound the rules select after the request reaches the core. A browser that cannot load pages, a timed-out terminal command, and an unchanged public IP may each point to a different failure point.
First, check the current listening port in the client’s port settings. The examples below use mihomo’s mixed-port: 7890, which accepts both HTTP and SOCKS proxy requests. 7890 is only an example, not a universal default. If your config uses separate port and socks-port settings, use the HTTP listener’s port in the commands below. Don’t use the external-controller port.
curl -v --connect-timeout 5 --max-time 15 --noproxy "" --proxy http://127.0.0.1:7890 https://example.com/
On Windows, use curl.exe to avoid older Windows PowerShell versions interpreting curl as an alias. Older PowerShell versions may also drop empty-string arguments passed to external programs. If the command fails with an argument error, run it in Command Prompt, starting with curl.exe. Here, --noproxy "" clears any inherited proxy bypass list for this test.
- If a connection to
127.0.0.1:7890is refused immediately, check that the core process is running, confirm the listening port, and make sure the command and client are in the same network environment. A host and a container have separate loopback addresses. - If verbose output shows a connection to the local port and a
CONNECT example.com:443request, the request reached the HTTP proxy. If it fails later, troubleshoot that stage: check core logs for a failed CONNECT; if the tunnel is established but certificate validation fails, check the clock, certificate chain, and network intermediaries. Don’t disable certificate validation to mask the problem. - If the request succeeds, check the client’s connection log for the destination domain and outbound. A
DIRECTmatch still means the request entered through the proxy; the core simply chose a direct connection. An unchanged public IP does not prove the system proxy is broken.
Browser troubleshooting: check extensions, then verify system proxy settings
Use only one source for proxy settings at a time
Open chrome://extensions/ in Chrome or edge://extensions/ in Edge. Start by disabling extensions that switch proxies, route traffic by domain, or set a PAC file. An extension’s Direct option usually explicitly bypasses the proxy; it does not mean “Use system settings.” To keep an extension enabled, select its system proxy mode and make sure no other extension is also controlling proxy settings.
Reload the target page and check the client’s connection log to confirm a new request was made. If needed, fully quit and restart the browser to avoid reusing an existing connection. Don’t rely on Incognito or InPrivate mode alone to rule out extensions: some extensions can run in private windows, and device policies still apply. If settings are managed by your organization, check the active policies at chrome://policy/ or edge://policy/. Contact your administrator for managed devices.
Check operating system settings and Firefox’s separate proxy settings
- Windows 11: Open Settings → Network & internet → Proxy, then check the address and port under Manual proxy setup. Note whether a setup script is also enabled or the target domain appears in the exceptions list. If only one domain is affected, check the exceptions list before reinstalling the client.
- macOS: Open System Settings → Network → your active network service → Details → Proxies. Check the service’s web proxy, secure web proxy, automatic proxy configuration, and bypass list. If you switch between Wi-Fi and Ethernet, make sure you’re checking the active service’s settings.
- Firefox: Open Settings → General → Network Settings → Settings…. To test the system proxy, select Use system proxy settings. If Manual proxy configuration or Automatic proxy configuration URL is selected, troubleshoot the address, script, and exceptions configured there instead; the system proxy switch alone won’t tell you what Firefox is using.
If the system proxy address reverts as soon as it’s set, record its values before and after toggling the switch. Then check whether another proxy client, network management app, or organization policy is updating it. Find out what is changing the setting before running multiple clients or repeatedly switching rule modes.
Terminal troubleshooting: compare default and explicit proxy requests
If the browser works but the terminal doesn’t, run the explicit proxy command above in the same terminal, against the same destination. Then run curl -v https://example.com/. If the explicit proxy request succeeds but the default request connects directly to the destination, first check how the tool reads proxy environment variables. The following temporary settings are for a POSIX shell and apply only to the current shell and processes it starts:
export http_proxy=http://127.0.0.1:7890
export https_proxy=http://127.0.0.1:7890
curl -v https://example.com/
The destination uses HTTPS, but the proxy URL still starts with http://: the former is the destination protocol; the latter is the protocol used to connect to the local proxy. For HTTP requests, curl recognizes lowercase http_proxy; for HTTPS requests, it also supports uppercase HTTPS_PROXY. If both uppercase and lowercase versions are set, check that their values match. Don’t assume every tool resolves conflicts the same way.
$env:http_proxy = 'http://127.0.0.1:7890'
$env:https_proxy = 'http://127.0.0.1:7890'
curl.exe -v https://example.com/
The commands above set variables for the current Windows PowerShell process. IDEs, background services, containers, and other terminals that are already running won’t inherit these changes. If curl works in the terminal but an IDE still can’t fetch, check the proxy settings in the environment that actually launches the task. For Git, run git config --show-origin --get-all http.proxy to check for a separate setting and see which file it comes from. Don’t post proxy variables containing credentials or unredacted logs in public support forums.
Only one domain fails? Check bypass lists and core rules separately
no_proxy or NO_PROXY takes effect on the app side. For example, if curl reads localhost,127.0.0.1,example.com, requests to example.com bypass the configured proxy. Test the same URL with a normal request and with an explicit request using --noproxy "". If only the normal request skips the local port, check environment variables and the tool’s own exclusions. Don’t permanently clear a company network’s bypass list just to fix one domain.
Core rules take effect after a request reaches Clash. In the connection log, compare the request time, domain, matched rule, and outbound chain. If the request matches DIRECT, check whether that rule appears before the rule you expected to match. If it matches a proxy group but the connection fails, check the group’s selected option and whether that outbound is reachable. In rule mode, rules are usually evaluated in order, so an overly broad rule near the top can prevent more specific rules below it from matching.
Retest after the fix: verify both paths with the same destination
- Keep the verified local port and choose a URL that was failing. Visit it in the browser using your usual setup, then access it from the terminal with a command that doesn’t include
--proxy. Check the client’s connection log for both requests; don’t rely only on whether the page loads. - If the browser request is missing from the log, recheck extensions, policies, system scripts, and browser exceptions. If the terminal request is missing, recheck environment variables, tool settings, and where the process is running. If both requests appear, investigate the outbound or destination service next.
- Closing the temporary test terminal discards its environment variable changes. If you changed persistent settings, use your notes to restore anything you no longer need. Reopen the terminal and browser you actually use, then test again to make sure the fix doesn’t depend on an old window.
If the retest still fails, note your operating system, client and core versions, inbound type and port, and whether the failure occurs during the local connection, CONNECT, TLS, or destination response. For config field definitions, see the configuration reference. Sharing these details when asking for help is much more useful than simply saying “the proxy is on, but traffic isn’t going through.”