This means Redis does not recognise the command you sent, usually a typo or a command your server version or modules do not provide. Correcting or enabling the command resolves it. Jump to your situation below or work through the methods in order.
The Redis ERR unknown command error means the server does not recognise the command you sent. The common causes are a typo or wrong argument shape, a newer command run against an older Redis that does not support it, or a command that belongs to a module (such as JSON, Search or Bloom filters) that is not loaded. The error helpfully echoes the command name and the first arguments, which usually pinpoints the mistake. The fix is to verify the command spelling and syntax against the official Redis command reference, upgrade Redis if the command was added in a later version, and load the required module if the command comes from one. Confirming the server version with INFO server tells you whether the command should exist at all.
Redis parses the first word of your request as the command name. ERR unknown command means that word does not match any command the running server knows, so it cannot dispatch it. The echoed name and arguments show exactly what it received.
That mismatch is either your text (a typo or wrong syntax) or the server's capabilities (an older version, or a missing module that would add the command). Checking the docs fixes the first; checking the version and loaded modules fixes the second.
“ERR unknown command is Redis not recognising the first word you sent. Helpfully it echoes that word back, so step one is just reading it, usually it is a typo. If the spelling is right, then it is a capability gap: either the command is newer than your server, so you upgrade, or it belongs to a module like RedisJSON that is not loaded, so you load the module. A quick INFO server tells you the version and settles whether the command should even exist.”
INFO server
MODULE LIST
ERR unknown command means Redis does not recognise the command. Read the echoed name, it is usually a typo, then verify spelling against the docs. If the spelling is right, the command may be newer than your server (upgrade) or belong to a module (load it). INFO server confirms the version.
If the command is spelled correctly and your version supports it but it is still unknown, you may be connected through a proxy or a managed-Redis layer that disables certain commands; check the provider's command-restriction list. You can also submit your error to us for a tailored fix.
