Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Trying to enable HTTPs in JIRA server - change the server.xml file


We made changes following the link (  but from some reason that did not work for us. 

We used again backup file for server.xml and web.xml and it work fine for HTTP. 

Now again when I want to test HTTPs I will follow all steps from link that is noted and after we make changes in JIRA Configuration tool we have to make changes in server.xml with this part: 

<Connector port="8443" protocol="org.apache.coyote.http11.Http11NioProtocol"
maxHttpHeaderSize="8192" SSLEnabled="true"
maxThreads="150" minSpareThreads="25"
enableLookups="false" disableUploadTimeout="true"
acceptCount="100" scheme="https" secure="true"
clientAuth="false" useBodyEncodingForURI="true"
keyAlias="jira" keystoreFile="<Jira_HOME>/jira.jks" keystorePass="changeit" keystoreType="JKS"/>


Connector that is now active for HTTP will remain same (without any other changes)?

Do we have to make changes in web.xml as well? 

Thank You! 

1 answer

1 accepted

1 vote
Answer accepted
Thomas Deiler Community Leader Jul 17, 2019

Dear @Samira Spago ,

I strongly recommend the use of a reverse proxy (Apache,nginx, ...) that terminates SSL instead of enabling this in Tomcat. If you running on Linux you can follow my article how to set up with nginx. 

This is best practice and also recommended by Atlassian.

So long


Dear @Thomas Deiler 

we resolved this issue without recommended use of a reverse proxy. But now there is problem with gadget layout on Dashboard with message "gadget.common.error.500" . 

We followed some of the answers on Community with similar issue but none of them helped with resloving this part. 

Does this "gadget.common.error.500" message can be resolved with reverse proxy or it is  another cause of this problem?


Thank You 


Thomas Deiler Community Leader Jul 18, 2019

Dear Samira,

most probably this is a SSL cert issue. Jira connects to itself via Rest API. When the SSL cert is selfsigned it has to be added to the Java keystore to be recognized.

So long


Dear @Thomas Deiler

as I found in one of the posts here on Community Atlassian about adding cert to the Java keystore and following Your instruction about this issue now I can confirm that we added our two SSL cert to the Java Keystore (image below). 

Do I need to restart Jira server now after adding cert to java keystore? Untitled.png


Thank You 


Thomas Deiler Community Leader Jul 19, 2019

Dear @Samira Spago ,

yes. Modifying the keystore will require the java app to reload this information.

So long


Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira

Do you use Jira Cloud with Microsoft Teams?

Hi, Jira users! Do you use Jira alongside Microsoft Teams? We want to hear how you’ve used the power of Jira Cloud and Microsoft Teams (via the Jira Cloud for Microsoft Teams app) to achieve a team...

251 views 1 5
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you