while accessing the on premise apian url via Chrome then getting invalid cert error

while accessing the on premise apian url via Chrome then getting invalid cert error.

 

It is showing Not secure message and invalid certificate. We have been using the same url and it was working fine.

 

I have requested for new certificate and it is placed in one of the directory.

 

Now I don't know which are all files I need to copy & replace in existing key store folder which is being referred by Appian settings.

 

Please suggest.

  Discussion posts and replies are publicly visible

Parents
  • I recently encountered the same issue while accessing my on-premise Appian URL in Chrome, and it displayed ERR_CERT_AUTHORITY_INVALID with the message “Not Secure / Invalid Certificate.”

    In my case, the problem happened after requesting and placing a new certificate, but I wasn’t sure which files to update in the keystore. What helped me was:

    • Making sure the new certificate, private key, and intermediate/CA bundle were all imported into the same keystore.

    • Replacing the old keystore file that Appian refers to in its settings (usually custom.properties or server.xml Depending on the setup.

    • Restart the application server so Appian picks up the updated keystore.

    If the CA chain or intermediate certs are missing, browsers like Chrome will still show the error.

    I found the article helpful for step-by-step guidance on fixing the error with new SSL/TLS certificates at:- https://certera.com/kb/how-to-fix-net-err_cert_authority_invalid-error-in-chrome/. Hope it helps!

Reply
  • I recently encountered the same issue while accessing my on-premise Appian URL in Chrome, and it displayed ERR_CERT_AUTHORITY_INVALID with the message “Not Secure / Invalid Certificate.”

    In my case, the problem happened after requesting and placing a new certificate, but I wasn’t sure which files to update in the keystore. What helped me was:

    • Making sure the new certificate, private key, and intermediate/CA bundle were all imported into the same keystore.

    • Replacing the old keystore file that Appian refers to in its settings (usually custom.properties or server.xml Depending on the setup.

    • Restart the application server so Appian picks up the updated keystore.

    If the CA chain or intermediate certs are missing, browsers like Chrome will still show the error.

    I found the article helpful for step-by-step guidance on fixing the error with new SSL/TLS certificates at:- https://certera.com/kb/how-to-fix-net-err_cert_authority_invalid-error-in-chrome/. Hope it helps!

Children
No Data