• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

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