• 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.

Recent content by Fatih G.

  1. Fatih G.

    Resolved Renew Let's Encrypt Certificate for Hostname

    OK, was just wondering because I get "Let's Encrypt certificate expiration notice" mails. But if they renew automatically, everything is fine now! Thank you very much! :cool:
  2. Fatih G.

    Resolved Renew Let's Encrypt Certificate for Hostname

    o_O ok! Thanks for this info - don't know how this happened - the subdomain was never added. While ordering the server I was asked to enter a URL/Hostname over which I can acces Plesk. I choosed server.webdevels.de and it worked out of the box without adding the subdomain in Plesk. I was also...
  3. Fatih G.

    Resolved Renew Let's Encrypt Certificate for Hostname

    Here I can only add a selfsigned certificate. Can't renew the cert from lets encrypt. Meanwhile under "Security Advisor" -> "System" it says again that Plesk is not secured with a SSL certificate, and I am able to click on "Plesk is not secured with a valid SSL/TLS certificate". But if I try it...
  4. Fatih G.

    Resolved Renew Let's Encrypt Certificate for Hostname

    Hello, I am not able to renew the Let's Encrypt SSL certificate for the Plesk Server itself (hotsname). I've installed the certificate over Security Advisor -> System -> Plesk. Now there is only this info: "Plesk is secured with a valid SSL/TLS certificate". The hostname I use is...
See more
Back
Top