Clarkes.Team
(866) CLARKE6 Get Started Client Portal

Based in Downtown Brooklyn

Cloudflare setup, DNS, and troubleshooting

  • We support it
  • We run it for clients
  • We use it ourselves

Cloudflare sits in front of your website: DNS, SSL, caching, a firewall and a CDN in one dashboard. It fixes a lot and, misconfigured, it breaks a lot. We set it up, tune it, and untangle the problems it causes.

Tell us what’s going on See the problems we fix

The relationship

How we work with Cloudflare

  • Support

    We support it

    Error 52x pages, redirect loops after enabling SSL, a cache that serves the wrong thing, email that stopped working after a DNS move: we know where each of these hides.

  • Managed

    We run it for clients

    For clients on a managed plan we run Cloudflare as part of the stack: DNS, SSL, firewall rules, caching rules and monitoring, with every change tracked.

  • In-house

    We use it ourselves

    Our own domains sit behind Cloudflare, so the setups we recommend are the ones we live with.

Sound familiar?

Cloudflare problems we fix

You don’t need to know the technical name for it. Tell us what’s happening, and we’ll work out what needs attention.

  1. “A redirect loop, or “too many redirects”, after turning on SSL.”

    Almost always the SSL mode. We set Full (strict) with a valid origin certificate and check the site’s own redirects.

  2. “Error 520, 521, 522 or 524.”

    These mean Cloudflare can’t reach, or hear back from, your server. We check the origin, firewall allowlists and timeouts, and fix the side that’s actually failing.

  3. “Email broke when we moved DNS to Cloudflare.”

    Proxied mail records and missing MX, SPF or DKIM entries are the usual cause. We rebuild the records and verify delivery.

  4. “Logged-in users see other people’s pages, or the cache never clears.”

    Cache rules that ignore cookies or dynamic paths. We write rules that cache what’s safe and bypass what isn’t.

  5. “We’re getting hammered by bots or a DDoS.”

    WAF rules, rate limiting, bot protection and challenge pages, tuned so real customers get through.

  6. “Moving to Cloudflare feels risky.”

    We stage the move: lower TTLs, mirror every record, switch nameservers, and watch. Done properly it’s invisible to visitors.

Something else with Cloudflare? Tell us about it.

Where it fits

The services behind the Cloudflare work

Related technologies

Questions we get

Cloudflare, answered plainly

Do we need a paid Cloudflare plan?

Often not. Most business sites do well on the free plan with the right configuration. We’ll tell you if a feature you actually need is behind a paid tier.

Can you move our DNS to Cloudflare without downtime?

Yes, that’s the normal way to do it: lower the TTLs first, copy every record, then switch. We check mail and subdomains before and after.

Does Cloudflare replace a security plugin?

It adds a layer in front. Application-level security on the site itself still matters, and we look at both.

Can you manage Cloudflare on an ongoing basis?

Yes, as part of a managed server or WordPress plan, with rules and changes documented.

Start the conversation

Got a Cloudflare headache?

Tell us what’s giving you trouble, or what you’d like to stop managing yourself. You don’t need a technical brief. A few sentences is a good place to start.

What’s it about? (optional, pick any)

No technical explanation needed. Please don’t include passwords or sensitive information.

Goes straight to our team so we can reply. Privacy policy