A setup usually fails at one of four stages, and each stage has its own error text. The installer returns a permissions error. The import returns a parse error. The capture mode fails to create its adapter. Or everything reports success and nothing loads because the rules sent the traffic somewhere it cannot go. These pages follow that order, because the log line you are looking at belongs to exactly one of them.
Clients covered
Clash Verge Rev: profiles, service mode and TUN, in order
What the profile system does, why service mode exists, and the three checks that separate a broken profile from a broken core.
Windows · macOS · LinuxFlClash: profiles and the empty-list problem
A cross-platform Clash client. What overwrites a profile, why the list empties after a switch, and how to verify before changing anything.
Windows · macOS · Linux · AndroidHiddify: import a configuration, then choose a capture mode
What the app expects as input, why VPN and system-proxy modes differ, and the first error worth reading on each platform.
Windows · macOS · Linux · Android · iOSKaring: from import to a verified connection
A cross-platform client that reads several subscription shapes. Format first, then capture mode, then one real request to verify.
Windows · macOS · Linux · Android · iOSShadowrocket: importing a subscription on iPhone or iPad
It is a client, not a service. What the import paths accept, how the global and rule modes differ, and what an empty node list means.
iOS · iPadOS (paid)sing-box: reading a configuration by its objects
Inbound, outbound, route and DNS. Why a valid JSON file can still fail, and how a remote rule set stops a core before any route exists.
CLI, all platformsStash: reading a configuration before trusting it
A Clash-compatible client for Apple platforms. What the remote configuration does, and why an override can empty a working proxy list.
iOS · iPadOS (paid)Surge: how a configuration actually decides traffic
Four sections decide everything: general, proxies, policy groups, rules. Most “node works but traffic goes direct” is a rule pointing at the wrong group.
macOS · iOS (paid)v2rayN on Windows: from download to a verified connection
Where the Windows build comes from, what the profile list does and does not prove, and the three states to check before blaming a node.
Windows · macOS · Linuxv2rayNG on Android: input format first, then connection
A share link, a Base64 subscription and a Clash YAML are three different inputs. Importing the wrong one looks like a network failure.
AndroidWhich client, by platform
| Client | Platforms |
|---|---|
| Clash Verge Rev | Windows · macOS · Linux |
| FlClash | Windows · macOS · Linux · Android |
| Hiddify | Windows · macOS · Linux · Android · iOS |
| Karing | Windows · macOS · Linux · Android · iOS |
| Shadowrocket | iOS · iPadOS (paid) |
| sing-box | CLI, all platforms |
| Stash | iOS · iPadOS (paid) |
| Surge | macOS · iOS (paid) |
| v2rayN on Windows | Windows · macOS · Linux |
| v2rayNG on Android | Android |
The four stages, in order
- Install. The binary, the helper service and the core are three different things. A failure in any of them looks identical in the UI.
- Import. Fetch, parse and apply are separate steps. An import error names one of them, and the fix is different in each case.
- Capture. System proxy and TUN are not the same interception point. Applications that ignore the system proxy will not see the first one at all.
- Verify. Connected is a UI state. The check that matters is whether the exit address changed and whether name resolution still works.
If you already have an error string and want the guide that matches it exactly, the error string index lists each log line against the stage it points at.
Tools
Converting share links into a configuration does not need an upload: the vmess / ss / trojan / vless to Clash converter runs in the browser and keeps the links on your own machine.
Nothing on this site hosts subscriptions, node addresses or configuration files you can connect with, and nothing here sells a plan. When a certificate cannot be verified, the advice is to stop using that node, not to disable verification.