#Zimbra desktop java error how to#
#Zimbra desktop java error software#

#Zimbra desktop java error software#

certificate sign CAyourDomain-template ca-crl-host='' name=CAyourDomainĬreate Certificate: /certificate add name=webfig-template common-name='webfig' country=GB days-valid=3650 key-size=4096 locality='Your City' organization='Your Organization' state=Hertfordshire trusted=yes unit='Technical Services' subject-alt-name='IP: Collaboration Server is open-source collaborative software that comprises a mail server and a web client. CA ' key-size': Note that using ' 4096' can max CPU and hang thinly provisioned models when signingĬreate CA: /certificate add name=CAyourDomain-template common-name=CAyourDomain country=GB days-valid=3650 key-size=4096 locality='Your City' organization='Your Organization' state=Hertfordshire trusted=yes unit='Technical Services' subject-alt-name='IP:' key-usage=digital-signature,key-cert-sign,crl-sign.' ca-crl-host': again, specify PUBLIC IP of router.' subject-alt-name': specify PUBLIC IP of router.' state': specify a county for those residing outside the USA.' CAyourDomain': replace 'yourDomain with your organization's domain.WARNING:ĭo not just cut-n-paste: Please replace my placeholders with sensible values -) The following is a MikroTik-specific procedure to clear the error. ' Error code: SSL_ERROR_NO_CYPHER_OVERLAP'ĭon't go down the rabbit hole investigating incompatible cyphers or the like: you just need to sign your certificate with a CA and things will work as expected. When the browser sees an unsigned cert, it will puke the error: When configuring a MikroTik for Webfig https access, you'll get this error if you just create and use a cert that has not been signed by a CA. The error message is a bit of a red-herring.

#Zimbra desktop java error how to#

I found some solutions on how to convert the pkcs file to x.509 but then I got other errors, so I'm totally stuck now. Keytool error: : Input not an X.509 certificate I've got the customer to send me the certificate chain and when I try to import that I get this error: keytool -import -trustcacerts -alias tomcat -file. Keytool error: java.io.IOException: toDerInputStream rejects tag type 45 Or this: keytool -importkeystore -srckeystore -srcstoretype pkcs12 -destkeystore. If I try to import the key to a keystore I get either this: cat | openssl pkcs12 -export -out.

I seem to be getting errors everywhere I turn. Is this an error I've made in producing the CSR or could it be an error the client has made with generating the cert? My understanding is that the cert does not control what ciphers or protocols should be used so I don't understand why this has happened.

Please contact the web site owners to inform them of this problem. The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. CannotĬommunicate securely with peer: no common encryption algorithm(s). Now, when I try to connect I get the following error (this is from Firefox, but all browsers produce a similar error):Īn error occurred during a connection to 172.31.1.36:8443. I added the certificate to a new keystore and amended the path in the server.xml file appropriately. However, the pen test also flagged that we should ideally not be using a self-signed cert so, by following these guides, I created a CSR and got the customer to create a certificate signed to their internal domain (the server could be accessed by a couple of different URLs hence the need to create a CSR with a SAN). This satisfied the pen test and the application continued to work in all three main browsers (Chrome, Firefox and IE). This worked subject to the expected browser error when using a self-signed cert.Īfter a pen-test they decided we need to disable some deprecated ssl protocols and and ciphers, so I amended the ssl connector in my tomcat server.xml to look like this: At the request of the customer I enabled this to use https by creating a self-signed certificate. My company has supplied a Tomcat/MySQL based application to a customer that by default uses http.