Unable to configure SSL due to Incorrect Java home or invalid keystore
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
After Configuring JIRA applications to run over SSL, JIRA applications starts but does not give access over port 443 or 8443. Logs contain:
1
2
SEVERE: Failed to load keystore type JKS with path /usr/local/jira/.keystore due to Keystore was tampered with, or password was incorrect
java.io.IOException: Keystore was tampered with, or password was incorrect
Causes and Resolutions
Add SSL Certificates automatically!
If you'd prefer to do this through the UI, we now have an Atlassian Labs plugin for this process.
The keystore file is specified incorrectly in
conf/server.xml. Check to make sure you specified the correct location and password with the keystorePass="<password value>" parameter.Check to make sure you're using the same password for the keystore when you use the keytool command to create it.
Make sure java_home is set correctly. See Installing Java.
Was this helpful?