(resend to check list)
If you don't have lets involved, and you don't have g_ssl_per_domain
enabled, then the folder you want is:
/usr/local/surgemail/ssl
And the file to put it in is:
surge_cert.pem (Certificate, followed by keychain)
and
surge_priv.pem (Your secret key)
After updating those files, restart surgemail. Check mail.err to see if
it reports any errors loading them. If the format is wrong/corrupt it
will fail, then restore the old files and restart surgemail.
(we recommend letsencrypt though as it's much easier, for 'most'
situations but does have some requirements) see
https://surgemail.com/knowledge-base/enable-ssl/
ChrisP
On 10/03/2021 12:15 pm, Lyle Giese wrote:
> I am using a third party ssl cert and it will expire on March 19th. I
> started the process to replace it today. I am unable to figure out
> how to upload the certificate and chain file. When using the
> webadmin, it accepts the upload, but I can not find where it put it on
> the server. It certainly did not put it at /usr/local/surgemail/ssl.
>
> I looked up the instructions for manual installation of certificates
> and that doesn't work. No matter what combination of commands and
> incantations, Surgemail reverts to the old cert that expires on March
> 19th. I am unable to figure where it's finding that certificate and
> pulling it in. the lets subdirectory is empty(I am not using LETS as
> I don't have the webmail on port 80 or 443). I can not find any
> pointers in surgemail.ini that would point to anything other than
> /usr/local/surgemail/ssl
>
> Lyle Giese
>
>
>
|