fabric-common | not a fork | Runtime Evironment library

From the network file you posted a couple of points

1. you can't define any nodes in it (for example you've added orderers). They are ignored
2. you've specified that your connection profile is a dynamic profile by setting discover to true in your network file, this means it will use discovery to determine the network topology and may not use the nodes you have explicitly defined in your connection profile. If you want to be explicit in your connection profile (and thus define a static connection profile) like you have in your above example, you should set discover to false, which hopefully will solve your problem.

As a side note, if you use discovery then the node-sdk (used by caliper) and caliper by default converts all discovered node hosts to localhost, which is why you see it trying to contact localhost. To disable this see Runtime settings in https://hyperledger.github.io/caliper/v0.4.2/fabric-config/new/

This is the issue reported in this Jira: https://jira.hyperledger.org/browse/FABN-1657

It should be fixed in current npm packages tagged unstable-2.2, and in a forthcoming v2.2.9 release of the Node SDK.

All configurations seems good, however you have to upgrade explorer version to be compatible with hyperledger fabric version.

So please use v1.1.4 instead of v1.1.1

Also make sure that you have mounted crypto config correctly, try to access this path inside the container /tmp/crypto/peerOrganizations/acme.com/tlsca/tlsca.acme.com-cert.pem

Try to change tlsCACerts path to use peer tls ca.crt /tmp/crypto/peerOrganizations/acme.com/peers/peer1.acme.com/tls/ca.crt

You have mentioned that the same configurations works with hyperledger fabric v2, if you have tried it locally not on the same server so I please disable the firewall on the server and give it a try

To check if you can reach domain and port please try this

cat > /dev/tcp/peer1.acme.com/7051

Check this https://support.bluemedora.com/s/article/Using-Bash-to-test-if-a-TCP-port-on-a-remote-system-is-open

So the problem was that I was using node v12.6.0 which is required by fabric-common module. When I downgraded node version to v11.6.0 and installed dependencies with flag --ignore-engines everything worked as expected.

Your network config file is not complete. Caliper still has to explicitly know about the chaincodes (aka contracts) that have been deployed onto your channels. Referring to this section in the tutorial https://hyperledger.github.io/caliper/v0.4.2/fabric-tutorial/tutorials-fabric-existing/#populating-the-template-file you will see a section on Channels which describe adding information about channels to the network config file. For example from that tutorial it defines this section

You try a gRPC call in peer Server where peer server is secured with it's TLS system. So if you fail to provide the valid TLS certificate, server tls handshake will be failed and you will not get success to establish the connection.

Please check that your network config file is properly develop, also check that you are using the same TLS certificate that is used to run the peer server and your TLS certificate path is correct.

The number of concurrent requests to the peer services has been capped by default in Fabric v2.1.0+ to prevent poorly programmed or malicious clients from DoS-ing the peers. You can always remove this restriction, or increase it by modifying these values in core.yaml. To remove the restriction, set the limit to 0, or increase it to a value that makes sense for your environment.

Generally speaking, if these messages are occurring, it is because the client application is misbehaving and not appropriately releasing resources. Once a client is done with a particular call, it's important to close and cleanup the associated network resources. A common source of leaks for connections to the peer is requesting event streams, reading one event, and then opening a new one without closing the previous.