Open Redis port for remote connections

Question

I can ping pong Redis on the server:

# redis-cli ping
PONG

But remotely, I got problems:

$ src/redis-cli -h REMOTE.IP ping
Could not connect to Redis at REMOTE.IP:6379: Connection refused

In config, I got the standard port:

# Accept connections on the specified port, default is 6379.
# If port 0 is specified Redis will not listen on a TCP socket.
port 6379

So maybe I should open port 6379 on the remote Ubuntu machine? How do I do it?

redis is not listening on the remote machine? – Sergio Tulentsev Sep 30 '13 at 09:45 — Sergio Tulentsev, Sep 30 '13 at 09:45
maybe, how to check it – Maxim Yefremov Sep 30 '13 at 09:51 — Maxim Yefremov, Sep 30 '13 at 09:51

MildlySerious · Accepted Answer · 2017-09-07T13:00:48.960

268

Did you set the bind option to allow remote access on the redis server?

Before (file /etc/redis/redis.conf)

bind 127.0.0.1

After

bind 0.0.0.0

and run sudo service redis-server restart to restart the server. If that's not the problem, you might want to check any firewalls that might block the access.

Important: If you don't use a firewall (iptables, ufw..) to control who connects to the port in use, ANYONE can connect to this Redis instance. Without using Redis' AUTH that means anyone can access/change/delete your data. Be safe!

edited Sep 07 '17 at 13:00

answered Sep 30 '13 at 09:53

MildlySerious

8,112
2
27
29

2

in config file I added string `bind 0.0.0.0` after string `bind 127.0.0.1`. Restarted redis. And now can connect remotly. – Maxim Yefremov Sep 30 '13 at 10:08
Is there any difference if we use `bind 0.0.0.0` alone vs `bind 127.0.0.1 0.0.0.0` – Nyxynyx Jun 25 '14 at 21:29
1

@Nyxynyx 0.0.0.0 binds to all adapters, so it's unnecessary. Shouldn't make a difference, though. – MildlySerious Jun 26 '14 at 20:39
1

Is it secure to open redis to any ip calls? How can we restricted accessing redis from only certain IPs? – brsbilgic Dec 04 '14 at 16:33
@brsbilgic That should probably be done using a firewall. Check out iptables or UFW. – MildlySerious Mar 06 '15 at 16:13
1

@MildlySerious thanks a lot. We have wasted almost 2 weeks figuring out whether firewall or network or some other issue. But this change worked like champ. – kinnu Mar 05 '20 at 18:03

score 26 · Answer 2 · answered May 26 '16 at 14:31

26

For me, I needed to do the following:

1- Comment out bind 127.0.0.1

2- Change protected-mode to no

3- Protect my server with iptables (https://www.digitalocean.com/community/tutorials/how-to-implement-a-basic-firewall-template-with-iptables-on-ubuntu-14-04)

answered May 26 '16 at 14:31

Abdo

12,869
9
77
97

2

I had to use bind 0.0.0.0. "bind 127.0.0.1" didn't work for me. I didn't need to set "protected-mode" to "no". Warning: Don't leave empty space before the "bind" or the server won't start. Note: I'm using the windows port of Redis – Josh Oct 26 '17 at 17:58

score 7 · Answer 3 · answered Dec 11 '15 at 18:10

7

A quick note that doing this without further securing your Redis server is not a good idea as it can leave you open to attack. Be sure to also implement AUTH or otherwise secure that. See http://redis.io/topics/security for details.

answered Dec 11 '15 at 18:10

backwardm

309
3
6

score 7 · Answer 4 · answered Mar 28 '20 at 06:40

7

Bind & protected-mode both are the essential steps. But if ufw is enabled then you will have to make redis port allow in ufw.

Check ufw status ufw status if Status: active then allow redis-port ufw allow 6379
vi /etc/redis/redis.conf
Change the bind 127.0.0.1 to bind 0.0.0.0
change the protected-mode yes to protected-mode no

answered Mar 28 '20 at 06:40

Gaurav Tyagi

471
6
5

the `ufw` was the difference for me. – Lucho Nov 17 '20 at 20:28
I missed the protected-mode option, this answer should get more votes for others not to miss this option too :) – Rutger Jan 21 '22 at 09:36

