During the process of CDH cluster encryption, the following error occurred when the signed certificate information was imported into the secret key library
keytool error: java.lang.Exception: Failed to establish chain from reply
Didn’t solve the problem, find a lot of articles, baidu search to an article in English https://www.veritas.com/support/en_US/article.000021204 later
The following is mentioned:
keytool error: java.lang.Exception: Failed to establish chain from reply
Didn’t solve the problem, find a lot of articles, baidu search to an article in English https://www.veritas.com/support/en_US/article.000021204 later
The following is mentioned:
Problem
When importing an SSL certificate to Clearwell’s keystore, an error is encountered.
Error Message
keytool error: java.lang.Exception: Failed to establish chain from reply
Cause
Root and/or Intermediate certificates have not been imported order.
I checked that I commented out the original step and did not execute it
That is, import the self-signed certificate (that is, my root certificate) information into the server secret key library
Modify the following, perform this step first, then perform normal.
Summary: The order in which certificates are imported into the secret key library is important, and if there is a root certificate or a multi-level certificate authority, they must be imported level by level from top to bottom.
Read More:
- Keytool error: java.io.FileNotFoundException : MyAndroidKey.keystore (access denied)
- OpenJDK11 failed: PKIX path building failed XXXXX
- Was import certificate — error prompt: java.security.cert .CertPathValidatorException: Certificate chaining error
- Certificate chaining error in sphere
- K8s configure HTTPS with existing certificate
- cURL error 60: SSL certificate problem: self signed certificate in certificate chain
- Extraskloatitles failed error = 22
- cas report error (No subject,’principal’ cannot be null, PKIX path validation failed, etc.)
- Spark login error unable to verify certificate and certificate host name verification failed
- To the brothers who encountered simple bind failed 192.168.1.×××: 636
- Error:Failed to create provisioning profile. – iOS
- Apache failed to start due to SSL library certificate has expired
- Python – SSL certificate error
- gvim: GConf-WARNING **: Client failed to connect to the D-BUS daemon
- The Ethereum private chain is built, and the block information cannot be synchronized. The error is resolved: Node data write error err=”state node failed with all peers(1 tries, 1 peers)
- E / Art: failed sending reply to debugger: a solution to broken pipe
- command/usr/bin/codesign failed with exit code 1- code sign error
- ssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed
- Error generating Ca in OpenSSL: TXT_ DB error number 2
- Solution: unity package failed. Commandinvocationfailure: gradle build failed