• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue Lets Encrypt Wildcard succeeds manually but fails on automatic

TimReeves

Regular Pleskian
I'm seeing mails like this - every day:

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

* 'Lets Encrypt timreeves.de' [days to expire: 89]
[-] *.timreeves.de
[-] timreeves.de

Could not retrieve dns service status: DNS service is not enabled​
and
Renewal of the following Let`s Encrypt certificates has failed:

* 'Lets Encrypt syrian-heritage.org' [days to expire: 85]
[-] *.syrian-heritage.org
[-] syrian-heritage.org

Could not retrieve dns service status: DNS service is not enabled​

Those are 2 different servers, both Debian 9 and latest Obsidian (and no Bind). In both cases, the _acme_challenge DNS TXT records are present - and on a manual call the certificates are created successfully. Therefore there is no basic problem with my setup. If it works manually, it should not fail - and why is it being even tried, I still have over 80 days valid? Something needs looking at here...
 
I'm not sure the renewal was actually tried. Some other threads here lead me to believe that Plesk's Let's Encrypt Extension merely reports that the DNS is disabled locally and therefore no action will be taken for these domains.

Even more importantly, you'll get the notices but even when the day of expiry actually comes, the certificates won't be renewed automatically.

Refer to this thread for some additional information: LetsEncrypt suddenly became reliant on DNS extension.
 
Many thanks to @learning_curve - yes, that linked article describes exactly what I'm seeing. And good to read that it's a registered bug in SSL It!, so we can hope for a fix in the not too distant future. Will just delete the erroneous mails until then. Other than that, the SSL It! extension adds welcome features, bundled into one extension. It's already a favourite of mine.
 
Back
Top