Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have an Amazon VPC setup with a private subnet containing 2 instances. One of them has redis running on it, the other instance I want to use to connect to the redis server. I have the redis instance listening on port 6123. When I connect locally on the Redis instance, everything works, but when I try to connect from the other instance on the subnet I get:

Connection refused - Unable to connect to Redis

I setup two separate VPC security groups, one for the redis server, allowing inbound connections on port 6123 using the other instance's security group as the source. Likewise, I added a rule to the security group for the other instance to allow outbound traffic on port 6123 to the redis-instance (using the redis instance's security group as the destination).

Is there something I'm forgetting here? Another rule that I have to add? Or a special route I have to setup?

Thanks for any help/direction, Tom

share|improve this question
up vote 12 down vote accepted

By default redis listens on have you edited your redis.conf to include the line bind your.private.ip.address ?

share|improve this answer
yea that was it! thanks a lot for the info 8) It's strange though because I added an ICMP rule using the same method to try and ping the redis server but none of the packets went through. oh well this will work. Thanks again! – Tomek Aug 16 '11 at 21:20
To make your Redis server accessible from external IP addresses, just comment out the bind line. – Ben Gotow Sep 1 '12 at 17:28

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.