Showing results for 
Search instead for 
Did you mean: 
Sign up Log in


Jira Stuff November 24, 2022

Hi everyone,

I hope someone can provide me a hint how to solve this problem with "ERR_SSL_PROTOCOL_ERROR" when I try to open my Basis-URL: https://server-jira-t.domain.local

Thank you

1 answer

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 24, 2022

Welcome to the Atlassian Community!

This means that your Jira is running on https, and your browser is not able to negotiate the right secure connection configuration with it.  

(This is vastly over-simplified to try to keep it simple for us human end-users, before any SSL experts leap in)

What happens with most secure (https) sites is a browser hits them, and asks "how do we encrypt our conversation?".  The server then hands back a token or certificate that the browser can use to encrypt what it is sending, and decrypt what the server is sending back.  A lot of other client types can handle that too, it's not just browsers (wget, curl, etc).

But, if that goes wrong for some reason, then you'll get the error you are seeing.  You might need an additional certificate, you might have a mis-configured server, or you might have a browser that doesn't work correctly with the protocols the site is demanding you use.

Quick test - try it in another browser.  Do you get a similar SSL error?

Either way, you're going to need to talk to the admins of your Jira system to find out what is wrong and how to get into it.

Jira Stuff November 29, 2022

Hi Nic,

Thank you for your response. I know this is a certificate issue, but we do not know what exactly went wrong. This is a new server and cert has been imported accordantly. 

Jira Stuff November 29, 2022

We have found the error thankfully to this link below:
Confluence fails to start with SSL - Cannot recover key | Confluence | Atlassian Documentation

It turned out, we had different passwords :-)

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events