Migrating from Akamai to Cloudflare

Website, Application, Performance DNS & Network
1

What is the name of the domain?

www.(testsite).com

What is the error number?

522 etc

What is the error message?

timeout, or too many redirects

What is the issue you’re encountering

Unable to successfully load subdomain when divorced from Akamai

What steps have you taken to resolve the issue?

Multiple, including discussing with internal Akamai experts, and plowing through existing knowledge.

What feature, service or problem is this related to?

DNS records

What are the steps to reproduce the issue?

  1. Turn proxying on for test.(mysite).com.
  2. Without proxying, it’s pure DNS and just fine, but points to icky Akamai.
  3. With proxying on, any one of a number of errors occur, as I attempt to adjust redirecting, A vs CNAME, etc
2

Welcome to the Cloudflare Community. :logodrop:

Have you told Cloudflare to connect to Akamai instead of your origin server?

Check the IPs you have set in your DNS.

Also be sure that you have your Encryption mode set to Full (strict) in Cloudflare so that you don’t create unwanted infinite redirects.

3

Hi! Thanks so much for the speedy reply.

Big picture - the desire is to bypass Akamai entirely and connect to the origin server; once that’s working, carefully apply whatever Cloudflare protections we may come up with.

Cloudflare owns the DNS entries, the vast majority of which are set to unproxied for now (feeding Akamai) while I get this working on a couple of subdomains.

Currently the subdomain ‘test’ points to a place within edgekey[.]net (Akamai CDN) using a CNAME.

When I update that record to either the hostname (which frustratingly is a different domain we own) or IP of the origin server and enable proxying, that’s when the 522 throws.

If I try a 302 redirect in Redirect Rules, leaving proxying on, I get ERR_TOO_MANY_REDIRECTS.

If I try a Host Header Override to the target domain, I get a 522 again.

I’ve since heard that they’re not using anything found under techdocs[.]akamai[.]com/property-mgr/docs/content-tgting. I’ve vetted similar features with them earlier, and it appears the Cloudflare defaults should be fine - but there are a lot to consider!

I double-checked just now, and encryption for the domain is set to “Strict (SSL-Only Origin Pull)”. I thought there was a way to alter that at the subdomain level if needed, to keep the main domain (and our sweet sweet revenue) safe, but couldn’t find it.

4

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.