TLS握手失败，出现错误远程错误:TLS:bad certificate server=Orderer remotead

Question

我正在尝试在多台机器上部署hyperledger fabric(v1.4.3(solo模式，角色ip映射如下：

orderer          192.168.1.251
peer0.org1       192.168.1.249
peer0.org2       192.168.1.248
peer1.org1       192.168.1.247
peer1.org2       192.168.1.246

我将fabric-samples/first-network复制到first中，并删除一些文件，first文件夹包含：

├── base
│   ├── docker-compose-base.yaml
│   └── peer-base.yaml
├── channel-artifacts
├── configtx.yaml
├── crypto-config.yaml
├── docker-compose-cli.yaml
byfn.sh

我保持crypto-config.yaml和configtx.yaml与fabric-samples相同，只是更改了docker-compose-cli.yaml。

orderer的docker-compose-cli.yaml:

# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#
version: '2'
volumes:
orderer.example.com:
networks:
byfn:
services:
orderer.example.com:
extends:
file:   base/docker-compose-base.yaml
service: orderer.example.com
container_name: orderer.example.com
networks:
- byfn

peer0.org1的docker-compose-cli.yaml:

# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#
version: '2'
volumes:
peer0.org1.example.com:
networks:
byfn:
services:
peer0.org1.example.com:
container_name: peer0.org1.example.com
extends:
file:  base/docker-compose-base.yaml
service: peer0.org1.example.com
networks:
- byfn
extra_hosts:
- "orderer.example.com:192.168.1.251"
- "peer1.org1.example.com:192.168.1.247"
- "peer0.org2.example.com:192.168.1.248"
- "peer1.org2.example.com:192.168.1.246"
cli:
container_name: cli
image: hyperledger/fabric-tools:$IMAGE_TAG
tty: true
stdin_open: true
environment:
- SYS_CHANNEL=$SYS_CHANNEL
- GOPATH=/opt/gopath
- CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
- FABRIC_LOGGING_SPEC=DEBUG
#- FABRIC_LOGGING_SPEC=INFO
- CORE_PEER_ID=cli
- CORE_PEER_ADDRESS=peer0.org1.example.com:7051             # change in different peer
- CORE_PEER_LOCALMSPID=Org1MSP                              # change in different peer
- CORE_PEER_TLS_ENABLED=true
- CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.crt      # change in different peer and org
- CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.key       # change in different peer and org
- CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt      # change in different peer and org
- CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/[e-mail]/msp      # change in different org
working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
command: /bin/bash
volumes:
- /var/run/:/host/var/run/
- ./../chaincode/:/opt/gopath/src/github.com/chaincode
- ./crypto-config:/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/
- ./scripts:/opt/gopath/src/github.com/hyperledger/fabric/peer/scripts/
- ./channel-artifacts:/opt/gopath/src/github.com/hyperledger/fabric/peer/channel-artifacts
depends_on:
- peer0.org1.example.com
networks:
- byfn
extra_hosts:
- "orderer.example.com:192.168.1.251"
- "peer0.org1.example.com:192.168.1.249"
- "peer1.org1.example.com:192.168.1.247"
- "peer0.org2.example.com:192.168.1.248"
- "peer1.org2.example.com:192.168.1.246"

另一个peer更改为上面yaml文件中的注释。我使用./byfn.sh generate在每个peer和orderer上生成通道工件，然后在peer0.org1(192.168.1.249(cli容器中，我成功地安装了链代码，但当我实例化链代码时，我看到orderer控制台抛出错误：

[core.comm] ServerHandshake -> ERRO 009 TLS handshake failed with error remote error: tls: bad certificate server=Orderer remoteaddress=192.168.1.249:58812

我注意到这种错误也发生在同行之间，我已经尝试了几种方法，但都失败了。有人能帮我吗也欢迎任何在kafka模式下部署hyperledger结构的教程！

谨致问候！

Answer 1

最后，我在创建genesis.block时删除了-channelID mychannel参数，从而解决了这个问题。我不知道为什么，所以如果有任何建议，请在这里评论。