• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

letsencrypt

  1. M

    Question Certificate renewal warning / notification although no certificate assigned/created

    Hello Plesk Team and Community, we are currently facing an issue where one of our customers receives a daily notification email stating that their Let's Encrypt certificate cannot be renewed. The domain in question is no longer pointing to our server. However, it is still configured in Plesk...
  2. kristobal1969

    Resolved Error messages with let's Encrypt when 1 serveur for main domain and another serveur for subdomain or mails

    Hello, I receive each day a message from Plesk telling that the domain is not secured though it is (on all domain and subdomains). in this exaple ngpark.fr and www.ngpark.fr are on the server with ip 217.160.0.52. They have their own certificate on that server (i do not manage this server). but...
  3. A

    Resolved SSL It! does not renew certificate for subdomains that are used as redirections.

    Hi there, I noticed today, that SSL It! does not renew certificates for redirection subdomains. As there is no SSL/TLS Certificate button in the dashboard for these kind of "domains" I can not reissue manually. I know there is the possibility to configure the subdomain as standard hosting...
  4. M

    Question Let's encrypt certificate emails do not contain certificate details

    So for every site on our shared Plesk server we get emails from Let's Encrypt stating: The following domains of account_name (login username) have been secured with Let`s Encrypt certificates: <none>...
Back
Top