RabbitMQ cluster on docker playground not accessible to nodejs amqp client

Kailash Yogeshwar

unread,

Nov 27, 2019, 12:15:18 PM11/27/19

to rabbitmq-users

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

unread,

Nov 27, 2019, 12:32:42 PM11/27/19

to rabbitmq-users

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

unread,

Nov 27, 2019, 9:04:53 PM11/27/19

to rabbitmq-users

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

unread,

Nov 27, 2019, 9:07:05 PM11/27/19

to rabbitmq-users

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

Kailash Yogeshwar

unread,

Nov 28, 2019, 9:06:19 AM11/28/19

to rabbitmq-users

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

Screenshot from 2019-11-28 19-35-37.png

Wesley Peng

unread,

Nov 28, 2019, 9:10:59 AM11/28/19

to Kailash Yogeshwar, rabbitmq-users

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

unread,

Nov 28, 2019, 9:41:50 AM11/28/19

to Wesley Peng, rabbitmq-users

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

Wesley Peng

unread,

Nov 28, 2019, 8:59:02 PM11/28/19

to rabbitm...@googlegroups.com

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

regards.

Reply all

Reply to author

Forward