Known issues

This page describes known issues that you might encounter when you use IBM Blockchain Platform v2.1.3.

Important: You are not looking at the latest product documentation. Make sure you are reading the documentation that matches the version of the software that you are using. Switch to product version 2.1.3, 2.5, 2.5.1, 2.5.2 (latest)

Certificate Authority patch install fails

After upgrading from IBM Blockchain Platform v2.1.2 to v2.1.3, installing the patch on a CA node fails. To resolve this problem see the Troubleshooting topic.

Chrome browser on Mac OS Catalina

The console will not work in the Chrome browser on Mac OS Catalina when the IBM Blockchain Platform v2.1.0 or v2.1.1 is deployed with the default configuration that uses self-signed certificates. There are three ways to resolve this problem:

Use a different supported browser with Catalina.
Use your own TLS certificates when deploying on OpenShift Container Platform or TLS certificates when deploying on Kubernetes or IBM Cloud Private.
Run the following commands to generate a new key and certificate pair for the console that will fix the problem.
1. Run the following command to get the pod that corresponds to the console:
```
 kubectl get po
```
2. Exec into the pod by running the command:
```
 kubectl get po <pod-name> -c optools bash
```
3. Delete the console key and certificate by running the command:
```
 rm -f /certs/tls.key rm -f /certs/tls.crt
```
4. Delete the console pod which causes it to restart by running the command:
```
 kubectl delete po <pod-name>
```
When the pod restart completes, you should now be able to log in to your console URL from a Chrome Browser.