ERR unknown command Redis Origin: Data OSI layer 7 · Application Last updated 5 Nov 2026

Redis: (error) ERR unknown command 'JSON.GET', with args beginning with: / unknown command 'FT.SEARCH'

The server doesn't know the command — wrong name, newer Redis version, or a missing module.

Exact message you may see ERR unknown command 'JSON.GET', with args beginning with:(error) ERR unknown command 'FT.CREATE'ReplyError: ERR unknown command `JSON.SET`, with args beginning with:ERR unknown command 'CONFIG' redisredis.exceptions.ResponseError: unknown command
Explore the map of this error Full error map →
Seen on: Redis Node.js

Meaning

Check the spelling and version (INFO server). Module commands (JSON.*, FT.*, TS.*, BF.*) need Redis Stack or the module loaded (MODULE LIST). Managed Redis (ElastiCache, Azure) often disables some commands (CONFIG, KEYS, FLUSHALL) or renames them (rename-command).

Common causes

  • Module not installed/loaded (RediSearch, RedisJSON)
  • Command from a newer Redis version
  • Command disabled/renamed by the provider or config
  • Typo
  • Using Valkey/other fork differences

⚡ Quick fix

  1. MODULE LIST and install Redis Stack or load the module
  2. Check INFO server redis_version vs command docs
  3. Use allowed alternatives on managed services (e.g. SCAN instead of KEYS)

Detailed fix by platform

Linux

  1. redis-cli MODULE LIST; redis-cli INFO server | grep redis_version

How to diagnose

  1. Module — Loaded?
  2. Version — New enough?
  3. Provider — Command disabled?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Data. Errors that are often confused with or caused by this one (click to open):

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 (Redis)BullMQ: Missing lock …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 (Redis)BUSY Redis is busy ru…Celery with Redis: tasks run twice (visibility_timeout) — Celery: Task executed twice / Restoring unacked messages — Redis broker visibility_timeout shorter than task ETA (Redis)Celery with Redis: ta…ERR CONFIG SET failed (possibly related to argument) — Redis: (error) ERR CONFIG SET failed (possibly related to argument 'maxmemory') - can't set immutable config (Redis)ERR CONFIG SET failed…ERR value is not an integer or out of range — Redis: (error) ERR value is not an integer or out of range (Redis)ERR value is not an i…ERR wrong number of arguments / syntax error — Redis: (error) ERR wrong number of arguments for 'set' command / ERR syntax error (Redis)ERR wrong number of a…ERR_IMPORT_ATTRIBUTE_MISSING — TypeError [ERR_IMPORT_ATTRIBUTE_MISSING]: Module needs an import attribute of "type: json" (Node.js)ERR_IMPORT_ATTRIBUTE_…ERR_PACKAGE_PATH_NOT_EXPORTED — Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './x' is not defined by "exports" (Node.js)ERR_PACKAGE_PATH_NOT_…ERR unkno…

Explore the map of this error Full error map →

🧠 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.