Fail

The CSR's signature doesn't match its key

The short version

Make the CSR again with the private key it should belong to.

What it means

A CSR is signed with the private key whose public half it carries. That signature proves whoever sent the request holds the key. For this request the signature doesn't verify with the public key inside it: the request was changed after it was signed, damaged when it was copied, or put together by a tool that signed it with a different key.

Why it matters

Every certificate authority checks this signature first and rejects a request that fails it, usually with a vague error such as "invalid CSR". Even if one accepted it, the certificate would carry a public key you might not hold the private half of, and it couldn't be installed. Editing a request by hand, for example to change a name in the base64 text, always breaks the signature.

How to fix it

  1. Find the private key the request was made with. If you can't be sure which one it is, make a new key: it costs nothing.
  2. Make the request again from that key. With OpenSSL: openssl req -new -key example.com.key -out example.com.csr. Or make a new key and request together with the CSR generator.
  3. Copy the whole request, from the BEGIN line to the END line, without changing any characters. Paste it as plain text; a word processor can change dashes or wrap lines.
  4. Send the new request to your certificate authority.

Check it worked

Paste the new request into the certificate decoder. The card should say its signature matches its key, and the names and key should be the ones you expect.