• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Forwarded to devs [Let's Encrypt] Could not issue/renew Let`s Encrypt certificates for <admin name>

Azurel

Silver Pleskian
User name: Azurel

TITLE

[Let's Encrypt] Could not issue/renew Let`s Encrypt certificates for <admin name>

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk Obsidian, Version 18.0.27 Update #1, CentOS Linux 7.8.2003 (Core), 64Bit

PROBLEM DESCRIPTION

I got today two e-mails.

Date: Sat, 06 Jun 2020 09:16:05 +0200
The following Let`s Encrypt certificates for Admin Name (login admin) have been renewed:
* 'Lets Encrypt sudomain.example.com'
- sudomain.example.com

1 second later
Date: Sat, 06 Jun 2020 09:16:06 +0200
Could not renew Let`s Encrypt certificates for Admin Namel (login admin). Please log in to Plesk and renew the certificates listed below manually.

Renewal of the following Let`s Encrypt certificates has failed:

* 'Lets Encrypt sudomain.example.com' [days to expire: 29]
[-] sudomain.example.com

idn_to_ascii: empty domain name: U_ILLEGAL_ARGUMENT_ERROR

The following Let`s Encrypt certificates have been renewed without some of their Subject Alternative Names:

<none>

Legend:
[+] This domain is secure. The domain's Let`s Encrypt SSL/TLS certificate has been renewed.
[-] This domain is not secure. Either the domain's Let`s Encrypt SSL/TLS certificate could not be renewed or the domain name was excluded from the certificate. You need to either renew the certificate manually or to request a new one to secure this domain.

Take a look in browser certificate says:
valid from: ‎Friday, ‎5. ‎June ‎2020 13:16:19
valid to: ‎Thursday, ‎3. ‎September ‎2020 13:16:19

STEPS TO REPRODUCE

no steps

ACTUAL RESULT

see description

EXPECTED RESULT

No mail with "Could not issue/renew Let`s Encrypt certificates for <admin name>"

ANY ADDITIONAL INFORMATION



YOUR EXPECTATIONS FROM PLESK SERVICE TEAM


Confirm bug
 
From developer:


Some more information is needed:
  1. Is SslIt extension installed or just LE?
  2. Is the certificate (sudomain.example.com) assigned to any other domain?
  3. Does the domain "sudomain.example.com" have hosting?
  4. Is it possible to provide logs?
 
1. SSL It! Version 1.4.1-747 is installed (Let's Encrypt is Version 2.10.0-621)
2. In this case its my "Hostname" showed in plesk "System Overview".
3. Its have a hosting with "Document root" and a single html-file in it.
4. (proxy_)error_log have no entries for this time.


let's encrypt mail history is for this subdomain:

Date: Tue, 07 Apr 2020 09:36:02 +0200
Yes two times in one mail same subdomain.
The following Let's Encrypt certificates for XXX (login admin) have been renewed:

* 'Lets Encrypt subdomain.example.com'
- subdomain.example.com

* 'Lets Encrypt subdomain.example.com'
- subdomain.example.com

identical e-mail for
Date: Fri, 07 Feb 2020 08:36:03 +0100


This subscription have only two domains: example.com and subdomain.example.com
SSL/TLS Certificate for example.com
Secured Components => Secured for "Domain" example.com and www.example.com
Subdomains => Secured for subdomain.example.com

SSL/TLS Certificate for subdomain.example.com
Secured Components => Secured for "Domain" subdomain.example.com
 
Last edited:
Back
Top