ssl and atlassian

[Phil Jackson]

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.

[Phil Jackson]

I am letting tomcat serve up the SSL. I have been using this tutorial

I was using these tutorials

https://confluence.atlassian.com/adminjiraserver071/running-jira-applications-over-ssl-or-https-802593051.html

https://confluence.atlassian.com/doc/running-confluence-over-ssl-or-https-161203.html

[G__Sylvie_Davies__bit-booster_com_]

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)?