• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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