Applicable to:
- Plesk for Linux
- Plesk for Windows
Note: This article has the reference to the issue with the fix available:
-
#EXTLETSENC-104
"When using Let’s Encrypt CLI for issuing a certificate, the alternative domain names, passed as command parameters, were not included in the cerfificate."
Fixed in:- Let’s Encrypt 3.2.0 31 August 2017
- Let’s Encrypt 2.3.0 31 August 2017
Symptoms
"www" subdomain is not secured when installing a Let's Encrypt certificate on a domain via a command-line interface.
The command below executes successfully, however www.example.com is not secured afterwards.
# plesk bin extension --exec letsencrypt cli.php -d example.com -d www.example.com --email mail@example.com
Cause
This is a Plesk bug with ID EXTLETSENC-104 , which was fixed in Let’s Encrypt 2.3.0 .
Resolution
Renew the Let's Encrypt certificate for www. example.com using the Let's Encrypt extension from the Plesk interface:
1. In Plesk, go to Domains > example.com > Let's Encrypt
2. Select the option Include a "www" subdomain for the domain and each selected alias
3. Click the Install button
Comments
1 comment
Bug #EXTLETSENC-104 have been fixed in Let’s Encrypt 3.2.0, Let’s Encrypt 2.3.0
Please sign in to leave a comment.