20 proxy client error strings — client, failure stage, first fix
Each entry states where the failure happens, not just what it says. Most of these fail before traffic ever reaches a node, which is why "reinstall it" and "change your node" are the two most common wrong answers.
Read this before you change anything
Save the first error line, verbatim. The first error is the cause; the lines after it are usually cascade. Copy it including the code and any quoted path.
Change one variable per round. Reinstalling, deleting the profile and switching nodes in the same session destroys the evidence you need.
Redact before you post. Subscription URLs, tokens, node passwords and unmasked logs are credentials. Redact them before pasting into an issue.
mihomo -t -f config.yaml # rule out the config first — cheapest test
sing-box check -c config.json
| Error string | Client | Fails at |
|---|---|---|
set system dns failed: exit code 1 | Clash Verge Rev | DNS rewrite |
the remote profile data is invalid yaml | Clash Verge Rev | Profile fetch/parse |
An attempt was made to access a socket in a way forbidden by its access permissions | Clash Verge Rev | Profile activation |
program not found / repeated "Install Service" | Clash Verge Rev | Service install |
service and cores not satisfied | Clash Verge Rev | Runtime mode |
IPC timeout on first core start | Clash Verge Rev | Core IPC handshake |
System proxy on, no internet | Clash Verge Rev | Traffic takeover |
TUN on, no internet | Clash Verge Rev | TUN / routing |
failed to open geosite.dat | v2rayN | Rule file load |
ArgumentOutOfRange_Count | v2rayN | Subscription parse |
Failed to import subscription content | v2rayN | Import / gzip |
运行Core失败 / bind: address already in use | v2rayN | Core start |
allowInsecure has been removed | v2rayNG | TLS config migration |
unknown field "tunnel-per-resolver" | Hiddify | Config schema |
netip.ParsePrefix("/24"): ParseAddr(""): unable to parse IP | Hiddify | WARP outbound build |
exit status 127 | Hiddify | Linux TUN helper |
HiddifyCli.exe requires elevation | Hiddify | Windows privilege |
auto_redirect → operation not supported | sing-box | Linux TUN / nftables |
Remote rule-set download failed | sing-box | Rule-set fetch |
configuration file config.yaml is empty | FlClash | Profile switch |
What each stage means
| Stage | What it rules out |
|---|---|
| DNS rewrite | Not the subscription, not the node. The client failed while changing the system DNS setting. |
| Profile fetch / parse | The download or the YAML/JSON parse failed. Node health is irrelevant. |
| Service install | The helper service is missing or blocked. Nothing downstream can work until it is installed. |
| Core IPC handshake | The GUI started but the core did not report ready. Usually a leftover process or a locked port. |
| Traffic takeover | System proxy or TUN is not actually capturing traffic. Compare with the client fully off. |
| Rule file load | A data file is missing or from a mismatched version. |
| Subscription parse | The payload is not in the format the client expects — often base64 when YAML was assumed. |
| Core start | The core binary failed or its listen port is taken. |
| Config schema | The config contains a field this version rejects — check the version before editing values. |
| TUN helper / privilege | The OS refused the privileged operation. Not a config problem. |
Full walkthroughs with commands, screenshots and stated evidence boundaries: jiedianshouce.com. Each entry there says whether the fix was verified in-house or only reproduced from a report — that distinction is kept deliberately.