How to configure Redis 3.4 and above in master/slave config to resolve error Sentinel running on protected mode?

From redis 3.2, Sentinel by default, is not reachable from interfaces other than localhost.

Either use the 'bind' directive to bind to a list of network interfaces, or disable protected mode with "protected-mode no" by adding it to this configuration file.

For example you may use one of the following:

bind 127.0.0.1 192.168.1.1

protected-mode no

For testing, you can try

redis-server --protected-mode no

This will set Redis protected mode to no.

As from documentation suggested steps.

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.