Cloudflare SSL set to Flexible
With SSL/TLS mode set to Flexible, Cloudflare serves HTTPS to visitors but talks to your origin server over plain HTTP. The leg between Cloudflare and your server is in the clear.
Why it matters
Anyone on the path between Cloudflare and your origin — a hop, a cloud network, a compromised router — can read or alter the traffic, including session cookies and form data.
Visitors see a padlock and assume the connection is secure end-to-end. Flexible mode makes that padlock a lie, which is both a security and a trust problem.
How to check for it
- Cloudflare dashboard → SSL/TLS → Overview shows the current mode. 'Flexible' or 'Off' is the problem; 'Full (strict)' is the goal.
- Via the API: GET /zones/:id/settings/ssl — the value should be 'strict', not 'flexible' or 'off'.
How to fix it
- Install a valid certificate on your origin (a free Cloudflare Origin CA certificate works) and set SSL/TLS mode to Full (strict).
- Turn on 'Always Use HTTPS' and set Minimum TLS Version to 1.2.
- Avoid 'Full' (non-strict) in the long run — it encrypts but doesn't validate the origin certificate.
SkyShield checks this automatically
Connect your AWS, Cloudflare, GitHub, GitLab, Hetzner or DigitalOcean account read-only and SkyShield flags this across every account and region, with the fix in plain words — alongside the agent that watches your servers. Start free.
FAQ
- What's the difference between Full and Full (strict)?
- Full encrypts to the origin but accepts any certificate, including self-signed or expired. Full (strict) validates the origin certificate too, which is what you want.