| Error string | Client | Guide |
|---|---|---|
set system dns failed: exit code 1 | Clash Verge Rev | Open guide |
the remote profile data is invalid yaml | Clash Verge Rev | Open guide |
failed to open geosite.dat | v2rayN | Open guide |
allowInsecure has been removed | v2rayN | Open guide |
Hiddify WARP: netip.ParsePrefix error, empty IP | Hiddify | Open guide |
ArgumentOutOfRange_Count after a v2rayN update | v2rayN | Open guide |
config.yaml is empty | FlClash | Open guide |
sing-box auto_redirect: nftables operation not supported | sing-box | Open guide |
Clash Verge Rev service install failed | Clash Verge Rev | Open guide |
cannot select profile: socket error in Clash Verge Rev | Clash Verge Rev | Open guide |
core IPC pipe did not become ready within 15s | Clash Verge Rev | Open guide |
Clash Verge Rev TUN mode not working | Clash Verge Rev | Open guide |
How to use this index
Copy the first error line from your client log — not the summary alert at the top. If the text matches a row here, open that guide and check the stage table before applying any step. If it does not match, the fault is probably in an earlier stage: an HTTP status, a timeout, or a port already in use.
Missing an error?
The Chinese site covers more cases. The GitHub repository clash-error-codes takes corrections and additions as issues or pull requests.
Related
All English guides · Client comparison matrix · Subscription format notes