Same certificates on Mail and Web Servers

Help
1

Hi Guys I have a mail server (Mailserve by Cutedge) and a Webserver (Abyss Webserver) on the same MacOs server machine.
Both the software have built in a mechanism to issue Letsencrypt certificates. The webserver issues the certificates without problem, but the mailserver can not issue them as it can not use the port 80 which is reserved by the webserver.
In theory the webserver should be turned off so the mailserver can take the port 80 and issue the certificate. Practically this is almost impossible as there is no way to know how much time the certificate will take to be issued. Is there a way for the web server certificate to be used by the mailserver also?

My domain is: prismastore.cy

My web server is (include version): Abyss Webserver for Mac latest version

The operating system my web server runs on is (include version): MacOs 12+

I can login to a root shell on my machine (yes or no, or I don't know): Yes

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): Letsencrypt Enabler 3.04 for the mailserve

ACME-Bot

ACME-Bot is an internal component of Abyss Web Server. It is responsible of interacting with ACME compliant certification authorities such as Let's Encrypt which delivers free SSL/TLS certificates trusted by all modern browsers and HTTPS clients. ACME-Bot installs obtained certificates and renews those near expiry. It also handles HTTP-01 challenges to prove domain ownership: For that end, ACME-Bot may create a responder host listening on port 80 (by default) to reply to ACME certification authorities challenges in an automatic way.

2

Quite possibly - the mail service is known by the same names as the web server (or you include the mail server name in the web servers certificate). You would just need to find where the webserver keeps it's certificates and either copy them or point to them from the mail server.

Certificates from Let's Encrypt are just domain validated, so they just say the holder of the private key for this cert has proven control of the domain x.y.com (or a list of domains), but the result cert itself can be used by any service.

4 Likes