Redis保护模式配置引起的问题

本文详细解析了在新服务器上集成Redis时遇到的JedisDataException:DENIED异常,介绍了Redis保护模式的触发原因及四种解决方案,包括禁用保护模式、编辑配置文件、重启服务与设置绑定IP或密码。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

在新服务器上Jedis jedis = pool.getResource()

  • 报错:

redis.clients.jedis.exceptions.JedisDataException:
DENIED Redis is running in protected mode because protected mode is enabled, no bind address was specified,
no authentication password is requested to clients.
In this mode connections are only accepted from the loopback interface.
If you want to connect from external computers to Redis you may adopt one of the following solutions:

  1. Just disable protected mode sending the command ‘CONFIG SET protected-mode no’ from the loopback interface by connecting to Redis from the same host the server is running,
    however MAKE SURE Redis is not publicly accessible from internet if you do so.
    Use CONFIG REWRITE to make this change permanent.

  2. Alternatively you can just disable the protected mode by editing the Redis configuration file,
    and setting the protected mode option to ‘no’, and then restarting the server.

  3. If you started the server manually just for testing, restart it with the ‘–protected-mode no’ option.

  4. Setup a bind address or an authentication password.

NOTE: You only need to do one of the above things in order for the server to start accepting connections from the outside.

在将redis集成在项目中时,如果是新安装在linux服务器的服务端,第一次使用往往会报JedisDataException:DENIED Redis is running in protected mode because protected mode is enabled, no bind address was specified异常。其实使用RedisTemplate连接远程Redis服务器的时候,Redis默认状态下是一守护状态下安装运行的,所以如果不是本地连接,就会报这个错误,而错误的提醒也很明显。redis的保护模式已经激活。没有绑定特定的连接ip地址,没有授权密码,
在这种情况下,连接只能是本地连接。
而想要从外部连接,则可以采取以下几种方式:

1):redis服务器运行时,在本地连接,并且运行命令:CONFIG SET protected-mode no.但是如果你要这样做,
你要确保Redis不要公开在互联网上,使用命令CONFIG REWRITE来使文件来永久的改变

2):第二种方式,你可以编辑Redis的配置文件,将protected mode选项的值改成no,并重新启动redis服务

3):如果你启动Redis只是为了测试使用,你可以重启Redis服务,加上–protected-mode no参数

4):设置绑定特定的ip地址或者给一个身份密码
以上的选项,使用其中一种就可以使用了,目前采用的是第四种方式的绑定本地的内网IP,只能将服务器的内网IP绑定到redis.conf下面,在阿里云上绑定了外网IP后无效。

配置文件:redis.conf

#bind 192.168.1.100 10.0.0.1
#bind 127.0.0.1 ::1

#protected-mode yes

#requirepass foobared
Caused by: redis.clients.jedis.exceptions.JedisDataException: DENIED Redis is running in protected mode because protected mode is enabled, no bind address was specified, no authentication password is requested to clients. In this mode connections are only accepted from the loopback interface. If you want to connect from external computers to Redis you may adopt one of the following solutions: 1) Just disable protected mode sending the command 'CONFIG SET protected-mode no' from the loopback interface by connecting to Redis from the same host the server is running, however MAKE SURE Redis is not publicly accessible from internet if you do so. Use CONFIG REWRITE to make this change permanent. 2) Alternatively you can just disable the protected mode by editing the Redis configuration file, and setting the protected mode option to 'no', and then restarting the server. 3) If you started the server manually just for testing, restart it with the '--protected-mode no' option. 4) Setup a bind address or an authentication password. NOTE: You only need to do one of the above things in order for the server to start accepting connections from the outside.
redis.clients.jedis.exceptions.JedisConnectionException: Could not get a resource from the pool

推荐的是使用第四种方式的给一个身份密码方式:

# vim ./redis.conf 

#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 requirepass 123456789
$ auth 123456789
OK
$ set key:01 val123456
OK
$ get key:01
"val123456"
Redis是一种高性能的键值对存储系统,广泛应用于缓存、消息队列等领域。尽管其性能优越且易于使用,在实际部署和运维过程中仍可能出现各种各样的问题。以下是Redis常见的一些问题及其简要说明: ### 1. 内存溢出 (Out Of Memory - OOM) #### 现象描述: 由于数据量过大或配置不当导致服务器内存不足,进而引发OOM错误,最终可能导致服务崩溃。 #### 解决方案建议: - 设置最大可用内存量 (`maxmemory`) 并采用合适的淘汰策略; - 定期清理过期的数据项; - 分析业务需求调整合理的key生命周期及大小限制等措施防止无节制增长。 ### 2. 性能瓶颈 #### 表现形式: 随着访问频率增加,响应时间延长甚至达到秒级延迟;CPU占用率过高影响其他进程运行效率。 #### 考虑因素与应对办法: - 对于频繁读写的热点Key优化查询路径降低复杂度; - 使用集群模式分散负载压力平衡资源利用率; - 配置持久化选项(如AOF/RDB)减少不必要的I/O操作次数; ### 3. 数据丢失风险 #### 可能原因: 突然断电、硬件故障等情况使得尚未同步到磁盘的日志文件损坏无法恢复造成部分新插入记录消失不见; 或者主从复制机制下Slave节点跟不上Master更新速度引起数据一致性异常。 #### 应急处理思路: - 合理规划备份计划定期保存快照副本确保意外发生前一刻的状态得以保留以便快速回滚修复; - 加强网络连接稳定性监测及时发现链路中断现象保证实时通讯畅通; - 监控主从之间的偏移差距设定阈值报警提示管理员尽早介入排查解决潜在隐患. 除了上述提到的问题外还有许多其它方面需要注意比如安全漏洞防护(设置密码保护)、兼容性考量等问题都需要我们在日常工作中不断积累经验加以防范改进。 希望这些问题能够帮助你更好地理解和预防可能出现的风险点!
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值