paulrusu8
paulrusu8
My network.json file is as follows: ``` { "name": "common", "version": "1.0", "client": { "organization": "AtlantisMSP", "connection": { "timeout": { "peer": { "endorser": "30000" }, "orderer": "30000" } } },...
Thanks for the comment. I tried to replace it, but to no avail. It still shows the same error.
My intuition is that it is the wrong certificate, but in a similar setup, it was in the same location and it did not throw this warning.
Went through your list: 1. I just recopied the files. 2. I have implemented your template channelflow. 3. Yes. That is why curling the peers from the container pod actually...
My problem is that in a previous configuration without tls, it worked pretty well without the cryptoStore and credentialStore keys. I guess I should first look into how to authenticate...
But with Kafka Orderers.
But the setup was very unstable, didn't have tls, no backup/persistence, and surely not your professional helm charting. Alas, it seems that transitioning will be a little harder than I...
Let's see. I am also very interested by the raft-concept as it seems more suitable for hyperledger than kafka.
You are right. I will give it a try and keep you updated. Thanks for the support.