• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Question Plesk: LetsEncrypt renewals sporadically failing/skipped

Paul Larson

Basic Pleskian
Server operating system version
Ubuntu 22.04.5 LTS
Plesk version and microupdate number
Plesk Obsidian 18.0.71.1
I don't have specifics, but I do seem to have domains fail, causing an alert, because their SSLs are expired. All are on Plesk servers. My issue is identical to this 2024 thread:


Just wanted to see if anyone else experiencing this.

Picking today's domain, for example, I don't see any email alert of an issue. I'm accustomed to emails like this:

Subject: Could not issue/renew Let`s Encrypt certificates for ...
Body:
Code:
Invalid response from https://acme-v02.api.letsencrypt.org/acme/[redacted]
Details:
Type: urn:ietf:params:acme:error:unauthorized
Status: 403
Detail: 67.205.170.6: Invalid response from https://example.com/.well-known/acme-challenge/[redacted]: 404

** 'Lets Encrypt example.com' [already expired] **
[-] example.com
[-] www.example.com

I'll be honest - I don't always pay attention to these emails because I get so many of them, and sometimes the failures are 'correct', and no site is down.

But, the domain that failed today has no accompanying email alert.
 
Hello, @Paul Larson . Couple of questions:

  1. Is the DNS of the domain name(s) managed locally?
  2. Are those wildcard certificates?
  3. What's the option selected in in Plesk > Service Plans > SERVICE_PLAN_NAME > Additional Services tab > SSL It!?
  4. Can you please check /var/log/plesk/panel.log and confirm if there are any relevant errors logged?
 
Back
Top