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

  1. K

    Resolved Plesk Obsidian – Let’s Encrypt certificate does not include domain aliases in SAN

    I was just about to explain that I’ve already resolved it. And it was exactly what you mentioned: the alias domains didn’t have the web service enabled, so HTTPS wasn’t being activated.
  2. K

    Resolved Plesk Obsidian – Let’s Encrypt certificate does not include domain aliases in SAN

    I was keeping the option of removing and reinstalling as a last resort, since I have hundreds of domains on that machine and the thought of having to reconfigure all of them is quite discouraging. And I’m not sure it will work. there are no Lets Encrypt logs in panel.log place
  3. K

    Resolved Plesk Obsidian – Let’s Encrypt certificate does not include domain aliases in SAN

    Sure, they don’t appear. On other Plesk servers I have, they do show up, but not on this one :S
  4. K

    Resolved Plesk Obsidian – Let’s Encrypt certificate does not include domain aliases in SAN

    Hello, I’m experiencing an issue in Plesk Obsidian Web Host Edition 18.0.74 Update #3 where domain aliases are not being included in the Let’s Encrypt certificate for the main domain. Setup: One main domain with hosting and valid Let’s Encrypt certificate. Several domains configured as...
See more
Back
Top