Skip to content

Instantly share code, notes, and snippets.

@Choumingzhao

Choumingzhao/WSL2_clash.md

Last active August 14, 2021 07:43
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save Choumingzhao/0a5d88ca81148ab74e2d4a1fffba5778 to your computer and use it in GitHub Desktop.
Save Choumingzhao/0a5d88ca81148ab74e2d4a1fffba5778 to your computer and use it in GitHub Desktop.
Download ZIP
When WSL2 cannot connect to local `Clash for Windows`
Raw
WSL2_clash.md

There're many posts about open setttings for Clash for Windows. But following solution actually help with the problem.

This solve the problem by simply adding a new firewall rule, which is the most efficient soluton..

@Choumingzhao
Copy link
Author

To avoid the problem, you may also consider switch to WSL1(Ubuntu for example) using
wsl --set-version Ubuntu 1

This way, you can connect to your Clash for Windows by setting http_proxy or ALL_PROXY to http://127.0.0.1:7890.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment