Hi, I can run and test my Smart Contract manually using command like this without any error: peer chaincode invoke -o localhost:7050 --ordererTLSHostnameOverride orderer.example.com --tls true --cafil

#fabric-sdk-node

Good day, Thank you for your reply! And apologies for my late reply. For the TLS certificates, I used the registerEnroll.sh script that is included in the test-network files (in /test-network/organiza

#hyperledger-fabric #fabric-sdk-node #fabric-orderer #fabric-peer

My guess has something to do with the TLS certs. In order to access your peers by the HL Fabric client, you need to configure the certificates properly. If you access them by IP instead of FQDN, you s

#hyperledger-fabric #fabric-sdk-node #fabric-orderer #fabric-peer

Hello everyone, I've been running into a problem with a Hyperledger Fabric network that I’ve deployed non-locally and I would like to ask for some insights or assistance regarding this problem. I depl

#hyperledger-fabric #fabric-sdk-node #fabric-orderer #fabric-peer

Those certificate verification failures during the TLS handshake look like a problem to me. I guess the node certificates are not valid for localhost. Maybe you could add entries to your client's loca

#fabric #kubernetes #fabric-sdk-node

Hello, we are running a Hyperledger Fabric network on Kubernetes (using minikube, kubectl to run locally) and then trying to connect the Node SDK with the network. Currently, we have a fabric network

#fabric #kubernetes #fabric-sdk-node

To close the loop on this one... we found that two peers were configured to use a single CouchDB database, and therefore the peers were stepping on each other and getting inconsistency between peer da

#fabric #fabric-peer #fabric-sdk-node #fabric-endorser #fabric-kubernetes

Do you mean the existing v1.4 peers are out of sync? Or you are re-processing all transactions into a new network and the new network peers are out of sync with each other? Or the new peers are out of

#fabric #fabric-peer #fabric-sdk-node #fabric-endorser #fabric-kubernetes

Hi Fabric Experts, Currently I am upgrading our network from HLF 1.4 to 2.2. As our current HLF network using docker and kubernetes we decided to use below approach for the migration. Identify the las

#fabric #fabric-peer #fabric-sdk-node #fabric-endorser #fabric-kubernetes

I think I don't need to change any msp or tls files unless they are expired when upgrading the network. How can I use the TLS CA certificate I was using on v1.2.0 network after upgrading to v2.2.2? He

#fabric-sdk-node #openssl #tls

Yes, docker is installed and local network is up. This is happening at npm install stage likely when chaincode docker image is built.

#fabric-sdk-node #tls #fabric

Do you have Docker installed?

#fabric-sdk-node #tls #fabric

On May 2, 2021, at 10:51 PM, Kevin X <kevinx8888@...> wrote:  I am trying to install chaincode on a mac catalina which has Symantec WSS. I get following error when I try to install chaincode: +

#fabric-sdk-node #tls #fabric

I am trying to install chaincode on a mac catalina which has Symantec WSS. I get following error when I try to install chaincode: + peer lifecycle chaincode install mycc.tar.gz + res=1 Error: chaincod

#fabric-sdk-node #tls #fabric

Is there any way to get a private data collection's history for a particular key in Hyperledger Fabric 2.3? We are using Nodejs for our chaincode implementation I read about a workaround here, which c

#hyperledger-fabric #fabric-sdk-node #fabric-questions

Hi Team, We were investigating to use Azure Key Vault to provide for our wallet services. The CSR, Private and Public Key is basically generated by the Vault and saved securely in the same location. T

#fabric-ca #fabric-ca-client #fabric-sdk-node #fabric

Hi Team, I have a kubernetes setup of HLF2.2 with Golang Chaincode and Nodejs SDK. I am performing load test on the network, when i try with 250 Concurrent thread, it shows unexpectedly chaincode inst

#fabric-sdk-node #fabric-chaincode #docker #fabric-kubernetes #network

Hello Tingli, I have verified with fabric v2.2 and it works fine. We can invoke any qscc from fabric-network sdk. Thank you. Heartfelt Regards, Pavan Adhav Blockchain Developer, Infinichainsphone: 839

#fabric-sdk-node #qscc

Hi Nicholas, It shows in my package.json with "fabric-network": "^2.1.0". Also, thanks for the helpful info! Hi Brett, I see. Thanks for the information. Then I will try it out and get back...

#fabric-sdk-node #qscc

This was a regression, it was patched here: https://github.com/hyperledger/fabric-sdk-node/commit/cbb3ba0aa22d61be6ebe9e258a15e13e3b8ef0d4 You'll need to upgrade to the absolute latest npm package, th

#fabric-sdk-node #qscc