You can find docker file of Fabric peers here: https://github.com/hyperledger/fabric/blob/release-1.4/images/peer/Dockerfile.in Best regards, Artem Barger.

#fabric #fabric-peer #fabric-orderer #fabric-ca

Hi zhuxy Please see my comments inline. Thanks! Different sections are convenient to have corresponding policy controls on orderer orgs and app orgs. For example, you can set one default policy for or

#fabric-orderer #fabric

I've noticed that the Orderers are arranged in the same org(called OrdererOrg) in both fabric 1.4 and 2.2. So here's my questions: - Why the orderers are arranged in OrdererOrg instead of Org1 or Org2

#fabric-orderer #fabric

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

Hi Ramesh, 1: In my situation I had all the certs expired, both admin (peer and orderers), TLS and MSP certs. 2: You need to sign with old certs in orderer tu run the update, if I recall correctly the

#fabric-questions #fabric-orderer #signcerts #fabric

Hi Mattia, Doubt1:. Does your both Orderer admin certs and Peer admin certs got expired or only Orderer admin certs got expired? In my case both Orderer admin certs and Peer admin certs got expired. D

#fabric-questions #fabric-orderer #signcerts #fabric

Mattia,Ramesh, If you have not seen Minifabric, you probably can take a few minutes looking into that. It allows you to deploy fabric in literally few minutes and allows you to update channel configur

#fabric-questions #fabric-orderer #signcerts #fabric

Hi Ramesh, Doubt 1: If i have understood correctly, for every update I followed the usual procces for channel update which is: fetch the latest config block decode to json copy the decoded json modifi

#fabric-questions #fabric-orderer #signcerts #fabric

Hi Mattia and Chris, Thank you for your suggestions. update orderer admin certs first in system channel then in every other application channel update peer admin certs first in system channle then in

#fabric-questions #fabric-orderer #signcerts #fabric

Ramesh, When you sign the channel config update transaction, it has to be with the old certs. Mattia, I am glad you were able to recover. Chris

#fabric-questions #fabric-orderer #signcerts #fabric

Hi Ramesh, I've managed to restore my production network but without adding new org. I think it's better if you first restore the network and then add the new organization (having an extra org involve

#fabric-questions #fabric-orderer #signcerts #fabric

Hi Mattia Bolzonella, Is this issue resolved? Even I am facing similar issue related to my certs got expired. I have created new certs and replaced in the same folder as before and my application is w

#fabric-questions #fabric-orderer #signcerts #fabric

Hi Chris, Thanks for the advice, the certs are correct. I will explain better the situation: Currently I have 2 channels, 3 orderers with the TLS certs expired. the system channel an application chann

#fabric-questions #fabric-orderer #signcerts #fabric

Hi Mattia, You have a cert mismatch. Make sure to double check where you placed the newly created certs and make sure they match. Chris

#fabric-questions #fabric-orderer #signcerts #fabric

Hi Chris, I updated one orderer TLS certs in the system channel but it's not included in the raft consensus. If i try to fecth the channel confing block from the updated orderer i get SERVICE UNAVAILA

#fabric-questions #fabric-orderer #signcerts #fabric

Hi, I'm working on the solution proposed, now I'm using a cli peer to do my channel update operations, before doing that I set the following variables in the peer cli: CORE_PEER_LOCALMSPID=MyOrderersM

#fabric-questions #fabric-orderer #signcerts #fabric

Yes, that is it. You got it!

#fabric-questions #fabric-orderer #signcerts #fabric

Just to be clear about what you told me to replace in my system channel configuration, sorry but I want to be 100% sure about what I'm doing: My json looks like this: "channel_group": { "groups": { "A

#fabric-questions #fabric-orderer #signcerts #fabric