Error 522 - Site Inaccessible - Urgent Help Needed on Free Plan

Application Performance
1

What is the name of the domain?

churcheurobin.com.au

What is the error number?

522

What is the error message?

Connection timed out

What is the issue you’re encountering

My website is inaccessible!

What steps have you taken to resolve the issue?

Hi there,

I’m reaching out for help with my website churcheurobin.com.au, which is currently returning an Error 522 – Connection Timed Out.

I’m on a free Cloudflare plan and unfortunately can’t access direct support. My hosting provider (HostPapa) has reviewed the issue from their end and responded with this:

“With your website, maybe try contacting Cloudflare support and find out what the issue is exactly and whether that can be rectified promptly before we can further advise on this. I will remain on standby for further assistance.”

I can access my HostPapa dashboard, but the site itself remains unreachable and hasn’t come back online. I haven’t made any recent changes to DNS settings, and everything appears to be configured as it was when the site was working.

I should add that I’m not very experienced with this sort of thing, so if there’s anything obvious I should check or clarify, I’d be grateful for guidance in plain language.

I’d be very grateful for any help or direction - especially in confirming whether this is a Cloudflare-side issue and if there’s a way to resolve it without needing to upgrade plans.

Thank you in advance,
Alison

What are the steps to reproduce the issue?

Unable to login to website

Screenshot of the error

Screenshot.png
Screenshot.png2044×1462 201 KB

2

Can you change the DNS record for your site to DNS-Only so we can see whether the problem is with your host or Cloudflare?

1 Like
3

Hi Laudian

Thank you for getting back to me. I didn’t know what DNS was so I had to ask ChatGPT (yes I’m embarrassed!!).

I believe I’ve changed the DNS record now. I’m told you should be able to see this within about five minutes. That would be good.

Cheers, Alison

4

Can you maybe show a screenshot of your DNS records?

You can find them here after selecting your domain: https://dash.cloudflare.com/?to=/:account/:zone/dns/records

They are still proxied as of now, and I’d be able to see any change immediately.

1 Like
5

image
image1920×1373 143 KB

Please can you tell me from the picture what I need to do?

6

Your server isn’t responding. You’ll need to contact your host and work with them to get that fixed.

Keep your DNS record on DNS-Only until the website starts working again.

Also confirm with your host that the 64.xxx.xxx.xxx IP address is the correct address that you should use.

1 Like
7

Laudian has given the best advice – contact your hosting service. Since it looks like your DNS settings are in order and have taken effect, a few things your host might want to look for include:

  1. (Most obvious) that the IP address of your server is indeed 64.34.75.146

  2. (Most likely) that there isn’t a firewall setting that is somehow blocking Cloudflare – i’m not sure what firewall they’re using but you can start by asking to temporarily disable ModSecurity and see what happens. Trying to be helpful, sometimes firewalls “develop” rules that can inadvertently block things that should not be blocked.

  3. (Less likely) You’re somehow getting an extreme amount of traffic and your website is built where dynamic content is so prominent that Cloudflare can’t take the weight off your server’s shoulders… and your server is overloading because of the strain on resources (and Cloudflare can’t connect with it before it “times out”).

8

Thank you for the reply Laudian. It has taken Hostpapa a while to get back to me… but here is the response:

"You are absolutely right, having the website be operational is a priority in this situation. The first thing I checked was how the website would work if we bypass Cloudflare’s services. I achieved this using two methods. One is a simply Temporary URL, that directly forces the site to work from the IP address of the server and skips Cloudflare all-together. This is the URL:

→ [https://. kykoxmlpox. papa-view (dot) com] (https:// kykoxmlpox .papa-view (dot) com/)

And another by using my local hosts file and adding the respective lines:

66.102.133. 145 [church eurobin. (dot) com.au](http:// churcheurobin (dot) com.au/) [www.churcheurobin (dot) com.au](http://www. churcheurobin (dot) com.au/)

Both ways, are simply to test the site directly without Cloudflare interference, and it appears that the website is fully able to resolve without any issues when doing so, here is a screenshot of how it appears on my end:

→ https: // i.imgur(dot). com. /. GQtc2QA. jpeg

I would only like to note that most of your images were not resolving properly, thus I temporaryly disabled the plugin:

→ jetpack-boost

And they started appearing correctly once again.

I believe the issue is mainly due to the IP that you are using in Cloudflare:

→ 64.34.75.146 - [hp316.hostpapa. (dot)com](http://. hp316. hostpapa. (dot)com/)

The above is the server where your data used to be located on, however the entire server was migrated to a brand new environment some time ago, and thus the IP was adjusted. The new IP is:

→ 66 (dot) 102.133.145 - sh-cp6-au.yyz2 (dot) servernameonline

As such, please proceed to update the “A” records in your Cloudflare account to the above-mentioned IP address. Once you do so, your website should be up, shortly thereafter.

Considering the above, we are looking forward to your next update on the case."

I took his advice and changed the IP address where instructed and the site seems to be back!

Thank you for helping me.

Alison

1 Like
9

Thank you for helping me. I put a reply on @Laudian …

1 Like
10

I’m now getting a 200 response when going through the Cloudflare proxy:

> GET / HTTP/2
> Host: churcheurobin.com.au
> User-Agent: curl/8.7.1
> Accept: */*
> 
* Request completely sent off
< HTTP/2 200  <~~~~~~~~~~~~~~~~~~~~~~~~ 200 Response
< date: Sun, 15 Jun 2025 02:03:38 GMT
< content-type: text/html; charset=UTF-8
< x-powered-by: PHP/8.0.30
< link: <https://churcheurobin.com.au/wp-json/>; rel="https://api.w.org/", <https://churcheurobin.com.au/wp-json/wp/v2/pages/2421>; rel="alternate"; title="JSON"; type="application/json", <https://churcheurobin.com.au/>; rel=shortlink
< cache-control: max-age=172800
< expires: Tue, 17 Jun 2025 02:03:37 GMT
< vary: Accept-Encoding,User-Agent
< report-to: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=mck6jmdrSiOolaIWew7F068Iabbos33%2FAcs7%2FMMcRrt1PfeHqT21tTQf%2BfrBiR8XLkxj8D0rrZl%2FSnWAad9xK8nZIQy4mXWbv704w7m%2BSHyIA1T2"}]}
< server: cloudflare <~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Cloudflare
< cf-cache-status: DYNAMIC
< nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
< cf-ray: 94fe7df7dac07bbc-LAX
< alt-svc: h3=":443"; ma=86400
11

I’m glad you got your site working again :wink:

Have a nice Sunday!

2 Likes
12

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