• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

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