This is a lookup table: see an error on the Logs page, find it here. Formats vary slightly across core versions - match on the keywords.
Connection errors
| Keyword | Meaning and fix |
|---|
dial tcp ... i/o timeout | Destination (or node) timed out. Sporadic: ignore. Clustered: identify the node, switch, or run the all-timeout flow. |
connect: connection refused | The target port refused. Node port changed (update the subscription) or the destination service is down. |
EOF / connection reset by peer | The far end cut the connection. One site: it blocks that node's IP - switch nodes. All sites: node or line interference. |
no such host | Name resolution failed. Check DNS config; or the domain is simply wrong/defunct. |
use of closed network connection | Normal noise during switches (nodes changed, connections closed en masse). Ignore. |
Startup and config errors
| Keyword | Meaning and fix |
|---|
bind: address already in use | Port conflict - see the port guide. |
yaml: line N: mapping values are not allowed | YAML syntax error at line N (indentation or a missing space after a colon, usually). |
proxy N: unsupport proxy type / unknown field | The config contains a protocol or field this core doesn't know (subscription added newer node types). That node is skipped, the rest work; mass omissions → see the core-version guide. |
rule ... error: proxy [X] not found | A rule references a nonexistent group name (renamed the group, not the rules) - the whole profile fails to load. |
start tun interface error | TUN failed to start - see TUN issues. |
Subscription and provider errors
| Keyword | Meaning and fix |
|---|
provider ... initial failed / update failed | A rule-set or node provider failed to download. Its URL usually needs the proxy: connect through any node, then reload the profile. |
404 / 403 / 429 (during subscription update) | Link dead, banned or rate-limited - see subscription failures. |
Three habits for reading logs
- Read timestamps: only the seconds around your reproduction matter; stale errors mislead.
- Look for repetition: the same error against the same target, over and over, is diagnostic; a single line rarely is.
- Cross-check with Connections: log says timeout → the Connections row shows which rule and node carried it. When the two line up, the cause is in hand.
Tip: for anything not listed, search the English error text (minus IPs and ports) - all Clash-family clients share the core's messages, and community coverage is extensive.
