Proxy Config Reference

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 stringClientFails at
set system dns failed: exit code 1Clash Verge RevDNS rewrite
the remote profile data is invalid yamlClash Verge RevProfile fetch/parse
An attempt was made to access a socket in a way forbidden by its access permissionsClash Verge RevProfile activation
program not found / repeated "Install Service"Clash Verge RevService install
service and cores not satisfiedClash Verge RevRuntime mode
IPC timeout on first core startClash Verge RevCore IPC handshake
System proxy on, no internetClash Verge RevTraffic takeover
TUN on, no internetClash Verge RevTUN / routing
failed to open geosite.datv2rayNRule file load
ArgumentOutOfRange_Countv2rayNSubscription parse
Failed to import subscription contentv2rayNImport / gzip
运行Core失败 / bind: address already in usev2rayNCore start
allowInsecure has been removedv2rayNGTLS config migration
unknown field "tunnel-per-resolver"HiddifyConfig schema
netip.ParsePrefix("/24"): ParseAddr(""): unable to parse IPHiddifyWARP outbound build
exit status 127HiddifyLinux TUN helper
HiddifyCli.exe requires elevationHiddifyWindows privilege
auto_redirect → operation not supportedsing-boxLinux TUN / nftables
Remote rule-set download failedsing-boxRule-set fetch
configuration file config.yaml is emptyFlClashProfile switch

What each stage means

StageWhat it rules out
DNS rewriteNot the subscription, not the node. The client failed while changing the system DNS setting.
Profile fetch / parseThe download or the YAML/JSON parse failed. Node health is irrelevant.
Service installThe helper service is missing or blocked. Nothing downstream can work until it is installed.
Core IPC handshakeThe GUI started but the core did not report ready. Usually a leftover process or a locked port.
Traffic takeoverSystem proxy or TUN is not actually capturing traffic. Compare with the client fully off.
Rule file loadA data file is missing or from a mismatched version.
Subscription parseThe payload is not in the format the client expects — often base64 when YAML was assumed.
Core startThe core binary failed or its listen port is taken.
Config schemaThe config contains a field this version rejects — check the version before editing values.
TUN helper / privilegeThe 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.