This means Redis ACLs are in use and the authenticated user is not allowed to run that command or touch those keys. Granting the permission resolves it. Jump to your situation below or work through the methods in order.
The Redis NOPERM error means Access Control Lists (ACLs) are in effect and the authenticated user lacks permission for the command, key, or channel it tried to use. Redis 6 introduced ACLs so you can restrict each user to specific commands and key patterns, and NOPERM is that restriction working: the user is authenticated but not authorized for this action. The variants name the command, a key the user may not access, or a pub/sub channel. The fix is to review the user's permissions with ACL GETUSER and ACL LIST, then, from an admin account, grant the needed access with ACL SETUSER, adding the command category or key pattern the user legitimately needs. Granting the minimum necessary keeps the principle of least privilege intact.
ACLs let you say which commands and keys each Redis user may use. When a user runs something outside that allowance, Redis returns NOPERM. The user is who they say they are, authentication passed, but they are not permitted to do this particular thing.
So unlike NOAUTH, the credential is fine; the authorization is not. The fix is to look at what the user is allowed and grant the specific command category, key pattern, or channel it genuinely needs, no more. An administrator with access to ACL SETUSER makes that change.
“NOPERM is different from NOAUTH, here the login worked but the user is not allowed to do that specific thing. ACLs are deliberately tight, so I first run ACL GETUSER to see exactly what the user can touch, then from an admin account I grant just the command category or key pattern it actually needs with ACL SETUSER. The temptation is to hand it allcommands and move on, but resist that, grant the minimum, because least privilege is the whole point of ACLs.”
ACL GETUSER username ACL LIST
ACL SETUSER username +get +set
+@read.+@all unless truly required.ACL SETUSER username ~app:*
ACL SETUSER username &events:*
NOPERM means ACLs allow the user to connect but not to run this command, key, or channel. Review with ACL GETUSER and ACL LIST, then from an admin account grant the specific command category or key pattern with ACL SETUSER. Grant the minimum needed rather than +@all.
If a user has the command and key grants but still hits NOPERM, the block may be on a key pattern or pub/sub channel it also touches; ACL GETUSER shows the full rule set so you can spot the missing pattern. You can also submit your error to us for a tailored fix.