Troubleshooting
Problem
Apps migration from Console to AppHost fails due to a bad certificates on AppHost. Usually, it fails in stage 4 (Starting apps on Target host) and throws "Unable to communicate with API" and "certificate signed by unknown authority" errors.
Symptom
The following error messages can be found in qradar.log file:
<HOSTNAME> dockerd[22742]: http: TLS handshake error from <IP_ADDRESS>:59066: remote error: tls: bad certificate
<HOSTNAME> dockerd[22742]: http: TLS handshake error from <IP_ADDRESS>:59084: remote error: tls: bad certificate
<HOSTNAME> dockerd[22742]: http: TLS handshake error from <IP_ADDRESS>:59100: remote error: tls: bad certificate
<HOSTNAME> dockerd[22742]: http: TLS handshake error from <IP_ADDRESS>:59102: remote error: tls: bad certificate
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSBQAC","label":"IBM Security QRadar SIEM"},"ARM Category":[{"code":"a8m0z000000cwt3AAA","label":"QRadar Apps"}],"ARM Case Number":"","Platform":[{"code":"PF016","label":"Linux"}],"Version":"7.4.0;and future releases"}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
10 February 2023
UID
ibm16856949