• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Let's Encrypt specifying multiple (sub)domains via CLI

bobtib

New Pleskian
When I try to use the letsencrypt extension via the CLI, I am unable to get it to generate the correct SAN entry in the certificate for both domain.com and www.domain.com.

The CLI documentation suggests :

plesk bin extension --exec letsencrypt cli.php -d domain.com -d www.domain.com

but this seems to generate a cert that has a SAN value of just DNS Name=domain.com

Using the Let's Encrypt extension from the plesk GUI and selecting the option 'include a "www" subdomain for the domain and each selected alias' seems to work fine, and correctly generates a cert with a SAN value of DNS Name=domain.com,DNS Name=www.domain.com

It looks like someone has already discovered/reported this problem in GitHub : SAN support

On a separate note the above quote from the CLI Documentation is incorrect in its present form as it fails to indicate that the --email:-m <string> option is required, otherwise an error is returned.
 
Back
Top