ERR DEBUG command not allowed: DEBUG command not allowed
RedisWhat does it mean?
You tried to run the DEBUG command, but the server does not allow it. DEBUG is a low-level, dangerous diagnostic command; for security reasons it is disabled or restricted by default in newer Redis versions.
Why does it happen?
In Redis 7+, DEBUG subcommands do not run without the enable-debug-command setting; managed cloud Redis services usually disable the command completely; or the command is denied by an ACL. Test/diagnostic scripts (e.g. DEBUG SLEEP, DEBUG OBJECT) often hit this error.
How to fix it
Avoid DEBUG in production. If it is genuinely needed in a local/test environment, enable it in the configuration: enable-debug-command yes (or 'local') in redis.conf. On cloud services the command usually cannot be enabled at all; use safe commands such as MEMORY USAGE, OBJECT ENCODING and INFO for equivalent information. If an ACL restriction applies, review the permissions.
More from this engine
- ERR This instance has cluster support disabledERR This instance has cluster support disabled
- ERR unknown subcommandERR unknown subcommand or wrong number of arguments
- ERR Client sent AUTH, but no password is setERR AUTH <password> called without any password configured for the default user (Redis 6+) / ERR Client sent AUTH, but no password is set (Redis <6)
- ERR Can't save in background: fork failedBackground save failed: fork failed
- NOPROTO unsupported protocol versionUnsupported RESP protocol version
- ERR Unknown option or number of arguments for CONFIG SETUnknown option or number of arguments for CONFIG SET (older versions: Unsupported CONFIG parameter)
- ERR MULTI calls can not be nestedMULTI calls can not be nested