SSL cipher problems with browsers


we have a Confluence server running on Windows Server 2012 R2 with Tomcat.

We want to secure our server with https. Because the port 443 is already used on our IP and firewall, we decided to use port 8091. HTTP is on port 8090 and works just fine btw.

For that we added a SSL wildcard certificate to a custom keystore.
Then we add a HTTPS connector to server.xml.
After that we changed the base url to

But then we have problems accessing confluence via HTTPS. We get the following error message in several browsers:  ERR_SSL_VERSION_OR_CIPHER_MISMATCH


We have found some KB and forum threads online and update some cipher parameters to the configuration. see:


here an example of our connector section:


<Connector port="8091" maxhttpheadersize="8192" enablelookups="false" disableuploadtimeout="true" acceptCount="100" scheme="https" secure="true" clientAuth="false" SSLEnabled="true" sslProtocols="TLSv1,TLSv1.1,TLSv1.2" ciphers="TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_RSA_WITH_RC4_128_SHA, TLS_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA256, TLS_RSA_WITH_AES_256_CBC_SHA,SSL_RSA_WITH_RC4_128_SHA" keystoreFile="ourKeystoreFile" keystorePass="******"/>;


How can we get our Confluence server running with the SSL/TLS ciphers that are compatible with browsers like Chrome, Firefox and so on?

3 answers

1 vote

I don't know if this would solve the error, but in general when using HTTPS it would benefit you in terns of performance to put a proxy in front of Confluence. On WinServer you could use IIS and let that web server handle the SSL handshake.

I agree with Josh here. I do not understand why so many people struggle with tomcat and SSL when its just to put a proxy in front. 

If it helps: (This gives compatibility, and A+ rating)

SSLProtocol all -SSLv2 -SSLv3


0 votes

FYI, by default Confluence 6+ uses port 8091 for Synchrony. So you may want to consider a different port.

0 votes


I had this exact same problem. Turned out it was because I was trying to use a PKCS12 (.pfx) format keystore instead of the proprietary JKS format. The admin interface accepted my PKCS12 keystore but apparently the rest did not.

Follow this post on Stack Overflow to convert your keystore to JKS and try again. It should work fine.

I'm also posting this here because I had one heck of a time figuring this out on my own, so for you time travelers out there, this is for you. ;)



Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Feb 06, 2019 in Confluence

Try out the new editing experience

Hi team, I’m Avinoam, a product manager on Confluence Cloud, and today I’m really excited to let the Community know that all customers can now try out the new editing experience and see some of the ...

895 views 45 7
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you