I am getting "Unable to connect via SSL" error. What could be the reason ?
Please check if you have followed the prerequisites
for adding IBM Websphere MQ monitor via SSL.
"Unable to connect via SSL" error could occur due to following reasons :
- SSL is enabled for the channel, but SSL Enabled option is not selected in add/edit monitor page.
- Run display channel ( channelname ) MQSC command and check if SSLCIPH is configured.
- IBM MQ certificate is not imported in Applications Manager.
- SSL Ciphersuite provided in new/edit monitor page is not the same as configured in the channel.
- The label of the certificate is not in the format "ibmwebspheremq<QueueManagerName>
Refer the prerequisites
page to know how to import/ export certificates.
LDAP - Unable to find valid SSL Certificate
If there is an error while adding LDAP Server Monitor with the message "Unable to find valid SSL Certificate", then please try the below steps to troubleshoot the issue. When the error occurs we can find the below traces in the "stderr.txt.*" log ...
Troubleshooting SSL Handshake Error
SSL Handshake Error SSL Handshake error occurs when a secure connection cannot be established to the URL added for monitoring. Common reasons for it are wrong SSL protocol version, incompatible ciphers, and invalid/missing client-side certificate. ...
How to monitor SSL Certificate of FTPS server?
Two modes to invoke client security in FTPS Explicit mode Implicit mode Explicit mode (Default port 21) - This port shouldn't be used In Explicit mode, an FTPS client must "explicitly request" security from an FTPS server by sending an FTP command ...
How to import certificates for monitoring Postgres Server with SSL authentication?
Error Message: The connection attempt failed! Reason: This error occurs when you are trying to add an SSL enabled server but the certificates which are used for SSL connection are not present in the cacerts. Solution: To import certificates, ...
How to import certificates for monitoring DB2 Server with SSL authentication?
By default, if you want to use self-signed certificates for SSL connection then the certificate generated by the DB2 server will be db2server.arm. But our AppManager doesn't support arm files. So it has to be renamed as the db2server.cer and then ...