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

SSL on EC2

JArnoldussen

Basic Pleskian
Parallels bills it's Plesk product as a cloud product, but they really fail to live up to this claim. For the past 4 months, we have been trying to run Plesk 10 for Windows on an EC2 instance, and there certainly have been a lot of challenges to overcome, one of which is promised to be fixed in release 10.1.1.

However, we have another major problem, and that revolves around SSL. How do you work the issue of needing an SSL certificate for multiple domains on Plesk running on EC2? If this was really a cloud-ready product, surely this would have been built in! Can anyone shed light on this?
 
hi,

We got ourselves a Positive MDC from Comodo and uploaded the cert with the customers domain names in it.
The customer seemed to be happy afterwards.

Patrick
 
Back
Top