failed to create new connection context deadline exceeded error in Hyperledger Fabric

Question

I am practising the Build your first network tutorial. When I run ./byfn.sh up, I get the following error:

Error: error getting endorser client chaincode: endorser client failed to connect to peer0.org1.example.com:7051 failed to create new connection context deadline exceeded.

How to solve this?

Answer 1

Try remove previous docker containers(have mentioned the command below) and then restart the network.

$ docker rm -f $(docker ps -aq) && docker rmi -f $(docker images | grep dev | awk '{print $3}') && docker volume prune

Comments

Hi @Kiran. That error got resolved. Now I am getting some binaries related error.

---

Try re-installing platform-specific binaries. Under the fabric-samples, run the following command:

$ curl -sSL http://bit.ly/2ysbOFE | bash -s 1.2.0

 

Answer 2

It seems like them are old configuration existing which is conflicting with your command. First run  ./byfn.sh down and then bring you network up using  ./byfn.sh up. This should help.

Comments

Tried it, didn't work. Please help. Another other solution?

Answer 3

I was facing the same issue. I tried many solutions but it didn't work. What finally worked for me is updating docker. I executed the below command and restarted the network and the error was solved. 

$ sudo apt-get install docker-engine

Comments

Updating docker didn't work for me. Any other solutions?

---

I think the changes I made while trying other solutions also contributed to solving the problem along with updating docker. It was a long time ago, so I don't remember. I'll post once I remember what I had tried.

---

Okay, so I was trying some solutions and found out the problem was with the peer.listenAdress. Setting it to the right address solved the problem. 

---

This wasn't what I tried but if it worked for you, could work for others too. I think you should post this as an answer.

Answer 4

Check for the peer.listenAdress in your configuration files. I was getting this error because I had set a wrong address and after I set the right address, the error was solved.