Articles in this section

See more

Let's Encrypt auto renew is not working for domains or Plesk with renamed certificates

Avatar
Dinara Tsydenova (Aspembitova)
Updated
kb: bug Plesk for Linux ext: le ABT: Group A

If you reuse this article in some tickets, ask customers why it is important to them to rename LE certificates. Post their answers to https://jira.plesk.ru/browse/EXTLETSENC-483  as comments

Applicable to:

  • Plesk for Linux

Symptoms

  • Let's Encrypt auto-renew task is not working for Plesk or a domain.

  • Plesk log /var/log/plesk/panel.log contains following entries with debug being enabled:

    CONFIG_TEXT: INFO [extension/letsencrypt] Check if Panel or Mail Server is secured by Let's Encrypt certificate...
    INFO [extension/letsencrypt] Panel or Mail Server is not secured by the Let's Encrypt certificate.

Cause

Let's Encrypt extension bug #EXTLETSENC-483 (Cannot auto-renew certificates in Plesk if they were renamed previously) which is planned to be fixed in future product updates.

Let's Encrypt auto-renew feature relies on certificate names and does not recognize certificate names other than Lets Encrypt example.com on domain level and Lets Encrypt certificate on server level..

Resolution

Until a fix became available, as a workaround, renew the certificate manually:

Securing Plesk
  1. Log in to Plesk.
  2. Renew the certificate manually in Tools & Settings > SSL/TLS Certificates > + Let's Encrypt:

    22.PNG

 

Securing particular domain
  1. Log in to Plesk.
  2. Renew this certificate manually from Domains > example.com > SSL/TLS Certificates > Get it free.
    23.PNG

Comments

0 comments

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles