Does Let's Encrypt Need a CSR? (And When You Must Supply One)

Short answer: no, and also yes
Let's Encrypt never asks you to upload a CSR through a web form. The ACME protocol has a finalize step where the client sends a CSR, but the client builds that CSR itself — the key is generated on your machine, signed into a CSR, and only the CSR travels to the CA.
So for the common case the answer is: you do not create a CSR by hand. Run certbot --nginx -d example.com, and certbot creates privkey.pem and the CSR, completes the challenge, and writes the certificate.
There are still four situations where you do need to produce the CSR yourself.
When a manual CSR is actually required
| Situation | Why the client cannot do it |
|---|---|
| Private key lives in an HSM or cloud KMS | The key cannot be exported, so the CSR must be signed inside the boundary and exported instead |
| Enterprise CA or hoster issues for you | Their portal wants a CSR file; they never see your key |
| You are reusing an existing key | The client would generate a new key and invalidate your pinned public key |
| You are debugging a failed finalize call | You need to inspect exactly which names the CSR carried |
Build the key and the CSR with OpenSSL
One command produces both files. The -addext flag keeps the SAN list on the CSR, which is what Let's Encrypt actually reads:
openssl req -new -newkey rsa:2048 -nodes \
-keyout privkey.pem -out request.csr \
-subj "/CN=example.com" \
-addext "subjectAltName=DNS:example.com,DNS:www.example.com"For an ECDSA key (smaller, faster handshakes — fine for Let's Encrypt):
openssl req -new -newkey ec -pkeyopt ec_paramgen_curve:prime256v1 -nodes \
-keyout privkey.pem -out request.csr \
-subj "/CN=example.com" \
-addext "subjectAltName=DNS:example.com,DNS:www.example.com"Both commands write privkey.pem unencrypted (-nodes). That is what a web server needs, and it is also why the file must be readable only by root.
Check the CSR before anyone signs it
openssl req -in request.csr -noout -textThree things matter in the output:
- Subject Alternative Name lists every hostname. CN is decorative — Let's Encrypt validates against SAN only.
- Public Key Algorithm and size match what you intended (2048-bit RSA or P-256).
- Signature Algorithm is present and matches the key type. A CSR with no signature block is not a CSR.
The site's CSR Decoder parses the same fields in the browser if you prefer not to paste the file into a shell.
What the CA does with the CSR
The ACME flow looks like this:
- The client asks for an order covering a set of identifiers.
- The CA hands out challenges (HTTP-01, DNS-01, TLS-ALPN-01).
- The client proves control of each identifier.
- The client POSTs the CSR to the finalize endpoint.
- The CA checks that the CSR names are exactly the validated identifiers, then issues.
Step 5 is where most manual attempts fail. If the order covers example.com and www.example.com but the CSR only lists example.com, finalize returns an error about identifier mismatch. The CSR cannot add names after validation — the two lists have to agree.
Four mistakes that break a Let's Encrypt CSR
- Missing SAN. A CSR with only
CN=example.comvalidates nothing on modern clients; the SAN extension is mandatory. - CN and SAN disagree. Some tools copy CN into SAN, some do not. Always inspect the file.
- Wildcard without DNS-01.
*.example.comrequires a DNS TXT challenge; HTTP-01 cannot prove a wildcard. - Key and CSR from different runs. If you regenerate the key after creating the CSR, the final certificate will not match your server key. Use the key-match tool to compare modulus or public point before deploying.
Reusing a key across renewals
A CSR is not tied to a certificate lifetime. You can keep the same private key for years and only regenerate the CSR — some teams do this because the key is pinned in configuration management, or because they rotate keys on a separate schedule from certificates.
The trade-off: a leaked key stays dangerous until you rotate it, no matter how often the certificate renews. If you have no operational reason to pin the key, let the client generate a fresh one on every renewal — that is the default for a reason.
Do it in the browser instead
If the CSR is only needed to hand to a panel, the CSR generator produces the key and CSR locally and never uploads either. Export the key, keep it off the network, and paste only the CSR where it is asked for.
FAQ
Can I paste my own CSR into Let’s Encrypt?
Yes, at the ACME layer. The client’s finalize call submits a DER-encoded CSR; a tool that lets you paste a CSR simply skips local key generation. The certificate is issued for the names in that CSR, so it must match the identifiers you already validated.
Does certbot overwrite my CSR or key?
certbot creates a new key pair per lineage under /etc/letsencrypt/live/<domain>/. If you replace the key manually, renewals keep using the file at that path — so swap it in place, or point --key-path at your own key.
Is a CSR required for a wildcard certificate?
The CSR must contain DNS:*.example.com, and the ACME challenge has to be DNS-01. A wildcard is not allowed through HTTP-01, so the CSR and challenge type have to be planned together.
Why does my CSR work with a commercial CA but fail at Let’s Encrypt?
Usually a name mismatch: commercial CAs often accept the CN while Let’s Encrypt only reads subjectAltName, or the CSR contains an internal name that cannot be validated publicly.
Free SSL/TLS tools
Verify and inspect your certificates in seconds.
Related Certificate Info
Learn more about choosing and buying certificates.