score 4 · Answer 5 · answered Jul 05 '17 at 09:40

4

1- Comment out bind 127.0.0.1

2- set requirepass yourpassword

then check if the firewall blocked your port

iptables -L -n

service iptables stop

answered Jul 05 '17 at 09:40

tony qi

95
7

score 3 · Answer 6 · edited Jul 09 '20 at 15:16

3

Open the file at location /etc/redis.conf
Comment out bind 127.0.0.1
Restart Redis:
```
 sudo systemctl start redis.service
```
Disable Firewalld:
```
 systemctl disable firewalld
```
Stop Firewalld:
```
 systemctl stop firewalld
```

Then try:

redis-cli -h 192.168.0.2(ip) -a redis(username)

edited Jul 09 '20 at 15:16

Tarick Welling

2,909
3
16
40

answered Nov 20 '17 at 10:09

Rizwan Basheer

127
1
5

score 3 · Answer 7 · answered Nov 11 '19 at 19:51

A quick note that if you are using AWS ec2 instance then there is one more extra step that I believe is also mandatory. I missed the step-3 and it took me whole day to figure out to add an inbound rule to security group

Step 1(as previous): in your redis.conf change bind 127.0.0.1 to bind 0.0.0.0

Step2(as previous): in your redis.conf change protected-mode yes to protected-mode no

important for Amazon Ec2 Instance:

Step3: In your current ec2 machine go to the security group. add an inbound rule for custom TCP with 6379 port and select option "use from anywhere".

score 2 · Answer 8 · answered Dec 19 '18 at 13:45

Open $REDIS_HOME/redis.conf and uncomment requirepass -YOUR-PASSWORD-HERE- and write down your password in the specified lines.
Login to redis using redis-cli and verify your password in the database using auth -YOUR-PASSWORD-HERE- command.
Disable protected mode by changing its string in $REDIS_HOME/redis.conf to protected-mode no.
Search for all bind ports values and comment all of them. Just add bind 0.0.0.0 to $REDIS_HOME/redis.conf file.
Disable your firewall or open redis port.
Start redis using ./redis-server $REDIS_HOME/redis.conf.
Check the configuration via ./redis-cli -h -YOUR-IP- -a -YOUR-PASSWORD-HERE-.
Check the configuration via ./redis-cli -h -YOUR-IP- ping.

Please don't ever give the advice "Disable your firewall". – Samantha Atkins Feb 21 '19 at 03:26 — Samantha Atkins, Feb 21 '19 at 03:26

score 2 · Answer 9 · answered Oct 23 '20 at 12:11

2

Another possibly helpful note.

Redis can be bound to multiple IPs - that's very helpful when you don't want to open it to entire world (0.0.0.0) but only make it accessible in local networks.

sudo nano /etc/redis/redis.conf
add your local network IP to the end of bind setting:

bind 127.0.0.1 10.0.0.1

restart the service: sudo service redis-server restart

Now you can easily access redis from other computers in same network, e.g. redis-cli -h 10.0.0.1

answered Oct 23 '20 at 12:11

Stalinko

2,787
23
24

thank you! very very helpful the suggestion 2 :-) that is exactly the solution I was looking for – lorenzo_campanile Feb 12 '21 at 11:30

score 1 · Answer 10 · answered Feb 25 '20 at 06:07

In my case, I'm using redis-stable

Go to redis-stable path 
 cd /home/ubuntu/software/redis-stable

Open the redis.conf

vim redis.conf

Change the bind 127.0.0.1 to bind 0.0.0.0

change the protected-mode yes to protected-mode no

Restart the redis-server:

/etc/init.d/redis-server stop
 redis-server redis.conf

Open Redis port for remote connections

10 Answers10

important for Amazon Ec2 Instance:

Linked