Recently migrated from Wordpress Hosted using Securi firewall to Kajabi, set up 301

What is the name of the domain?

bartoliconsulting.com

What is the error number?

502

What is the error message?

Error Message: Backend or gateway connection timeout

What is the issue you’re encountering

I recently moved my domain from wordpress hosted using Securi firewall, to Kajabi. I have a 301 redirect set up inside cloudflare for all non www requests for this domain to be redirected to the www version of the site, however I encounter an error:Error Code: HTTP 502 Error Message: Backend or gateway connection timeout. Server ID: 14034 What’s going on? Origin server might be down Sucuri Network blocked by Origin Firewall

What steps have you taken to resolve the issue?

Established a 301 redirect rule for all non WWW URLs to redirect to the www version of the domain. I attached screen shot of the rule

What feature, service or problem is this related to?

Nameservers

What are the steps to reproduce the issue?

  1. go to You are being redirected...
  2. You will see the error

Screenshot of the error

You have several issues…

Your DNS records for the apex domain are not proxied so no redirects can have any effect on that as requests are not passing through your Cloudflare account.
https://cf.sjr.org.uk/tools/check?31bbf01259904e528747bc43ad62d252#dns

The static redirect must start with https://. Note that your current redirect rule will also redirect www to www so end up in a loop.

Better for you to create the rule for…
Hostname does not equal www.bartoliconsulting.com

Then use a dynamic instead of static redirect to…
concat("https://www.bartoliconsulting.com", http.request.uri.path)
…to pass the path, and select “preserve query string” as well.

1 Like

Yep, I think I noticed the loop occur - definitely an issue! I just uploaded the bulk redirects about 5 min ago, how long should that take effect?

ok, so I did just now proxy the server, but now I’m getting Bad Gateway 502, I’ve been told NOT to proxy because you get that.

Which record did you proxy?

both the A record and the CNAME - though, I’m not seeing the error any longer, and looks as though the bulk migration all took effect

The CNAME for www can remain “DNS only”, as that is the target of the redirect (although if it works, you will be using O2O so requests will pass through your account first).

Anything you want to redirect from needs to be proxied. You can replace those records with AAAA 100:: as they don’t need to point at your host because you are redirecting away from those anyway.

1 Like

and from my understanding, the O2O is NOT ideal! Therefore, whether it works or not, it should NOT be proxied?

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