Let’s Encrypt certificate cannot be installed with the following error:
PLESK_ERROR: Invalid response from https://acme-v01.api.letsencrypt.org/acme/authz/DEADBEEFMwVU3eZxfBU9-PRUcd51tflRLJD7CoBTxrQ.
Detail: DNS problem: SERVFAIL looking up A for example.com
PLESK_ERROR: Error: Could not issue a Let’s Encrypt SSL/TLS certificate for example.com. Authorization for the domain failed.
Invalid response from https://acme-v01.api.letsencrypt.org/acme/authz/0VWhDoTjEzzwPXNzPHd-zO73YAdXa8qgyac7eEiPQqY.
Detail: unknownHost :: No valid IP addresses found for example.com
PLESK_ERROR: DNS problem: NXDOMAIN looking up A for example.com
– check that a DNS record exists for this domain
A website example.com may be created recently and may be accessible from the web;
Domain name cannot be resolved against some of global DNS resolvers:
# dig example.com @220.127.116.11 +short
A record does not exist or DNS propagation is not completed.
Add A record for a domain.
If it is not clear what NS servers are managing DNS for the domain:
- Go to the online NS record checker (for instance this one: Online tool for NS server check);
- Check if the NS servers are the same with the Domains > exmple.com > DNS Settings. If they are, then your DNS is managed by Plesk.
If there are not matching or the option Domains > example.com > DNS Settings is absent, thus, 3-d party DNS server is used (i.e. DNS provider).
If DNS is managed in Plesk:
Add record (type A) for the example.com in Plesk > Domains > example.com > DNS Settings > Add Record:
If DNS is managed by a 3d-party DNS provider:
Contact the domain provider in order to add appropriate A record
Note: If record has been already added, but the error persist, it is required to wait for a while. DNS propagation may take up to 72 hours. Use this tool in order to check global DNS propagation: DNS Propagation Check.