jira SSL Configuration error

Question

Hi All

we are facing trouble in connecting jira to SSL

We have .pfx file in jira server. and port 443

also edited the server.xml file by adding the below lines

KeystoreFile="xyz\abc.pfx"

keystorePass="nsjkc'

keystoreType="PKCS12"

keyAlias="tomcat"

we are getting the jira page for http://localhost:443

and https://localhost:443 : we getting the error this page cannot provide a secure connection error

Firewall, Antivirus is disabled. also, we have imported the certificate to chrome browser(trusted root certificate)

Is it an Infra error? if not let me know where we are failing in the configuration

Regards,

Pooja

Nic Brough -Adaptavist- · Answer

Server is the service that is running - in this case, Jira.  Client is something that connects to it to use it (usually a browser)

You say you have configured as per Atlassian recommendation, but the error you are getting is almost certainly telling you that you have not.

Could you explain all of your configuration?  Assuming you have Jira running on a server and you started with the basics, such that Jira was running ok on plain http on port 8080 - what have you changed on top of that?  And what Atlassian documentation did you work from?  (We know you've added the certificate to the server.xml and the browser, but how have you done the rest of the SSL setup?)

Pooja_lp8tti · Answer

@Nic Brough -Adaptavist-

Thank you for the suggestion

What are these server and client means?

We have removed the chrome cache as per your suggestion

Are you behind a proxy? No, we are not using any proxy

Is that configured for https / SSL correctly: we have configured as per Atlassian recommendation

And is the server configured hand over a full https connection to it (no mixed content or redirects to non-httpss/ssl stuff?) : I am not getting this point could you share any document regarding this point

Nic Brough -Adaptavist- · Answer

Ok, you've checked antivirus, so not that, but have you

* checked the date/time on server and client are very close
* tried clearing the chrome caches* SSL state (hidden in settings -> proxy -> "clear ssl state")
* Browsing history

* Are you using an insecure protocol on the server, like TLS 1.0 and 1.1?

Once you've run through those, the next thing to look at is definitely the infrastructure between server and client.  Are you behind a proxy?  Is that configured for https / ssl correctly?  And is the server configured hand over a full https connection to it (no mixed content or redirects to non https/ssl stuff?)