node-redis: ClientClosedError: The client is closed
A command was sent through a node-redis client that was never connected, was quit(), or disconnected.
ClientClosedError: The client is closedThe client is closed node-redisError: The client is closedClientClosedError node-redis v4Error: Socket closed unexpectedly Meaning
In node-redis v4 you must await client.connect() before commands and handle client.on('error'). Don't call commands after quit()/disconnect(). Create one client at startup, reuse it, and in serverless re-use across invocations.
Common causes
connect()not called/awaited- Commands after
client.quit() - Client created per request and closed
- Connection error closing it without reconnect strategy
- Missing error listener causing crash
⚡ Quick fix
const client = createClient({ url }); client.on("error", console.error); await client.connect();- Reuse a singleton client
- Don't quit before pending commands finish
Detailed fix by platform
Node.js
import { createClient } from "redis"; const client = createClient({ url: process.env.REDIS_URL }); client.on("error", e => console.error(e)); await client.connect();
How to diagnose
- connect — Awaited?
- Lifecycle — Closed early?
- Listener — error handler?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- BullMQ: Missing lock for job / job stalled more than allowable limit BullMQ: Error: Missing lock for job 42. moveToFinished / job stalled more than allowable limit
- BUSY Redis is busy running a script Redis: (error) BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE
- Celery with Redis: tasks run twice (visibility_timeout) Celery: Task executed twice / Restoring unacked messages — Redis broker visibility_timeout shorter than task ETA
Most viewed in Redis
- READONLY You can't write against a read only replica Redis: READONLY You can't write against a read only replica
- MISCONF Redis: MISCONF Redis is configured to save RDB snapshots, but it's currently unable to persist to disk
- OOM command not allowed Redis: OOM command not allowed when used memory > 'maxmemory'
Other ways to find it
Where this error sits
Origin: Data. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 5 Nov 2026