Loading...
Loading...
Troubleshoot and resolve common issues with the ClickHouse Node.js client (@clickhouse/client). Use this skill whenever a user reports errors, unexpected behavior, or configuration questions involving the Node.js client specifically — including socket hang-up errors, Keep-Alive problems, stream handling issues, data type mismatches, read-only user restrictions, proxy/TLS setup problems, or long-running query timeouts. Trigger even when the user hasn't precisely named the issue; vague symptoms like "my inserts keep failing" or "connection drops randomly" in a Node.js context are strong signals to use this skill. Do NOT use for browser/Web client issues.
npx skill4agent add clickhouse/clickhouse-js clickhouse-js-node-troubleshooting⚠️ Node.js runtime only. This skill covers thepackage running in a Node.js runtime exclusively — including Next.js Node runtime API routes, React Server Components, Server Actions, and standard Node.js processes. Do not apply this skill to browser client components, Web Workers, Next.js Edge runtime, Cloudflare Workers, or any usage of@clickhouse/client. For browser/edge environments, the correct package is@clickhouse/client-web.@clickhouse/client-web
| Issue | Symptoms | Reference file |
|---|---|---|
| Socket Hang-Up / ECONNRESET | | |
| Data Type Mismatches | Large integers returned as strings, decimal precision loss, Date/DateTime insertion failures | |
| Read-Only User Errors | Errors when using response compression with | |
| Proxy / Pathname URL Confusion | Wrong database selected, requests failing behind a proxy with a path prefix | |
| TLS / Certificate Errors | TLS handshake failures, certificate verification issues, mutual TLS setup | |
| Compression Not Working | GZIP compression not activating for requests or responses | |
| Logging Not Showing Anything | No log output, need custom logger integration | |
| Query Parameters Not Interpolated | Parameterized queries not working, SQL injection concerns | |