[rabbitmq-discuss] Set rabbitmq to use in Amazon EC2 with different regions
Pedro Sá da Costa
psdc1978 at gmail.com
Thu Jul 25 15:11:07 BST 2013
If I leave MQ configured with RABBITMQ_NODE_IP_ADDRESS=0.0.0.0, and I try
to connect to the *public* IP address, it seems that the request reaches
the MQ but the connection is terminated by unknown reason. I get this error
from the MQ log:
=ERROR REPORT==== 25-Jul-2013::14:02:34 ===
closing AMQP connection <0.459.0> ("client IP":42364 -> "private EC2
1 - Why the client reached the MQ? The public DNS is translated
autormatically to the private DNS in Amazon EC2?
2 - How can I get more information in the logs to understand why the
connection is terminated?
On 25 July 2013 12:46, Ceri Storey <ceri at lshift.net> wrote:
> (25/07/13 12:12), Pedro Sá da Costa wrote:
> If I set the RABBITMQ_NODE_IP_ADDRESS to 0.0.0.0, or I don't set the RABBITMQ_NODE_IP_ADDRESS,
> the message broker starts with the internal IP. This means that I cannot
> access it outside from the internet. If I put the public IP, the error
> continues. How I can set rabbitMQ to access is it from the internet?
> What happens if you leave it configured with
> RABBITMQ_NODE_IP_ADDRESS=0.0.0.0, but try to connect to the *public* IP
> On 23 July 2013 12:15, Michael Klishin <michael.s.klishin at gmail.com>wrote:
>> 2013/7/23 Pedro Sá da Costa <psdc1978 at gmail.com>
>>> Error description:
>> Try using 0.0.0.0 for RABBITMQ_NODE_IP_ADDRESS. This will relieve you
>> from having to worry about the exact IP value of the interface.
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
> Best regards,
> rabbitmq-discuss mailing listrabbitmq-discuss at lists.rabbitmq.comhttps://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss