Hi @claybuxton ,
would you mind taking us on a little debugging tour?
I think that there is something wrong with the certificate or the keystore but we need to find out what, so let’s burrow the old SSLPoke from Atlassian and see if this one is able to connect successfully
java SSLPoke server 443
this will basically just try to create a TLS session with the server you provide on the port you provide and fail if this session can not be validated. if this is failing, then we know that the error is the keystore or the certificate for sure.
the next point to look for information is to extract the archive and have a look at the extensions using javas keytool:
keytool -list -v -keystore path_to_keystore_file
keytool -export -alias alias_name -keystore path_to_keystore_file -rfc -file path_to_certificate_file
- alias_name: Specifies the same alias that was used to generate the certificate.
- path_to_keystore_file: Specifies the same KeyStore path that was used to generate the certificate.
- path_to_certificate_file: Specifies the exported certificate file, often given an extension of .cert.
you should be able to check the resulting certificate using openssl
hope that gives us a little more insight what’s going on here