java 连接redis 拒绝_Spring Session java连接redis 失败解决方案

朴灿烈づ我的快乐病毒、 2022-11-04 15:26 342阅读 0赞

日志提示连接拒绝, 是因为redis默认的protected-mode默认为yes

解决方案1:

进入redis-cli  输入命令

CONFIG SET protected-mode no

![f92b0e3ccaa61dcf4f0b5af0057e0890.png][]

解决方案2.

在redis目录下的redis.conf配置文件中增加

protected-mode no

方案2需要重启redis

设置成功, 重启项目就没有这个错误了

Spring Session连接redis 或者直接用Java连接redis ,遇到这个问题都可以这么解决

下面解决之前启动日志, 错误信息

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'enableRedisKeyspaceNotificationsInitializer' defined in class path resource \[org/springframework/session/data/redis/config/annotation/web/http/RedisHttpSessionConfiguration.class\]: Invocation of init method failed; nested exception is org.springframework.data.redis.RedisConnectionFailureException: Unable to connect to Redis on 192.168.1.88:6379; nested exception is com.lambdaworks.redis.RedisCommandExecutionException: 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.

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1628) ~\[spring-beans-4.3.12.RELEASE.jar:4.3.12.RELEASE\]

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:555) ~\[spring-beans-4.3.12.RELEASE.jar:4.3.12.RELEASE\]

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:483) ~\[spring-beans-4.3.12.RELEASE.jar:4.3.12.RELEASE\]

at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306) ~\[spring-beans-4.3.12.RELEASE.jar:4.3.12.RELEASE\]

at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230) ~\[spring-beans-4.3.12.RELEASE.jar:4.3.12.RELEASE\]

at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302) ~\[spring-beans-4.3.12.RELEASE.jar:4.3.12.RELEASE\]

at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197) ~\[spring-beans-4.3.12.RELEASE.jar:4.3.12.RELEASE\]

at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:761) ~\[spring-beans-4.3.12.RELEASE.jar:4.3.12.RELEASE\]

at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:867) ~\[spring-context-4.3.12.RELEASE.jar:4.3.12.RELEASE\]

at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:543) ~\[spring-context-4.3.12.RELEASE.jar:4.3.12.RELEASE\]

at org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:443) ~\[spring-web-4.3.12.RELEASE.jar:4.3.12.RELEASE\]

at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:325) \[spring-web-4.3.12.RELEASE.jar:4.3.12.RELEASE\]

at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:107) \[spring-web-4.3.12.RELEASE.jar:4.3.12.RELEASE\]

at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4772) \[catalina.jar:8.0.15\]

at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5196) \[catalina.jar:8.0.15\]

at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) \[catalina.jar:8.0.15\]

at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:725) \[catalina.jar:8.0.15\]

at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:701) \[catalina.jar:8.0.15\]

at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:714) \[catalina.jar:8.0.15\]

at org.apache.catalina.startup.HostConfig.manageApp(HostConfig.java:1585) \[catalina.jar:8.0.15\]

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~\[?:1.8.0\_45\]

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~\[?:1.8.0\_45\]

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~\[?:1.8.0\_45\]

at java.lang.reflect.Method.invoke(Method.java:497) ~\[?:1.8.0\_45\]

at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:300) \[tomcat-coyote.jar:8.0.15\]

at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) \[?:1.8.0\_45\]

at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801) \[?:1.8.0\_45\]

at org.apache.catalina.mbeans.MBeanFactory.createStandardContext(MBeanFactory.java:463) \[catalina.jar:8.0.15\]

at org.apache.catalina.mbeans.MBeanFactory.createStandardContext(MBeanFactory.java:413) \[catalina.jar:8.0.15\]

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~\[?:1.8.0\_45\]

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~\[?:1.8.0\_45\]

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~\[?:1.8.0\_45\]

at java.lang.reflect.Method.invoke(Method.java:497) ~\[?:1.8.0\_45\]

at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:300) \[tomcat-coyote.jar:8.0.15\]

at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) \[?:1.8.0\_45\]

at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801) \[?:1.8.0\_45\]

at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1466) \[?:1.8.0\_45\]

at javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:76) \[?:1.8.0\_45\]

at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1307) \[?:1.8.0\_45\]

at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1399) \[?:1.8.0\_45\]

at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:828) \[?:1.8.0\_45\]

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~\[?:1.8.0\_45\]

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~\[?:1.8.0\_45\]

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~\[?:1.8.0\_45\]

