When a site sits behind the Cloudflare proxy, the connection between Cloudflare and your server should be encrypted too, which means the server needs a certificate, especially in Full (strict) mode. Let's Encrypt usually fills that role, but Cloudflare offers its own option: the Origin CA certificate. It is free, issued in minutes and valid for up to 15 years. The catch is that only Cloudflare trusts it; browsers do not.
How it works
Origin certificates are signed by Cloudflare's private CA, whose root is trusted only on Cloudflare's edge. Visitors see Cloudflare's public certificate, while Cloudflare validates your Origin certificate when it connects to your server. That only works while the record is proxied (orange cloud). Switch a record to "DNS only" and browsers connect directly, see the Origin certificate and show a security warning.
When it is a good choice
It shines for projects that will stay behind Cloudflare permanently. A logistics company in Fergana runs misol.uz, kabinet.misol.uz and api.misol.uz on one VPS, all proxied, with the server IP hidden. One Origin certificate for misol.uz and *.misol.uz covers everything for years with no renewal. It also helps when renewing Let's Encrypt behind the proxy is awkward: the firewall only admits Cloudflare IPs, port 80 is closed, or you don't want a DNS API token on the server.
In those setups both ACME challenges become fiddly. HTTP-01 has to pass through the proxy and any redirect or security rules on the way, while DNS-01 needs credentials that can rewrite your zone if the server is ever compromised. An Origin certificate sidesteps both problems, because nothing has to be validated or renewed on a schedule, and the only ongoing task is noting the expiry date somewhere you will see it years from now.
When to avoid it
If you might ever leave Cloudflare or turn off the proxy, the site instantly becomes untrusted for every visitor. Non-proxied names such as mail.misol.uz or FTP need publicly trusted certificates. And any external system that connects to the origin directly, such as a payment provider sending webhooks to the server IP, will reject it.
| Criterion | Cloudflare Origin | Let's Encrypt |
|---|---|---|
| Validity | Up to 15 years | Short, auto-renewed |
| Trusted by browsers | No | Yes |
| Works without Cloudflare | No | Yes |
| Wildcard | Yes, instantly | DNS-01 only |
Creating and installing it
Create the certificate under SSL/TLS, Origin Server in the Cloudflare dashboard, choosing RSA or ECC, hostnames and validity. The default covers the apex and one wildcard level, so *.misol.uz matches api.misol.uz but not v2.api.misol.uz. The private key is shown only once; save it immediately, or you will have to issue a new certificate and revoke the old one.
mkdir -p /etc/ssl/cloudflare
chmod 600 /etc/ssl/cloudflare/misol.uz.key
ssl_certificate /etc/ssl/cloudflare/misol.uz.pem;
ssl_certificate_key /etc/ssl/cloudflare/misol.uz.key;
nginx -t && systemctl reload nginx
openssl x509 -in /etc/ssl/cloudflare/misol.uz.pem -noout -issuer -dates -ext subjectAltName
On Apache use SSLCertificateFile and SSLCertificateKeyFile. The issuer line should mention "CloudFlare Origin". Then set the Cloudflare SSL mode to Full (strict), the mode Origin certificates are designed for.
For sites on shared hosting
You rarely need an Origin certificate on shared hosting. sayt.uz hosting issues free, auto-renewing Let's Encrypt certificates from the panel, and they work the same with Cloudflare in Full (strict) mode or without Cloudflare at all. That keeps you flexible: if you ever drop Cloudflare, nothing breaks. Keep Origin certificates for servers you manage yourself that will stay behind Cloudflare long term.