- Not using the correct keysize (1024 / 2048 bits) - as you have done, you may need to remove your surge_priv.pem file if you are moving from 1024 to 2048 bits.

- Not pasting in the correct cert / intermediate cert.

- Surgemail not having to be restarted if you e3dited the pem files manually.

So if you are still not getting anywhere, drop me (offlist!!) your surge_priv.pem and surge_cert.pem (and preferably the files GoDaddy supplied you), and the url you are trying to connect on and I'll run some tests to see what I can repeat. Ah while you are at it please include your surgemail.ini.

Thanks

Marijn


On Sunday 06/02/2011 at 1:15 pm, surgemailHIDDEN@etwinsite.com wrote:

Hi,

We just purchased a basic SSL certificate from Godaddy and every time we add the certificate, everything that uses SSL becomes unusable. Internet Explorer 8 (PC) says "Internet Explorer cannot display the webpage - What you can try: diagnose connection problems". Flock (Mac) says:

    An error occurred during a connection to 204.238.32.70:7443.

    Cannot communicate securely with peer: no common encryption algorithm(s).

    (Error code: ssl_error_no_cypher_overlap)

    The page you are trying to view can not be shown because the authenticity of the received
    data could not be verified.

    * Please contact the web site owners to inform them of this problem.

The process we followed was:

1) On the SSL Certificate page of the admin site for surgemail, clicked on get new CSR, entered appropriate information. When this was done, clicked on SAVE CHANGES. We got an error saying that it wasn't created because ssl/surge_priv.pem existed and needed to be deleted. (of course this causes a problem with the certificate and requires us to add an exception for the certificate).

2) Deleted /usr/local/surgemail/ssl/surge_priv.pem

3) repeated the operation to get a CSR several times. This had to be done on numerous times because despite requesting a 2048 bit key every time, the first four or five attempts yielded only a 1024 bit key.

4) obtained a new certificate from Godaddy.

5) pasted new certificate followed by Godaddy�s intermediate certificate under SSL certificate(s). We also commented each certificate as shown here: http://netwinsite.com/surgemail/help/secure.htm.

As soon �Save Changes� is clicked then nothing works. The only way to get any SSL connection into the server / email is to delete surge_csr.pem, surge_cert.pem and surge_priv.pem and reboot the machine. We believe we followed the correct procedure. Did we? It seems that either we did something wrong or there�s a problem with surgemail.

Anything you could do to help would be very much appreciated.

Thank you..