问题原文
原帖链接 · Joel Chu · CC BY-SA 3.0
Here is what happened:
I generate the CSR via the MediaTemple site (that is the only way to do it. since a GS is a share server). Send it over the namecheap.com (its signed by RapidSSL).
When I got back the certificate and CA. Tried to import it back the media temple. I get the
"Key do not match" error.
Contact both support. They just keep pushing the blame to the other. namecheap.com say there is an RSA key generate (which I do not have access to). And media temple just blame other people outright without even trying to explain what could have gone wrong.
My question is:
Anyone has the same problem?
What could be the cause of this error?
Thanks
已采纳解答
原帖链接 · Stephane · CC BY-SA 4.0
I have similar issue pretty often but that is because I'm generating a lot of certificates manually and singing them with an internal CA.
The cause of the issue is pretty straightforward: the private key that your server has kept doesn't match the public key embedded within your certificate.
The most common cause of this error is, by far, an operator error, sometimes made worth by poorly designed software. Basically, what often happens is that you generate a key pair and a CSR (Certificate Signing Request), send the CSR and then re-generate a new key pair. If the software is too dumb to remember more than one key, then it will lose the previously generated private key.
The solution for these kind of issues, if you're unwilling to simply outsource the job to the server operator. is to generate everything locally (using OpenSSL is the best option) and be careful about the private key you generate (I use a local Mercurial repository for this, which allows me to keep track of what was generated when and, if necessary, go back in time). Once you have the signed certificate, you it, along with the private key, to the server.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
