Node HandbookNODE HANDBOOK中文
English reference

Proxy client error strings, explained by the stage that fails

Clash Verge Rev, v2rayN, v2rayNG, Hiddify, sing-box and FlClash. Each guide quotes the error verbatim, says which step broke, and marks where the public evidence stops.

Most troubleshooting pages tell you to change something and hope. These start from the actual error text and the client's own code path: whether the request was even fetched, whether the body parsed, whether the core started, whether the tunnel rules were accepted. That distinction decides which fix is worth trying — and which one quietly destroys your working profile.

Where a public upstream issue exists, it is cited with its number and the platform it came from. Where it is a single report, it says so. No claim here is extended beyond the evidence behind it.

All English guides (12)

set system dns failed: exit code 1 — Clash Verge Rev

Config validation passes, then Clash Verge Rev fails to set the system DNS. Which stage actually fails, how to separate TUN from system proxy, and where Issue #8328 stops being evidence.

the remote profile data is invalid yaml — Clash Verge

Clash Verge Rev checks the HTTP status first, then parses the body as YAML, then looks for proxies. Which branch produced your error, and what each one rules out.

Clash Verge Rev service install failed — Is Admin false, program not found

The service prompt keeps coming back. How to read Is Admin and Running Mode, what program not found and the 'service and cores' error actually mean, and when to stop reinstalling.

cannot select profile: socket error in Clash Verge Rev — HNS check

A profile is imported but clicking it fails with 'An attempt was made to access a socket in a way forbidden by its access permissions'. The official FAQ points at Host Network Service — here is how to check it without deleting your profiles.

core IPC pipe did not become ready within 15s — Clash Verge Rev

The first service core start times out after 15 seconds, then the automatic retry succeeds and the proxy works. What that log actually proves, and how to tell it apart from a core that never really started.

Clash Verge Rev TUN mode not working — connected but no internet

System proxy works, TUN does not. A three-state baseline, then service permissions, the virtual adapter, default route conflicts and DNS — one change per round, with the log evidence to match.

failed to open geosite.dat — v2rayN core won't start

v2rayN says only 'Failed to run Core'. The actual cause sits in the line above it: a missing geosite.dat, a truncated file ending in EOF, or a port conflict in a different file.

allowInsecure has been removed — v2rayNG TLS failure

Failed to build TLS config, then 'allowInsecure has been removed'. Why the field is rejected, how to tell it apart from a real certificate error, and what you must not switch off.

ArgumentOutOfRange_Count after a v2rayN update

The fetch succeeded, then the import threw ArgumentOutOfRange_Count. How to separate fetch, parse and apply, and how to avoid overwriting nodes you still have.

sing-box auto_redirect: nftables operation not supported

TUN starts, then nftables rejects a rule with 'operation not supported'. How to split the log by stage, what Issue #4588 actually shows, and when to stop testing.

config.yaml is empty — FlClash profile switch fails

Switching profiles in FlClash reports 'config.yaml is empty'. Which versions the fix covers, what the v0.9.0 breaking change means, and how to keep a restore point.

Hiddify WARP: netip.ParsePrefix error, empty IP

error patching outbound ... netip.ParsePrefix("/24"): ParseAddr(""): unable to parse IP. What the empty address means, and why it does not mean your nodes are dead.

Prefer a table?

The error string index lists every error by exact text, the client it belongs to, and the stage it points at.

About the source

These pages are English editions of material maintained on the Chinese site jiedianshouce.com. The same error index is also published as a GitHub repository: clash-error-codes.

What this site does not do

It does not host subscriptions, node addresses, tokens or configuration files you can connect with. It does not sell provider plans. When a certificate cannot be verified, the advice is to stop using that node, not to disable verification.