Open Evasion opened 7 years ago
I have the same issue with V3.2.100... Revert back to V3.0...
Must be a bug in the latest release then. I am currently using v2.8.19 because of this issue.
I ran into this same error message while testing my Dockerization of 3.2.100 and it turned out to be due to protected-mode yes
in the default configuration -- when that's replaced with protected-mode no
(and bind 127.0.0.1
is repalced with bind 0.0.0.0
), it works. :+1:
(I also found both https://github.com/MSOpenTech/redis/issues/437 and https://github.com/MSOpenTech/redis/issues/309 which reference the same message, but don't appear to be related, since they're not referring to Redis 3.2)
See https://github.com/antirez/redis/commit/edd4d555df57dc84265fdfb4ef59a4678832f6da for more information about protected-mode
.
This issue occurs when connecting to a V3.2.100 remote host. Tested connecting to a V 2.8.19 and it works. I have tried removing the listening port restriction in the config file i.e 127.0.0.1 commented. Any idea on what else to try would help.