redis.conf错误-尽管禁用了我的redis.conf文件中的auth

Question

在本地对本地Redis实例运行应用程序时，我看到以下错误。

ReplyError: Ready check failed: NOAUTH Authentication required.
            at JavascriptReplyParser.Parser.returnError (/Users/Olegzandr/WebstormProjects/node_redis/index.js:193:31)
            at JavascriptReplyParser.run (/Users/Olegzandr/WebstormProjects/node_redis/node_modules/redis-parser/lib/javascript.js:135:18)
            at JavascriptReplyParser.execute (/Users/Olegzandr/WebstormProjects/node_redis/node_modules/redis-parser/lib/javascript.js:112:10)
            at Socket.<anonymous> (/Users/Olegzandr/WebstormProjects/node_redis/index.js:269:27)
            at emitOne (events.js:77:13)
            at Socket.emit (events.js:169:7)
            at readableAddChunk (_stream_readable.js:146:16)

我相信通过在配置文件中使用以下行，我已经禁用了身份验证：

# By default protected mode is enabled. You should disable it only if
# you are sure you want clients from other hosts to connect to Redis
# even if no authentication is configured, nor a specific set of interfaces
# are explicitly listed using the "bind" directive.
protected-mode no  #is this correct?

而且不需要密码：

# Require clients to issue AUTH <PASSWORD> before processing any other
# commands.  This might be useful in environments in which you do not trust
# others with access to the host running redis-server.
#
# This should stay commented out for backward compatibility and because most
# people do not need auth (e.g. they run their own servers).
#
# Warning: since Redis is pretty fast an outside user can try up to
# 150k passwords per second against a good box. This means that you should
# use a very strong password otherwise it will be very easy to break.
#
# requirepass foobared

知道有什么不对吗？

Answer 1

如果有人在运行redis实例中运行CONFIG SET REQUIREPASS [PWD]，那么redis将不顾conf文件更改其auth配置。在此之后，即使已经连接的客户端也必须设置AUTH，否则他们将接收NOAUTH Authentication required。

试着重新启动红宝石，小心有害的雷射！

Answer 2

在redis-cli上，使用正确的密码(如果您错误地设置了密码)。然后将所需的通行证设置为空。这将解决这个问题。

AUTH <old-password>
CONFIG SET REQUIREPASS ""

注意:只有当您知道密码(意味着您已经将密码设置为任何redis实例)时，这才有效。如果没有，上述重新启动redis的解决方案应该有效。