[rabbitmq-discuss] newbie problem--'Error: unable to connect to node 'rabbit at rabbitmq-small02-dev': nodedown'

Carl Hörberg carl.hoerberg at gmail.com
Fri Mar 16 17:43:57 GMT 2012

you can allow traffic only between instances in the same security group by
setting the "source" field to the id of the security group


On Fri, Mar 16, 2012 at 18:25, John Stoner <johnstoner2 at gmail.com> wrote:

> [Just a bit of context, some of this conversation happened off list--I'm
> trying to start a rabbitmq cluster on some firewalled EC2 instances, and
> Emile has been helping me identify all the details about ports and
> configuration and all that good stuff.]
> We're looking to open fewer ports, not more.* *Is there a minimum we
> could do? Would one work, or would it break something else?
> Also, we have these ports open to all TCP.  In the spirit of securing our
> systems, I guess we could open 4369 only to the IPs of the other machines
> in the cluster. Is that a good idea? Can you think of more firewall
> restrictions to add?
> On Fri, Mar 16, 2012 at 5:24 AM, Emile Joubert <emile at rabbitmq.com> wrote:
> Hi John,
>> On 16/03/12 05:41, John Stoner wrote:
>> > OK, I got it to start with a good config file. what's an appropriate
>> > range for these port numbers?
>> You are free to use any unused port range between 1024 and 65536.
>> -Emile
> --
> blogs:
> http://johnstoner.wordpress.com/
> 'In knowledge is power; in  wisdom, humility.'
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120316/ef59b159/attachment.htm>

More information about the rabbitmq-discuss mailing list