• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

SSL certificate not updating via Plesk GUI

DennisAm

Basic Pleskian
I have a few SSL certificates that have almost been expired. Therefore, I renewed them and received new cerfiticate files.
However, when I try to update them in Plesk, some of them aren't updated. These are the steps I take:
  1. Go to the subscription that the certificate is for
  2. Go to "SSL Certificates"
  3. Click on the existing certificate, so that the screen "Change Properties of SSL Certificate" opens.
  4. Upload the new .crt file.
  5. Plesk returns "The SSL certificate was successfully updated.":
    pleskssl.png
Then, when I open the IIS Manager in the Windows Server GUI, I still get the old certificate:

pleskssl1.png

Instead of

pleskssl2.png

The only way I can get it to work is to:
  1. Go to SSL Certificates.
  2. Create a new certificate, upload the old private key and new .crt file.
  3. Assign the certificate to the domain.
  4. Now, the new certificate is assigned correctly and served by IIS.
Again, this is only the case for some of my domains (about 50%). For the other domains, I can simply update the SSL certificate by requesting a new one and uploading it to the server (following the steps mentioned above).

I checked Plesk logs (after having turned on Debug mode), but there's no errors in there:
Code:
[2015-12-06 15:54:34] DEBUG [util_exec] [d91e099b8a073bdc87978612faa7edaf][0] Starting: openssl x509 -text -noout
[2015-12-06 15:54:34] DEBUG [util_exec] [d91e099b8a073bdc87978612faa7edaf][0] Finished in 0.02644s, Error code: 0
[2015-12-06 15:54:34] DEBUG [util_exec] [56644c2ac2713] Starting: filemng root cp2tempnam "C:/Program Files (x86)/Parallels/Plesk/PrivateTemp/cer9AA0.tmp" "D:\Program Files (x86)\Parallels\Plesk\/var/certificates" cert
[2015-12-06 15:54:34] DEBUG [util_exec] [56644c2ac2713] Finished in 0.03193s, Result: TRUE
[2015-12-06 15:54:34] DEBUG [util_exec] [56644c2aca749] Starting: ch_mode 400 "D:\Program Files (x86)\Parallels\Plesk\var\certificates\{cert-431b39aa-9c29-11e5-80e2-6c626d653773}"
[2015-12-06 15:54:34] DEBUG [util_exec] [56644c2aca749] Finished in 0.01776s, Result: TRUE
[2015-12-06 15:54:34] DEBUG [util_exec] [56644c2acef34] Starting: ch_owner 0:0 "D:\Program Files (x86)\Parallels\Plesk\var\certificates\{cert-431b39aa-9c29-11e5-80e2-6c626d653773}"
[2015-12-06 15:54:34] DEBUG [util_exec] [56644c2acef34] Finished in 0.02302s, Result: TRUE
[2015-12-06 15:54:34] DEBUG [util_exec] [56644c2ad4be8] Starting: remove_files "D:\Program Files (x86)\Parallels\Plesk\/var/certificates/{cert-c6e55854-9c27-11e5-80e2-6c626d653773}"
[2015-12-06 15:54:34] DEBUG [util_exec] [56644c2ad4be8] Finished in 0.02477s, Result: TRUE
[2015-12-06 15:54:34] INFO [panel] The SSL certificate was successfully updated.
[2015-12-06 15:54:37] DEBUG [util_exec] [e8700ce27eab663b0390339ccf7da49c][0] Starting: openssl x509 -text -noout
[2015-12-06 15:54:37] DEBUG [util_exec] [e8700ce27eab663b0390339ccf7da49c][0] Finished in 0.02478s, Error code: 0

What can this be? Can we consider this to be a bug in Plesk, since no errors are given by the system?

Server: Windows Server 2012 R2
Plesk version: 12.5.30 Update #13
 
The only way I can get it to work is to:
  1. Go to SSL Certificates.
  2. Create a new certificate, upload the old private key and new .crt file.
  3. Assign the certificate to the domain.
  4. Now, the new certificate is assigned correctly and served by IIS.
These are the correct procedures I know ...(If you used the OLD private key to order for the new SSL)
 
Thanks for your reply!
Yes, I did use the old private key. Again, it works for some domains, for some it doesn't...
 
Back
Top