Please add Mailman support to Let's Encrypt.

Ideally, one could issue either a certificate directly for lists.domain.com or a wildcard certificate for *.domain.com.

Furthermore, a secure connection should be enforceable.

Thanks!

We have a setup where webmail.example.com and example.com point to another server than our Plesk instance. Because of this we can't enable Let's Encrypt on Webmail since the CSR contains webmail.example.com and example.com.
So I hope you consider adding an option to only create webmail.example.com (without SAN example.com)

Currently the Let's Encrypt Wildcard requires that main domain would be hosted on the Plesk server, and pass the HTTP-01 challenge as well as DNS-01 for Let's Encrypt.
However for issue the Wildcard Let's encrypt require only DNS-01 challenge.
The HTTP-01 limits the causing the issue since not always the main domain is hosted on the same server as the subdomains.

This is all about security, it's simply not a fully developed product without this facility and I am hugely shocked and surprised it doesn't already exist.

Currently, when giving users the ability to access SSL to add their own certificates, they can also view Let's Encrypt and create free certificates. It would be useful to allow users access to add their own certificates without giving them access to use Let's Encrypt and there is currently no way to do this.

Additionally, any users logging in to manage their domains can see Let's Encrypt (although cannot use it) and we keep getting asked about it, so it would be useful to hide this off for users unless they specifically need access.

It will be good if Plesk can implement automatically applied wildcard let's encrypt option by default.

https://zerossl.com now offers 90 days ssl certificates that work with ACME.

It would be nice to be able to choose it as a ssl certificates provider in Plesk.

Probably not too complicated since it relies on same technologies.

Hello,

Please add functionality for uploading purchased certificates for securing domain aliases.

At the moment domain, aliases always use the certificate for the main domain. This is not suitable if different certificates are used for a domain and an alias.

Let's Encrypt certificates can be issued for aliases, but certificates uploading should also be possible.

If a domain has SNI disabled from IIS > Site > example.com > Bindings, Plesk reverts it back to Enabled when it pushes changes to IIS.

It would be nice to have an option in the domain's SSL settings to turn ON/OFF SNI and lock it.

If you have a .pfx file containing Certificate, Private Key and CA certificate, allow to upload that container with one step.

This way, a customer doesnt have to use tools like openssl to extract and convert the certificate themselves.

.pfx is the preferred format on windows plattforms ,e.g. when you export a certificate from another IIS-based server.

Issuing Let's Encrypt certificates for mail.domain.tld (to secure SMTP POP IMAP) without web-hosting enabled on the main domain. At this way, Plesk can provide only mail services.

SSL Certificate changes are currently not logged in Action Log in any way. Such changes should be logged as they are part of hosting settings.
Yet, they should reflect the certificate details (e.g. "Certificate A was changed to certificate B").

Can we get a button to manually reissue SSLs for all domains and subdomains?

I had a few issues in the past year because SSLs didn't automatically renew which made me lose hours with support tickets.

I would prefer to hit the button "Reissue SSL for domains" once every 60 days over relying that everything will just work automatically.

Currently, Plesk only provides the option to include a single domain on a Certificate Signing Request (CSR): https://support.plesk.com/hc/en-us/articles/213939845

According to our business needs, we need to issue a CSR with alternative subject names, we need to include multiple domains on this CSR so we can issue a SAN certificate, but Plesk doesn't have such functionality.

Add the option to remove certain domain names from Let's Encrypt certificates auto-renewal failure (customer's digest) and Let's Encrypt certificates auto-renewal success (customer's digest).

For example, I have domain example.com without "www" part (by design) that is secured with Let's Encrypt certificate for example.com (without "www" part). Plesk sends the notification that the www.example.com could not be secured. With the suggested option it will be possible to switch off such notification for "www" part only so that the regular notification for example.com will be active.

Currently, it is impossible to secure the webmail for the alias.
Please allow the possibility to issue Let's Encrypt SSL for the wbmail of the domain alias.

The Plesk extension uses by default http-01 challenge, which doesn't work when the website is hosted on a private IP address.

The must be an option to choose the dns-01 challenge as proffered one. This functionality is currently missing :|