• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue DNS Integration for Cloudflare stop working

tanasis

Regular Pleskian
Server operating system version
AlmaLinux 8.10
Plesk version and microupdate number
Version 18.0.62 Update #1
Hello,
DNS Integration for Cloudflare stop working.

Connection to Cloudflare is OK. I have also Update credentials.

The error is:
Could not issue/renew Let`s Encrypt certificates....
image5180.jpg


The only way to renew is to pause Cloudflare, renwew it, and then unpause Cloudflare.

Any help??
 
That only shows that the domain is synced with CloudFlare. It does not indicate show if it's peroxided.

You can expanding (open) the domain details to see if records for the domain are proxied.
Screenshot 2024-07-20 201107.png
 
Yes, that indicates the domain is proxied by Cloudflare.

If issuing the certificate works without using Cloudflare the request (to access the ACME validation from Let's Encrypt) probably get blocked by Cloudflare. It is best to review your domain settings on Cloudflare. But it might also be worth to check if there aren't any IP's banned from Cloudflare by fail2ban on your server.
 
Yes, that indicates the domain is proxied by Cloudflare.

If issuing the certificate works without using Cloudflare the request (to access the ACME validation from Let's Encrypt) probably get blocked by Cloudflare. It is best to review your domain settings on Cloudflare. But it might also be worth to check if there aren't any IP's banned from Cloudflare by fail2ban on your server.

It is not only in one domain. This happened to all domains that I have in my server and there are in Cloudflare.
 
@othmaqsa, could you please confirm if the SSL certificates that are failing have the wildcard option enabled and if auto-sync is enabled in the DNS Integration for Cloudflare extension?
 
Thank you for the confirmation. When the wildcard option is enabled the SSL validation occurs through an _acme-challenge TXT record. In theory, since you have auto-sync enabled, that should happen automatically. However, there is currently a known bug (EXTPLESK-5633) which prevents the synchronization of the TXT record with the Cloudflare DNS zone. Unfortunately, I cannot provide an ETA for the resolution of the bug. Please try applying the workaround from the following article:

 
@Sebahat.hadzhi , thank you for your message.

Is there anyway to sync automatically the _acme-challenge TXT record when I'm using the SSL/TLS encryption mode Full Strict ?

1 site, I can do it manually, but now I have several sites and it's hard to do it manually, knowing that the this txt record expires after 3 months and I will not be notified.

Thank you!
 
No, unfortunately, I can't suggest an alternative for automatically updating the record on Cloudflare's end. Apart from manually updating it, what else I can suggest is switching the DNS to Plesk or using a non-wildcard certificates.
I know that people have had success following this guide in the past. However, please note that this is not an official Plesk guide, I have not tested it myself, so I cannot guarantee how well it works and that it won't lead to issues. Therefore, it should be followed at one's own risk.
 
Back
Top