• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • 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.

Question Plesk with Cloudflare Proxy DNS Records and Letsencrypt..

cpulove

New Pleskian
Server operating system version
Debian 12
Plesk version and microupdate number
Plesk Obsidian 18.0.64 Update 1
Hey, maybe there is some help out there with my Cloudflare DNS/SSL Setup.

I have some issues with Letsencrypt Certs while using a domain with Cloudflare and its proxy function, looking for a way, to solve this issue:

I've setup a NS with "_acme-challenge" and "domain name" to autorenew the Letsencrypt certificates with the Cloudflare DNS Extension in Plesk, which works fine.

But as soon as I enable a proxy for an A, AAAA or CNAME record, I get the "ERR_SSL_VERSION_OR_CIPHER_MISMATCH" error.

I know that the Cloudflare Client Certificate is able to protect all the web traffic with SSL, but unfortunately not e-mail traffic.

So my question:
Is it possible, to use the origin Cloudlfare certificate for the main domain web traffic and webmail and use proxy there, but keep the Letsencrypt certificate for all the e-mail traffic of the domain and do not proxy this email subdomain? Will Letsencrypt keep working/renewing itself only for the mail.xxx.xx subdomain and use the origin Cloudflare cert for all the rest?

If so, how is the way to setup this the right way in Plesk, both certs, Cloudlfare and Letsencrypt side by side?

I need to solve this problem, as I run some Nextcloud subdomains with IPv6 DNS only, and I do need the Cloudflare proxy option, to get a valid IPv4 for these Subdomains, as Nextcloud internal updates and App downloads are only working with an IPv4 so far. And of course I do not want to manually renew the certificates, every 3 month!

Help would be nice.
 
Back
Top