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

Comodo certificate problem on Windows Server 2003

G

gtsiag

Guest
I did the following while installing the certificate in question.

1) Logged in Plesk Admin Panel, and from there went to Server->Certificates. Added a new certificate and certificate CA, using the relative private key.
2) Assigned the certificate to the exclusive IP address i want to, via Server->IP addresses.

However, when i access the domain in question, a warning pop up indicates that the certicate is not valid. The certificate that the browser receives is not the one that i've set up in Plesk but the Default certificate(as indicated in Server->Certificates), although the domain's IP is not set to this. Also, this does not seem to be a problem whenever i'm using Firefox browser, the error only occurs in Internet Explorer.

Any clues?
 
Back
Top