【问题标题】:Hyperledger anchor peers cannot communicate with each other because of tls bad certificate由于 tls 证书错误,Hyperledger 锚节点无法相互通信
【发布时间】:2021-04-14 03:27:49
【问题描述】:

我创建了一个超级账本结构通道 [channel1],其中包含两个对等组织**(Org1,Org2)** 和一个订购者组织 (OrdererOrg),然后是每个对等组织中的一个对等点(peer0.org1.com/peer0.org2.com)和排序者组织中的三个排序节点**[Orderer0, Orderer1, Orderer 2]**。将排序节点和对等节点加入通道并将 [peer0.org1.com] 和 [peer0.org2.com] 设置为锚节点后,在对等节点日志中打印以下错误:

peer0.org1.com

2021-04-14 10:53:08.108 CST [core.comm] ServerHandshake -> ERRO 1a2 Server TLS handshake failed in 962.117µs with error remote error: tls: bad certificate server=PeerServer remoteaddress=127.0.0.1:58281
2021-04-14 10:53:09.112 CST [core.comm] ServerHandshake -> ERRO 1a3 Server TLS handshake failed in 2.162124ms with error remote error: tls: bad certificate server=PeerServer remoteaddress=127.0.0.1:58283
2021-04-14 10:53:10.836 CST [core.comm] ServerHandshake -> ERRO 1a4 Server TLS handshake failed in 1.629684ms with error remote error: tls: bad certificate server=PeerServer remote address=127.0.0.1:58285

peer0.org2.com

2021-04-14 10:53:11.107 CST [gossip.gossip] func1 -> WARN 12f Deep probe of localhost:20000 for channel channel1 failed: context deadline exceeded
2021-04-14 10:53:11.108 CST [gossip.discovery] func1 -> WARN 130 Could not connect to Endpoint: localhost:20000, InternalEndpoint: localhost:20000, PKI-ID: <nil>, Metadata:  : context deadline exceeded

configtx.yaml

core.yaml of [peer0.org1.com]

core.yaml of [peer0.org2.com]

我遵循的教程:

Creating a channel

【问题讨论】:

    标签: hyperledger-fabric hyperledger


    【解决方案1】:

    我通过向组织 msp 添加一个名为 tlscacerts 的文件夹解决了这个问题。 注意到在测试网络 /test-network/organizations/peerOrganizations/org1.example.com/msp/tlscacerts/ enter image description here 将您的 tls 根 ca 证书复制到其中。

    【讨论】:

      猜你喜欢
      • 1970-01-01
      • 1970-01-01
      • 2016-08-19
      • 1970-01-01
      • 2018-11-23
      • 2016-03-19
      • 1970-01-01
      • 1970-01-01
      • 2020-10-11
      相关资源
      最近更新 更多