at java.lang.reflect.Method.invoke(Method.java:497) ~\[?:1.8.0\_45\]

at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:323) \[?:1.8.0\_45\]

at sun.rmi.transport.Transport$1.run(Transport.java:200) \[?:1.8.0\_45\]

at sun.rmi.transport.Transport$1.run(Transport.java:197) \[?:1.8.0\_45\]

at java.security.AccessController.doPrivileged(Native Method) ~\[?:1.8.0\_45\]

at sun.rmi.transport.Transport.serviceCall(Transport.java:196) \[?:1.8.0\_45\]

at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568) \[?:1.8.0\_45\]

at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826) \[?:1.8.0\_45\]

at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$254(TCPTransport.java:683) \[?:1.8.0\_45\]

at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler$$Lambda$1/1394664682.run(Unknown Source) \[?:1.8.0\_45\]

at java.security.AccessController.doPrivileged(Native Method) ~\[?:1.8.0\_45\]

at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682) \[?:1.8.0\_45\]

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) \[?:1.8.0\_45\]

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) \[?:1.8.0\_45\]

at java.lang.Thread.run(Thread.java:745) \[?:1.8.0\_45\]

Caused by: org.springframework.data.redis.RedisConnectionFailureException: Unable to connect to Redis on 192.168.1.88:6379; nested exception is com.lambdaworks.redis.RedisCommandExecutionException: 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.

at org.springframework.data.redis.connection.lettuce.LettuceConnectionFactory.createLettuceConnector(LettuceConnectionFactory.java:545) ~\[spring-data-redis-1.7.10.RELEASE.jar:?\]

at org.springframework.data.redis.connection.lettuce.LettuceConnectionFactory.initConnection(LettuceConnectionFactory.java:214) ~\[spring-data-redis-1.7.10.RELEASE.jar:?\]

at org.springframework.data.redis.connection.lettuce.LettuceConnectionFactory.getSharedConnection(LettuceConnectionFactory.java:518) ~\[spring-data-redis-1.7.10.RELEASE.jar:?\]

at org.springframework.data.redis.connection.lettuce.LettuceConnectionFactory.getConnection(LettuceConnectionFactory.java:190) ~\[spring-data-redis-1.7.10.RELEASE.jar:?\]

at org.springframework.session.data.redis.config.annotation.web.http.RedisHttpSessionConfiguration$EnableRedisKeyspaceNotificationsInitializer.afterPropertiesSet(RedisHttpSessionConfiguration.java:249) ~\[spring-session-1.3.1.RELEASE.jar:?\]

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1687) ~\[spring-beans-4.3.12.RELEASE.jar:4.3.12.RELEASE\]

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1624) ~\[spring-beans-4.3.12.RELEASE.jar:4.3.12.RELEASE\]

... 58 more

Caused by: com.lambdaworks.redis.RedisCommandExecutionException: 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.

at com.lambdaworks.redis.LettuceFutures.await(LettuceFutures.java:104) ~\[lettuce-3.5.0.Final.jar:?\]

at com.lambdaworks.redis.RedisAsyncConnectionImpl.select(RedisAsyncConnectionImpl.java:819) ~\[lettuce-3.5.0.Final.jar:?\]

at org.springframework.data.redis.connection.lettuce.LettuceConnectionFactory.createLettuceConnector(LettuceConnectionFactory.java:537) ~\[spring-data-redis-1.7.10.RELEASE.jar:?\]

at org.springframework.data.redis.connection.lettuce.LettuceConnectionFactory.initConnection(LettuceConnectionFactory.java:214) ~\[spring-data-redis-1.7.10.RELEASE.jar:?\]

at org.springframework.data.redis.connection.lettuce.LettuceConnectionFactory.getSharedConnection(LettuceConnectionFactory.java:518) ~\[spring-data-redis-1.7.10.RELEASE.jar:?\]

at org.springframework.data.redis.connection.lettuce.LettuceConnectionFactory.getConnection(LettuceConnectionFactory.java:190) ~\[spring-data-redis-1.7.10.RELEASE.jar:?\]

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1687) ~\[spring-beans-4.3.12.RELEASE.jar:4.3.12.RELEASE\]

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1624) ~\[spring-beans-4.3.12.RELEASE.jar:4.3.12.RELEASE\]

... 58 more

[f92b0e3ccaa61dcf4f0b5af0057e0890.png]: /images/20221023/110b47e6be574bb3833279adae204bb9.png