Local utilities

Write less. Avoid mistakes.

Generate import links and process rules, then collect safe diagnostic information. All input stays in your browser.

URL Scheme

Import link generator

Encode a subscription URL into a link ClashFX can open. Subscription URLs are sensitive—never share the result.

Rule generator

Route by process

Enter the actual macOS executable name to generate a ClashFX PROCESS-NAME rule.

Find the name with ls /Applications/App.app/Contents/MacOS/. Use the returned filename—not the display name or bundle identifier.
Troubleshooting

Locate first.
Change second.

Test the base network, system proxy, node, configuration, and TUN in that order so each result narrows the cause.

01

Check base networking

Turn off the system proxy and Enhanced Mode. If networking still fails, the cause is outside ClashFX.

02

Test only system proxy

Choose a known working node and enable only the system proxy.

03

Then enable TUN

If failure begins now, inspect permissions, DNS, other VPNs, and old extensions.

Read-only diagnostic commands

Check the processConfirm ClashFX is running
ps aux | grep ClashFX
Check listening portsFind default port conflicts
lsof -nP -iTCP -sTCP:LISTEN | grep -E 'ClashFX|7890|7891'
Inspect system DNSCompare DNS before and after TUN
scutil --dns | grep nameserver
Open the config directoryOfficial default: ~/.config/clashfx
open ~/.config/clashfx
Diagnostics may contain usernames, subscription URLs, node addresses, or IPs. Redact them before posting publicly.