Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Installing wildcard SSL using the Docker Image

Joe
May 13, 2020

Apparently my google fu is not strong.

According to the documentation I should be able to use the Environment Variable "JVM_SUPPORT_RECOMMENDED_ARGS" to pass the the truststore and keystore variables without having to drop in a custom server.xml file

e.g.

-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/ssl/website.jks -Djavax.net.ssl.trustStoreType=jks -Djavax.net.ssl.trustStorePassword=password -Djavax.net.ssl.keyStore=/var/atlassian/application-data/jira/ssl/website.jks -Djavax.net.ssl.keyStoreType=jks -Djavax.net.ssl.keyStorePassword=password -Djavax.net.ssl.keyStoreAlias=mykey

 

The settings are getting picked up and I can see them being referenced in the logs during startup and I have confirmed that keytool can open the jks within the container using the correct password.

But I can't for the life of me get https://IP:8443 to work, but the non ssl page works fine (aside from an error that the healthcheck is expecting https)

 

has anyone been able to get this to work?

1 answer

0 votes
Joe
May 14, 2020

UPDATE: If I drop in a server.xml file to overwrite the default, it works. So clearly my key isn't the problem.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
7.13.13
TAGS
AUG Leaders

Atlassian Community Events