Confluence no longer runs over SSL after updating cert and baseurl

[Erik thomas]

We have a site installed confluence server that was running fine over SSL. We've updated the certificate in the keystore and changed the base URL to a new FQDN. We restarted the service and the site will now only run over http. Any guidance would be appreciated!

[Nic Brough -Adaptavist-]

What do you mean by "site will now only run over http?" - I mean, is it even running a connection on https ports, and if so, what are the errors you get when connecting to it?

Also, how are you doing the SSL?  Is it a proxy in front of Confluence or have you enabled it in the Tomcat?

[Erik thomas]

An https connection simply timesout. Http continues to work fine. SSL is enabled in Tomcat. We successfully updated our jira install but confluence refuses all ssl connections after the install of the new cert from the same CA. Server.xml is pointed to the appropriate .keystore file and the correct cert has the alias tomcat and the Base URL has been updated. Using portecle to examine the ssl connection throws a javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated error.

Any ideas of even where to look would be appreciated. Thanks.