node-sdk | Transloadit 's official Node.js SDK | SDK library

I was missing camel case on the keyStart prop.

In the single machine case your client application is running on your local machine but the nodes (peers and orderers) are running in Docker containers on your local machine, and have hostnames like peer0.org1.example.com.

Within the Docker network the nodes can talk to each other using their hostnames, e.g. peer0.org1.example.com. Your client (outside the Docker network) can't talk to peer0.org1.example.com because that DNS name does not exist. Instead it needs to connect to localhost on ports mapped (by Docker) to/from specific hosts/ports within the Docker network.

Your client application gets node endpoints in two ways:

1. Entries in its local connection profile.
2. Network topology returned by service discovery.

You can set appropriate (localhost) endpoint URLs in your connection profile. However, the endpoint URLs returned by discovery will be the ones exposed within the Docker network, e.g. peer0.org1.example.com. To facilitate this scenario, the SDK provides the discovery.asLocalhost setting which, when enabled, maps all endpoint addresses returned by discovery to the same port at localhost. An alternative approach is to add entries to your local hosts file that map the node names to localhost.

You should not have the discovery.asLocalhost setting enabled if your nodes are accessible on the real network using their configured hostnames. These hostnames must be resolvable in DNS (so for a real deployment you can't use non-resolvable addresses like example.com), and must match your Fabric network configuration (and server certificate details if using TLS).

For example: Let us assume, this is the content of the DockerFile you are having. Aliases are given as base, dev and prod.

The unexpected server response 403 error is due to the fact that the server recognizes the connection request but fails to authorize it and doesn't allow connection. The connection was being rejected by the server as no origin header was set. The docs of NodeJS WebSocket describe it as:

If verifyClient is not set then the handshake is automatically accepted. If it is provided with a single argument then that is:

info {Object}

• origin {String} The value in the Origin header indicated by the client.

• req {http.IncomingMessage} The client HTTP GET request.

• secure {Boolean} true if req.connection.authorized or req.connection.encrypted is set.

For the part of setting origin properly, you can look at How to set WebSocket Origin Header from Javascript?

I solved, I fix the connection profile. I can conclude that fabric-node-sdk 1.4 can be used with fabric 1.2.

This is as expected. If you take a look at the GitHub repo for ibm-watson - https://github.com/watson-developer-cloud/node-sdk - you will notice that there is no example requiring the top level library. This stops you from pulling in the full library, when you only need to pull in a small sub-component.

The value of the mspid you are passing in to createIdentity is blank. In your config you define the msp id as

The admin was actually correctly set up, or else the orderer would complain about the Admins policy not being satisfied. What has happened is that the orderer has accepted the request and created the genesis block for the channel. It then proceeds to set up a handler to broadcast future blocks for that channel, and in doing so it verifies that its certificate satisfies the /Channel/Writers policy, which is required to call the Broadcast API.

The mentioned policy is by default an of type ImplicitMeta, which means it should be satisfied via /Channel/Orderer//Writers. Because the error message states that only 1 sub-policy needs to be satisfied (i.e. ANY Writers), it means your orderer's certificate does not meet up to its own organization's Writers policy. You need to add the OU type for an orderer to the rule, or set it to member to allow any certificate in the org to act as writer:

(As per the comments in your question.)

Right now you're measuring the latency between India and us-west-2, not the latency of QLDB operations. Please use a region that has lower latency (https://docs.aws.amazon.com/general/latest/gr/qldb.html) or rely on the server-side metrics that you should be able to find in the CloudWatch console.