Let's Encrypt fails to issue a certificate with the following error: The example.com DNS zone contains an AAAA record, but the domain is not assigned an IPv6 address in Plesk.
Plesk repair utility shows the error for wildcard domain: File not found: _.example.com.conf
Cannot add WordPress plugin to set using command-line interface
Unable to change the WordPress password for dashboard via Plesk after migration
Extension Catalog does not report name of the extension whenever the installation fails
Unable to Add your site copy to Facebook in Web Presence Builder: This page isn't available
Microsoft Azure DNS extension loads slowly
Unable to update Atomic Basic ModSecurity rule set via Plesk daily task
Subscription unable to sync with service plan: Joomla! Toolkit - Months to keep Audit Logs
An error is displayed in Plesk UI after daily task: DNS Service is not installed on this instance

See more

Unable to install the Let's Encrypt certificate on a subdomain of an alias

Updated June 20, 2019 15:08

Applicable to:

Plesk Onyx

Symptoms

Unable to create the certificate for the subdomain alias dev.alias.com at Domains > dev.example.com > Let's Encrypt.
The domain alias.com is an alias for example.com
Accessing to dev.alias.com returns invalid Common name.

CONFIG_TEXT: NET::ERR_CERT_COMMON_NAME_INVALID

Cause

It is caused by a bug in the product with the ID #EXTLETSENC-696 which will be fixed in future Plesk updates.

Resolution

As a workaround, it's possible to create the subdomain dev.example.com as an independent domain and then create the alias dev.alias.com.

Comments

0 comments

Please sign in to leave a comment.

Have more questions? Submit a request