Hi, with the keys from either source you will need to do the same thing.
The CSR is irrelevant, you don't need it. (It's the request you send to
The Private key is essential, you need it and for surgemail copy it to
(if you created the CSR within surgemail, then you already have the
surge_priv.pem and don't need to touch it)
The public key is essential, and it goes into surgemail/ssl/surge_cert.pem
The certificate authority bundle is also required, it is APPENDED to
On 14/05/2016 9:21 a.m., surgemailHIDDEN@etwinsite.com wrote:
> Support ChrisP <surgemailHIDDEN@email@example.com> wrote:
> Thanks for the help.
> I ended up buying a comodo SSL for my domain for 50$ / yr
> they provided me 3 keys
> Certificate Authority bundle:
> I was still confused as to where to place these keys since the terminology did not match surgemail
> Certificate Signing Request (CSR)
> SSL certificate(s)
> so I started to play with letsencrypt again. and I managed to get it to work and create keys, the keys have a short lifespan and do not populate into the surgemail path in which I need it to, would I require an automated script for this? Do i need to rename the keys to match what surgemail ssl directory had Also would this also mean the comodo SSL i purchased was not necessary? I may try to get a refund if so.
> I'm still unsure how to set this up, it looks like I'm on the right path but would still require some direction
Last Message | Next Message
Site Map |
Contact Netwin |
POP3 Mail Server |
Linux Webmail |
UnInstall instructions for all products
Copyright © 2017 Netwin Ltd. All rights reserved.