Hi all,
I've spent all day trying to get this working, and I'm at the tearing-out-hair stage. I hope someone who's done this can help out.
I've followed the Atlassian instructions, and purchased a certificate from GoDaddy. The infobox (on that linked page) about PKCS12 format caused nothing but hours of grief, but the Tomcat instructions from GoDaddy seemed to work fine, and I had a keystore that seemed to have three certificates in it.
Making the changes in server.xml (as per the Atlassian instructions) caused no errors, and there are mentions in the log about "Initializing ProtocolHandler http-bio-443", so it seems to know to start listening on that port.
Feb 16, 2015 2:47:12 PM org.apache.coyote.AbstractProtocol start INFO: Starting ProtocolHandler ["http-bio-8090"] Feb 16, 2015 2:47:12 PM org.apache.coyote.AbstractProtocol start INFO: Starting ProtocolHandler ["http-bio-443"]
Indeed, running s_client shows a successful initial connection (yay!), followed by an error (boo):
jurgen@xx:~$ openssl s_client -connect wiki.xx.xx:443 CONNECTED(00000003) 43062:error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure:/SourceCache/OpenSSL098/OpenSSL098-52.10.1/src/ssl/s23_clnt.c:593:
Running sslscan shows all SSLv2 connections "Rejected", all SSLv3 connections "Failed", and all TLSv1 connections "Rejected".
I'm at a loss of what to do next. What other information can I provide? Is there anything else I can try here?
Thanks, @Renato Rudnicki. I gave that a go, and it's still not working. It's failing more quickly than it did before though, so that's a positive.
I'm going to try starting again from scratch and see how that goes.
Hi Jurgen,
I believe the issue you are facing is described on this documentation from Stash. Could you try the workaround mentioned on the KB and let us know if it works?
Regards,
Renato Rudnicki
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.