• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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