Cloudflare SSL: edge certificates, origin certificates and Full (strict)
Understand Cloudflare’s two TLS connections. Check origin certificate requirements, browser trust and safe troubleshooting before changing encryption mode.
Start by drawing the actual route: visitor, Cloudflare, then hosting server. A DNS-only hostname may connect directly to the server instead. Record which names are proxied and which services must remain reachable without Cloudflare before choosing an origin certificate.
For a Bangladesh business, this matters when a hosting company manages the server while another agency manages Cloudflare. Agree ownership of both certificates and both renewal processes; neither team should assume the other is monitoring everything.
In this guide
A practical checklist
Identify the edge and origin separately
Check Full (strict) prerequisites
Choose a certificate for the intended access
Make the origin ready before changing mode
Test application behaviour and monitor both expiries
Common problems and decisions
Cloudflare reports 526
Cloudflare reports a handshake failure
The site breaks after pausing Cloudflare
Prepare for the next conversation
Supply support with the public hostname, proxy status, error code, origin certificate type and the time the issue began. Keep origin IP addresses and administrative access out of a public case study. A quotation should state whether work covers Cloudflare, the origin server or both, and who maintains renewals afterward.
Continue with the right guide or service
Common questions
Is Cloudflare’s visible certificate the one I installed in cPanel?
Not necessarily. A proxied site can show Cloudflare’s edge certificate while a different certificate is installed on the hosting server.
Do I always need to buy an origin certificate?
No. The suitable option depends on direct-access requirements, automation, validation and support. A compatible free public certificate or Cloudflare Origin CA may fit the architecture.
Can I fix an origin problem by disabling verification?
That can conceal the symptom while weakening the intended security. Diagnose and repair the origin configuration before treating the connection as verified.
Does Full (strict) remove the need for application security?
No. It validates the encrypted connection to the origin; it does not patch the application or protect a stolen administrator account.