After Update the Virtualmin , I cannot apply my new ssl cert.

4 posts / 0 new
Last post
#1 Mon, 01/14/2013 - 03:37
andersen

After Update the Virtualmin , I cannot apply my new ssl cert.

After Update the Virtualmin , I cannot apply my new ssl cert.

I have follow the guide to create the new csr. http://www.virtualmin.com/documentation/tutorial/how-to-add-an-ssl-certi...

I go to rapidssl create the certificate. They have sent back the new certificate. When i copy my new certificate to Virtualmin ssl manage new certificate tab, i apply the new certificate is show private not match ? What going on. Before the upgrade of virtualmin , i have follow the guide no problem.

Failed to install certificate : Certificate problem detected : Certificate and private key do not match

I use this tool to check ssl is passed https://www.sslshopper.com/certificate-key-matcher.html

System Centos 5.6 Webmin version 1.610
Virtualmin version 3.97.gpl GPL

Kernel and CPU Linux 2.6.18-238.19.1.el5 on x86_64 Real memory 2.45 GB total

Virtual memory 5.31 GB total

Local disk space 237 GB total

Mon, 01/14/2013 - 08:51
andreychek

Howdy -- when you're in the "New Certificate" tab, and pasting in the new SSL Cert -- you'll see the matching private key pasted in the textbox below.

It's labeled "Matching private key".

By default, the Matching Private Key will be set to "Keep existing private key".

Make sure that's set to "Pasted Text", or else you could receive the error that you're getting.

-Eric

Tue, 01/15/2013 - 22:10
andersen

Thank you quick help Andreychek. I have fixed the mismatch issues. But when i apply the "New Certificate" the newkey.ssl will gone.I need to manually create back my newkey.ssl. Any idea of this case ?

Before My Issues is when i create the csr. It automatic create the new private key. So make my org private mismatch.

Wed, 01/16/2013 - 08:27
andreychek

Well, when you go into the New Certificate screen, it should show the newkey.ssl file in the textarea... and then, once you click save, the newssl.key file will be renamed to ssl.key, overwriting the old key.

Are you saying that's not what's happening though?

-Eric

Topic locked