BB SkillsFind a workflow. Make it your own.
Create account
New here? Start with the guide ↗
Browse sections ＋
Library / Development / ClickHouse Node.js Client Troubleshooting
{ }
Resource profile / ClickHouse Node.js Client Troubleshooting
About this skill

Workflow & requirements

ClickHouse Node.js Client Troubleshooting

Reference: https://clickhouse.com/docs/integrations/javascript

⚠️ Node.js runtime only. This skill covers the @clickhouse/client package 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-web. For browser/edge environments, the correct package is @clickhouse/client-web.

How to Use This Skill

  1. Identify the issue — match symptoms to the Issue Index below and read the corresponding reference file.
  2. Lead with the diagnosis — explain what's likely causing the issue before giving the fix.
  3. Note version constraints — flag if a fix requires a minimum client version and check it against what the user provided.
  4. Ask only what's missing — if the fix is version-dependent and you don't know their version, ask; otherwise help immediately.

Issue Index

Identify the user's issue from the list below and read the corresponding reference file for detailed troubleshooting steps.

Issue Symptoms Reference file
Socket Hang-Up / ECONNRESET socket hang up, ECONNRESET, intermittent connection drops, long-running queries timing out reference/socket-hangup.md
Data Type Mismatches Large integers returned as strings, decimal precision loss, Date/DateTime insertion failures, CANNOT_PARSE_INPUT_ASSERTION_FAILED inserting a UUID into a UInt128 column reference/data-types.md
Read-Only User Errors Errors when using response compression with readonly=1 users reference/readonly-users.md
Proxy / Pathname URL Confusion Wrong database selected, requests failing behind a proxy with a path prefix reference/proxy-pathname.md
TLS / Certificate Errors TLS handshake failures, certificate verification issues, mutual TLS setup reference/tls.md
Compression Not Working GZIP compression not activating for requests or responses reference/compression.md
Logging Not Showing Anything No log output, need custom logger integration reference/logging.md
Query Parameters Not Interpolated Parameterized queries not working, SQL injection concerns reference/query-params.md
FORMAT Clause / SHOW POLICIES Errors Syntax error from a duplicate FORMAT, or SHOW [ROW] POLICIES failing even with a format provided reference/query-format-clause.md

Still Stuck?

PACKAGE TRANSPARENCY

Inspect before installing

Source: ClickHouse · Apache-2.0 · SHA-256 shown alongside the download.

18 files33342 ZIP bytes0 script/code files

License file included. A license and checksum are not a security certification. Review package instructions and scripts before running them.

View files and uncompressed sizes

An adaptation record is bundled. Inspect the declared changes and archived original before use. Review adaptation and original-file hashes →

Machine-readable installation guide →
CATALOG REVIEW NOTES

Know what you need before installing

Source and packaging checks recorded on 2026-10-03. These notes are not safety certification or measured task performance.

Requirements

A supported Node.js runtime, @clickhouse/client and authorized ClickHouse HTTP(S) access. Exact codec/logging/socket options depend on installed version. Supply trusted certificates and keep credentials out of logs.

Costs, access & practical limits

Apache-2.0 material; separate hosting, tooling, model access and services may have costs. Full skill/agent runtime evaluation has not been performed. Compression and integer-precision defaults corrected with originals retained. Header-duration tables are approximate budgets, not service guarantees. Closing connections is not a delivery or completion guarantee. TLS verification bypass is an upstream development-only example, never a production fix. Examples do not reproduce your proxy, authentication or workload. No cloud account configured.

View the recorded checks
  • Pinned original bytes verified against Git blob hashes
  • Complete Apache-2.0 license and publisher NOTICE retained
  • Core identity and local references validated
  • Selected Node client configuration and version boundaries reviewed; limitations disclosed

Upstream commit: 356a8c1b9a7392adb389a132f5ad3fec38532a03

Runtime status: not tested by this catalog. Configure your client and test the skill in your own environment.

SCENARIOS

Inputs, criteria and recorded outcomes

Records are supplied by the site administrator and bound to a specific package. They are not third-party safety certification. This page does not execute skills.

No published scenario records yet. Resource availability and download counts do not imply measured task performance.

Community reviews

★ New

Be the first to share your experience.

Sign in to leave a review →

More to explore

View all ↗