• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Plesk 8.1.1: default cert appears after being changed.

R

ricebus

Guest
Hello,
I've installed Plesk 8.1.1 on my FreeBSD 6.2 box (from ports).

I've used SWsoft's guide of installing SSL certs on specific domains.
I've generated a private key, sent the csr to verisign and got it signed.

After receiving the signed certificate from VeriSign I've copied it to Plesk and pasted the intermediate cert found here:
http://www.verisign.com/support/verisign-intermediate-ca/secure-site-pro-intermediate/index.html

but after doing it plesk printed the following message: "Warning: The CA certificate does not sign the certificate."

I kindely ignored the message as I could not find any solution to this and approached right to the next step and installed the certificate by entering the Setup link and selected my cert as the default for the domain. at this point everything looked fine and Plesk showed no errors.

I entered my site and checked the cert and it looks like plesk's default certificate is still active there. I tried restarting my box but it didnt help.
I checked the conf/ dir and all the certificates specified in httpd.include are the correct ones.

Any ideas?

Thanks in advance,
George
 
Problem fixed,

I had to allocate the domain it's own IP and then allocate the certificate to the IP.

Hope this will help someone with the same problem I had.
 
Back
Top