Resolved Could not issue/renew Let's Encrypt certificates for <customer>

[Epic Voyage]

Server operating system version

CentOS 7 (Core)

Plesk version and microupdate number

18.0.60 Update #1

Hi,

I have an older server which has been upgraded to Plesk Obsidian. I am receiving SSL renewal failure emails, like the one attached, which refer to a customer in the subject line, but which have an empty body. There are no domains or subdomains listed.

Is there a way to determine which domain is causing the problem (and maybe fix the email template?) without clicking through each subdomain on the server?

 

[Kaspar@Plesk]

You'll probably find some info about the failed certificate(s) renewal in the panel log. Look at Tools & Settings > Log browser > Plesk.

As for the empty body in the notification you can check in Tools & Settings > Notifications if the "SSL It! certificates auto-renewal failure" notification has a body by clicking the edit icon.


The default body is:

Could not secure domains of <client_contact_name> (login <client_login>) with <vendor> certificates. Please log in to Plesk and secure the domains listed below manually.
Securing of the following domains has failed:


<failedKeepDomainsSecured>


The following domains have been secured without some of their Subject Alternative Names:


<keepDomainsSecuredWithErrors>


Could not renew <vendor> certificates for <client_contact_name> (login <client_login>). Please log in to Plesk and renew the certificates listed below manually.
Renewal of the following <vendor> certificates has failed:


<notRenewedCertificates>


The following <vendor> certificates have been renewed without some of their Subject Alternative Names:


<partiallyRenewedCertificates>




Legend:
[+] This domain is secure. The domain's SSL/TLS certificate from <vendor> has been issued/renewed.
[-] This domain is not secure. Either the domain's SSL/TLS certificate from <vendor> could not be issued/renewed or the domain name was excluded from the certificate. Renew the certificate manually or request a new one to secure this domain.

 

[Epic Voyage]

Those logs are extremely helpful!

And the SSLIt! template was empty. I will mark this as resolved after confirming my next warning email.

Thank you for the thorough solution!

 

[Epic Voyage]

I thought I used to be able to edit posts to marked them as [Resolved], but do not see that option now. Both aspects of your solution are working great. Thanks again!

 

[Kaspar@Plesk]

That good to read, thank you for letting us know. I've marked to thread as resolved for you.