Cannot connect as described in the README about eventstore-client-nodejs

[alexlawrence]

Sorry for my cryptic comment. Yes, I always managed to connect with the Node.js client by using the factory syntax EventStoreDBClient.connectionString('...'); I mentioned this in my first comment. Sorry if it wasn't clear enough.

It did only not work for me when using the constructor function (new EventStoreDBClient()). However, I found out what the problem was. I was missing the "insecure" flag for the ChannelCredentialOptions constructor argument. 🤦

This issue is therefore invalid and can be closed.

[YoEight]

Can you share how you started your docker container please?

[alexlawrence]

I followed the docs on this and tried both ways that are described there.

This means, I tried it with both of the following commands:

docker run --name esdb-node -it -p 2113:2113 -p 1113:1113 eventstore/eventstore:latest --insecure --run-projections=All
docker run --name esdb-node -it -p 2113:2113 -p 1113:1113 eventstore/eventstore:latest --insecure --run-projections=All --enable-external-tcp --enable-atom-pub-over-http

Actually, I am using docker-compose, but I don't think this should make a difference.

What I didn't try so far is to connect from within the Docker container itself (using localhost). So far, I either tried to connect from the host or another container that has access to the EventStore container. The factory function variant (EventStoreDBClient.connectionString("<your value>");) works for both of those scenarios.

[YoEight]

The last part of your comment is hard to understand. What do you mean by it worked on both scenarios? Do you mean you managed to connect with the NodeJS client?

I propose to make sure that in the most simple use case, you are able to connect to a server while using the nodejs client.

The goal is to determine if the client is at fault or your docker configuration.