When something on your site breaks and Cloudflare is in the picture — a page not loading, an unexpected redirect, an SSL error — the cause is often a specific Cloudflare setting actively causing the problem, which this diagnoses and corrects, distinct from a broader, proactive review of your whole Cloudflare setup done when nothing’s actively wrong.
Try bypassing Cloudflare temporarily to confirm it’s actually involved
If you have a way to access your site directly through its origin server (bypassing Cloudflare, sometimes via a modified hosts file entry or a direct IP), comparing that against the normal, Cloudflare-routed experience helps confirm whether Cloudflare itself is actually part of the problem.
Cloudflare settings audit & correction
Something actively broken with Cloudflare in the picture, traced to the one setting causing it.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
This or something else?
| Something is actively broken and you suspect a specific Cloudflare setting is the cause | This fix covers it |
| You want a comprehensive, proactive review of your whole Cloudflare setup, not a specific active problem diagnosed | Cloudflare full configuration audit & setup, in the Integrations & Automation bucket, the broader, proactive version |
| The issue is specifically page rules or cache rules causing incorrect caching | Cloudflare page rules & cache rules setup, in the Integrations & Automation bucket, a more targeted version |
| The conflict is between Cloudflare and your origin server more generally, not one specific setting | CDN configuration & origin conflict fix, the broader diagnostic |
What you are seeing
- A page failing to load, redirecting unexpectedly, or showing an SSL error specifically when accessed through Cloudflare
- The issue possibly resolving when Cloudflare is temporarily bypassed
- The problem starting after a specific, identifiable Cloudflare setting was changed
- Inconsistent behaviour depending on caching state within Cloudflare
Common causes
- An SSL/TLS mode setting mismatched with your origin server’s actual certificate configuration
- A firewall or security rule inadvertently blocking legitimate traffic or a specific feature
- A page rule configured incorrectly, causing unexpected caching or redirect behaviour
- A recent Cloudflare setting change made without fully testing its site-wide effect
- A fallback feature like Always Online serving a cached snapshot because Cloudflare incorrectly believes your origin server is unreachable
What we do
- Confirm Cloudflare’s actual involvement by comparing against direct origin access where feasible
- Review recent Cloudflare setting changes and current configuration for the specific cause
- Correct the identified setting causing the active problem
- Verify the issue is resolved through the normal, Cloudflare-routed path
- Confirm no other functionality was affected by the correction
- Document the cause and correction for future reference
What is included
- The specific Cloudflare setting causing the active problem identified and corrected
- Verified resolution through the normal, routed path
- Confirmation no other functionality was affected
- A written note on the cause and correction
Not included
- A comprehensive, proactive review of your entire Cloudflare configuration beyond the specific active problem — a separate, broader fix
- Page rule or cache rule setup as a standalone project, a separate, related fix
- Resolving a genuine Cloudflare service outage — that’s Cloudflare’s own issue, on their timeline
- Ongoing monitoring for future Cloudflare-related issues
Questions about this fix
How is this different from the full Cloudflare audit service?
This is specifically diagnostic — something is actively broken, and we're finding the specific setting causing it; the full audit is a proactive, comprehensive review of your whole configuration done as a health check, not in response to an active problem.
What if I'm not sure whether Cloudflare is actually involved in my issue?
Comparing behaviour with and without Cloudflare in the path, where that's feasible for your setup, is the most direct way to confirm this — we can help establish that comparison as the first step of diagnosis.
Could a change I made recently in Cloudflare have caused this?
Yes, that's a common pattern — a setting changed without fully testing its site-wide effect is one of the more frequent causes of this kind of sudden, specific breakage.
Will fixing this specific setting also improve my site's overall Cloudflare configuration?
Not necessarily beyond resolving the active problem — if you'd also like a broader review to catch other, non-urgent issues, that's the separate, comprehensive audit service.
Is this urgent?
Generally yes, if it's actively affecting your site's function or accessibility for visitors right now, which is the nature of a diagnostic fix like this versus a proactive, scheduled review.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.