• 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

Question Lets Encrypt and Plesk Onyx Errors with Cloudflare DNS

daedparrotsoftware

New Pleskian
We have an OVH dedicated server using Cloudflare as our DNS (NOT Plesk)
Running CentOS Linux 7.7.1908 (Core)‬, Plesk Obsidian 18.0.20 Update #2 ,
last updated at Nov 8, 2019 04:17 PM

All sites are running WordPress, latest php, etc.

All our domains are on dedicated IPs running full SSL between the sites and Cloudflare.
The sites, Https, WordPress, etc. are running fine. An SSL of DeadEasyApps.com test via QualysLabs
returns NO errors - rates our SSL as an "A"

HOWEVER, ever hour, Plesk sends us an ERROR report about the certificates that says:

Could not renew Let`s Encrypt certificates for Admin (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 DeadEasyApps.com' [days to expire: 58]
[-] *.deadeasyapps.com
[-] deadeasyapps.com

Skip wildcard certificate renewal for the domain 'deadeasyapps.com'. TXT record

could not be created automatically.

Can not imagine why?? The Lets Encrypt Extension says:
Domain deadeasyapps.com secured
Domain with the "www" prefix www.deadeasyapps.com secured
Wildcard SSL/TLS certificate *.deadeasyapps.com secured


etc.
Also the _acme-challenge TXT record is there in the Cloudflare DNS.

Every hour,getting this renewal and "TXT record can not be created" is being generated. Any ideas? :)

Joe C.
 
Thanks for the link. :)

The DNS part does not apply to our situation - we get no DNS error in the email from Plesk.

However, we DO see the
"Skip wildcard certificate renewal for the domain '*example*'. TXT record could not be created
automatically
." part, and our error DOES seem to be trying to renew a cert that doesn't need
it yet.

I guess I should have posted this as an issue, if our error is also a related bug. Can't be sure. :)

Sid
 
Back
Top