Update channel config transaction
Im trying to update the app channel to add a new admin to the channel (as the previous one is going to expire) but with the attached envelope I get the following error:
Create channel and join error: Create channel error:
Create channel and join error: Create channel error: error should be nil for SaveChannel of orgchannel: create channel failed: create channel failed: SendEnvelope failed: calling orderer ‘orderer1.example.com:7050’ failed: Orderer Client Status Code: (2) CONNECTION_FAILED. Description: dialing connection on target [orderer1.example.com:7050]: connection is in TRANSIENT_FAILURE
Unable to update ServerTLSCert and ClientTLSCert for Orderers
I have a Hyperledger Fabric Network composed of 5 Orderer a 4 Peers.
There is only one channel.
The components are deployed on a Kubernetes
cluster using an NFS
as persistence layer.
The certificates that identifies the Orderer and Peers identities are managed by CertManager
installed on Kubernets
cluster using Helm.
The certificates has been expired and has been renewd by CertManager
automatically but after this updates the network is not working.
I’ve found on the internet that the network must be updated submitting a channel update containing the new certificates for the orderers.
what is the minimum size of EC2 instance for setting up fabric on local machine
I am trying to set up the fabrix test sample given in hyperledger fabric documentation and need to know which EC2 to select.
Hyperledger fabric FabCar sample missing
I just downloaded the latest version of hyperledger fabric which is
Is it possible to store real world data on Hyperledger Fabric? for example a pdf file of healthcare data
Is it possible to store real world data on Hyperledger Fabric? for example a pdf file of healthcare data. If it is possible then can you give a brief idea about how to get started with it?
Does Hyperledger Fabric Gateway Service send a transaction to an orderer if there were not enough endorsement approvals from other peers collected?
Starting from Hyperledger Fabric v2.4 there is a Gateway Service. It helps to make transaction flow more easy for the client. So the client doesn’t need to collect endorsements manually. But the question is what algorithm is used there.