Redis 3.2.8中config get *命令无法执行，提示未知命令求助

AI 小北

2026-5-21

Fixing "ERR unknown command 'config'" in Redis 3.2.8

Hey there! Let's troubleshoot why you're hitting that ERR unknown command 'config' error even though the CONFIG GET command has been available since Redis 2.0. Here are the most likely causes and fixes to try:

Common Causes & Solutions

Check if the CONFIG command was renamed or disabled
Redis often includes security configurations that rename or disable sensitive commands like CONFIG to block unauthorized access. Open your redis.conf file and look for a line like:
```
rename-command CONFIG ""
```
or something similar to:
```
rename-command CONFIG "hidden_config_cmd"
```
If it's set to "", the command is fully disabled. If it's renamed, you'll need to use the new command name instead. For local testing, you can comment out this line, restart Redis, and try executing CONFIG GET * again.
Verify you're connected to the correct Redis instance
It's easy to accidentally connect to a different Redis deployment (like an older version running on another port). Run the INFO server command and check the redis_version field to confirm you're actually interacting with Redis 3.2.8. If not, double-check your connection parameters (host, port) to ensure you're targeting the right instance.
Check for Redis Cluster restrictions
If you're working with a Redis Cluster, the CONFIG command can't be executed globally through the cluster client. You need to connect directly to individual cluster nodes and run the command on each one separately.
Double-check command syntax
Even small typos can trigger this error. Make sure your command has proper spacing: CONFIG GET * (or lowercase config get *—Redis commands are case-insensitive). Avoid mistakes like config get* (missing a space), which would be interpreted as a single unknown command.