ssl and atlassian

I am working to split out our Atlassian products on separate servers, and I am having issues with getting the SSL working on them. I have a wildcard certificate in hand, so I don't need to request a new one. I used portecle to import the wildcard certificate into the cacerts file that was setup for each Atlassian product. I also imported it into cacerts that is in the java as well. I am new to doing this certificate stuff, and I am not quite sure if I am doing it right, but I have configured everything and pointed the Atlassian app to the cacert file, and when I go to the https site, I get a "refused to connect" error.

ps: The products that I am trying this on is crucible, jira, confluence and bitbucket, with all the same error.

2 answers

Are you changing their port (e.g., to 443)?   Or are you putting them behind a reverse-proxy (e.g., Apache with ProxyPass / ProxyPassReverse)?   Or are you letting them serve SSL themselves through Tomcat on their default ports (e.g., 8443)?

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,331 views 14 20
Join discussion

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot