I got a CA cert by submitting my CSR from GoDaddy, after applying a certificate to my Tomcat web server. When I access my website using Chrome or Mozilla I face the error:


I invoked the following command for the CSR generation process:

 keytool -genkey -alias mydomain -keyalg RSA -keystore mydomain.jks -keysize 2048 -sigalg SHA256withRSA
 keytool -certreq -alias mydomain -sigalg SHA256withRSA -keystore mydomain.jks -file mydomain.csr

How can I solve this?


2 Answers 2


That warning is caused by the size of the group used for ephemeral Diffie Hellman key exchange being too small. So small that the symmetric keys can be extracted by academics.

The certificate does not affect the size of the group used for DHE. The configuration of the web server does.

Currently the recommendation is that the group size in bits should be as large as the RSA key for the certificate, usually 2048 bits, and in any case no smaller than 1024 bits. Also, you must generate your own group, not use a predefined one, or else 1024 bits is not enough.

Make sure your server does not support intentionally weak "export" crypto - that means 512 bits.

Use Qualys tool to check the server configuration.

Java docs.

  • Java/JSSE doesn't support generating your own parameters, although JDK8 does allow you to control the size chosen from a hardcoded set, as per your link. Dec 6, 2015 at 1:07

The simplest fix is to upgrade your Java version to Java 8 as Java 7 has reached its EOL (end of life) in April 2015.
Also if it does not work and you have JDK 1.8, setting the system property -Djdk.tls.ephemeralDHKeySize=2048 is recommended to ensure stronger keysize in the handshake. Refer to the Java 8 docs

Edit Here is a list of the strong ciphers you may need in your Tomcat server.xml inside your HTTPS connectors:


Edit 2

Do check your JAVA_HOME path variable, it may be pointing to an older version of java i.e. less than jdk 1.7

I was facing the same problem as my JAVA_HOME was pointing to jdk1.6 so correcting the JAVA_HOME fixed this

  • This (all) assumes Tomcat using JSSE (HttpProtocol or HttpNioProtocol) not APR. That cipher list does not include any DHE keyexchange, so it doesn't matter whether good DHE parameters are forced or even available, and thus works on JDK7 as well, assuming the client(s) accept at least one of ECDHE_RSA (with an implemented curve) or plainRSA, which most browsers should and current Chrome and Firefox definitely do. Dec 6, 2015 at 1:03

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .