• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Question let's encrypt two different vps, same domain

jviure

New Pleskian
Hi! I ve two vps, two plesks, two subscriptions (domain.com and mail.domain.com). One plesk is for the web (Wordpress), the other for mails. I ve let's encrypt in both subscriptions. In the web vps all works fine, but, in the mail plesk I've to move the ssl cert every three months -created with the hosting plesk - to the mail subscription cause the acme challenge cannot be resolved. Some idea how can avoid that? is very tired being pending of the expiration date of the certificate. Thanks!
 
(every two months actually, because letsencrypt renews when there's one month left)
Does one of the plesks provide DNS, or is that configured on the provider's server?
Does the mail plesk also have webmail.domain.com?

I have a similar problem, but in the other direction. www. is on another server because the plesk server became too slow for magento. So www mounts /var/www/vhosts/default/htdocs/.well-known/acme-challenge from the main server by sshfs. Someday I'll get around to writing a script to fetch the new key and reload nginx ... caveat: automating this means one of the servers must have privileged access credentials for the other server.
 
Back
Top