[FAB-8091] doc possible backlevel shim on tls err

Update the text on debugging a remote error: tls: bad
certificate message to remind the user that a chaincode
is a peer client also, and that using an old version of
the chaincode shim might result in this error.

Change-Id: I05dae9a57625301196500b5d9127ec3e7e3f8c81
Signed-off-by: Luis Sanchez <sanchezl@us.ibm.com>

docs/source/enable_tls.rst

@@ -120,5 +120,12 @@ not receive the correct client certificate or it received a client certificate t
 not trust. Make sure the client is sending its certificate and that it has been signed by one
 of the CA certificates trusted by the peer or orderer node.
 
+If you see the error message ``remote error: tls: bad certificate`` in your chaincode logs,
+ensure that your chaincode has been built using the chaincode shim provided with Fabric v1.1
+or newer. If your chaincode does not contain a vendored copy of the shim, deleting the
+chaincode container and restarting its peer will rebuild the chaincode container using the
+current shim version. If your chaincode vendored a previous version of the shim, review the
+documentation on how to :ref:`upgrade-vendored-shim`.
+
 .. Licensed under Creative Commons Attribution 4.0 International License
    https://creativecommons.org/licenses/by/4.0/

docs/source/upgrade_to_one_point_one.rst

@@ -130,6 +130,8 @@ Repeat this process for each orderer.
 
 .. note:: We repeat. Pay close attention to your orderer upgrades. State forks are bad.
 
+.. _upgrade-vendored-shim:
+
 Upgrade Chaincodes With Vendored Shim
 -------------------------------------