RabbitMQ cluster on docker playground not accessible to nodejs amqp client

[Kailash Yogeshwar]

I have created cluster on docker playground PWD but not able to connect to it using nodejs library node-coffee. I have create separate user with admin privileges but still no luck however i am able to telnet 5672 and node's are up as i can access management ui.

[Michael Klishin]

Please help others help you by providing some relevant information:

 * How was RabbitMQ provisioned?

 * What error messages you are getting if any

 * What's in the server logs [1]

and what library exactly you use. node-amqp is a terribly buggy client library which some RabbitMQ-as-a-Service providers outright block.

Make sure you use the library we use in our tutorials.

[Kailash Yogeshwar]

Hi Michael,

I had  deployed my own cluster on Play with Docker project.

I had created instance node1 and deployed rabbitmq cluster using docker-compose file and ports were exposed.

I was able to see all the nodes in cluster through management UI.

However I  was using clinet amqp-coffee developed by dropbox to connect to my Remote RabbitMQ server by providing host as provided by Play With Docker aka PWD in this format 

const AMQP = require('amqp-coffee');

const connectOptions = {

   host: [

    { host: 'ip172-18-0-30-bnf72c3jagq000etunj0-5672.direct.labs.play-with-docker.com' , port: '15672' },

    { host: 'ip172-18-0-30-bnf72c3jagq000etunj0-5673.direct.labs.play-with-docker.com',  port: '25673' },

    { host: 'ip172-18-0-30-bnf72c3jagq000etunj0-5674.direct.labs.play-with-docker.com',  port: '35674' }

  ],

  login: "admin",

  password: "admin",

  reconnect: true

}

 

const connection = new AMQP(connectOptions);

connection.on('ready', () => console.log('ready')) 

I used telnet also with host and it was accepting my telnet request but not TCP.

[Kailash Yogeshwar]

Ignore ports they are purposely written wrong they are 5672, 5673, 5674.

[Kailash Yogeshwar]

 I have specified tcp.listeners.1 0.0.0.0:5672 for accepting remote connection yet no success.

[Wesley Peng]

Since you can ssh to the container, can you run netstat or ps command to see if RMQ process is running?

Regards 

28 листопада 2019 р., 22:06:35,від "Kailash Yogeshwar" <kailashyo...@gmail.com>:

 I have specified tcp.listeners.1 0.0.0.0:5672 for accepting remote connection yet no success.

On Thursday, November 28, 2019 at 7:37:05 AM UTC+5:30, Kailash Yogeshwar wrote:

Ignore ports they are purposely written wrong they are 5672, 5673, 5674.

 

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/d2db939a-5a15-4394-9e5b-ac5c7d52e89c%40googlegroups.com.

[Kailash Yogeshwar]

Yes as you can see the process is running and it's port 5672 is exposed

[Wesley Peng]

How did you test port 5672? by hand or by a script? can you show the code?

regards.