TLS Handshake error at peer after trying to invoke chaincode via fabric SDK
Closed this issue · 8 comments
Created connection profile for a org and using fabric SDK sucessfully created an admin identity along with an user in an wallet , After that while invoking the chaincode through SDK getting Discovery error and cannot connect through the fabric Gateway , After checking peer logs could find that we are getting TLS handshake error replaced the TLS certs with differnt certs generated through the script , If you can guide us will be helpful
please, run "docker ps -a" and send your result here.
which certificate path should i replace here with
Please, list and show your Docker Fabric domains/example.com folders
The peer0.org0 tlsCACert path is in
peerOganizations/org0/peer1.org0/tls/tlscacerts/tls-cert.pem
Your connection profile config file is using variables, take care with them to reflect the right path of this cert file for each peer
If docker is running in your host, use "localhost" instead of an IP address.
An important detail: Docker Fabric Wizard doesn't create a first peer on each org with zero (0) in its name.....always start with 1.
Take a look in your "docker ps -a" command and in your folder list results.
A tip: Take a look on domains//setup.json file
organizations/peers//volumes shows the whole path for certicate files used by each peer.