Upma

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

I did some testing, radically simplifying the system. I tried simply having 1 TLS, 2 Orderers, and 2 Root CAs with a peer on each. If I set one orderer I have no problems but if I add another one on a

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

I think my problem is in the configtx.yaml and it depends either on a wrong orderers communication or on the incorrect insertion of the intermediate in the configuration file. I enclose the configtx.y

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

It certainly looks like there is some connection error from the client to 172.19.0.9:7055 but hard to know the root cause. Assuming the client really can establish a connection to that host/port, it c

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

Hello everyone, i'm having some problems starting the "peer channel create" command. I have a network with 1 TLS-CA, 3 ROOT-CA and 1 INTERMEDIATE-CA. My peer is running on the intermediate CA. When i

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

Hi all, I am creating a network with CA roots and CA intermediates using fabric CA and docker compose. So far I have been able to correctly create the roots, intermediates, perform registration and en

#docker-compose #docker #fabric-ca

Hi Kavin, From what I can see, you commented out the docker configuration files, going to directly edit the server configuration files. This way it actually works but what I was trying to do was to us

#fabric-ca #docker

Hello, I have been making changes to the docker file attempting to replicate what is done here https://hyperledger-fabric-ca.readthedocs.io/en/latest/deployguide/cadeploy.html using docker compose. I

#fabric-ca #docker

I am trying to setup blockchain network with two organizations having two peers in each organization. I generated crypto material using fabric-ca-server-client command after setting up separate CAs fo

#fabric-ca

Hi Kavin, I have already read the documentation and when I try to manually set the configuration files I have no problem. The problems arise when I start using docker-compose. First of all in the docu

#fabric-ca #docker

Hi Famar, Thanks & Regards Kavin Arumugam

#fabric-ca #docker

Hello everyone, I'm trying to implement a test fabric network by setting 1 TLS-CA, 1 ROOT-CA, 1 ORG, 1 Orderer and 1 Intermediate CA. I'm having some trouble implementing intermediate CA with docker.

#fabric-ca #docker

Just in case if this helps: [FAB-18384] admin certs and tls certs expired after 1 year - Hyperledger JIRA Regards, Satheesh

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

Hi, I had set up a hyperledger fabric network (v1.4.2) with few orgs a year back in a kubernetes cluster using Hyperledger Bevel. Each org has its own CA and TLSCA servers running with TLS enabled. Th

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

When trying to register a new user on one of our Organizations, in this case, organization "MedicOrg" (with its corresponding MSP, certs, peers and CAs), I get the following error where an admin is en

#affiliations #fabric-ca #fabric-ca-client #hyperledger-fabric

It relates to how the CA works. The peer knows the Root CA of the Org through the peer's MSP files. It can then verifies the incoming certificates against the Root CA. Just as verifying the certificat

#fabric-peer #fabric-ca

Hi, I was reading the source code of hyperledger fabric, and reading the log of a peer in a DEBUG mode. I wonder how fabric peer know the information of the certificate authorites of its own Org? For

#fabric-peer #fabric-ca

Hello, I'm currently working on a project with three organizations and an orderer. So in order to do this, I created a new network, with its own configuration files and with a script that sets up ever

#docker #fabric-ca #fabric-orderer #orderer #organizations

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

The peer are emitting the error logs as:

#fabric-ca #fabric