Please help, my website started to show a 522 Error - Connection Timed Out.
I made no hosting/Cloudflare changes, nor had any peaks in traffic/requests that I’m aware of.
Great that you found the community tip on the topic (OMG… someone actually uses the search ). Most of the steps there involve asking your hosting provider about something, rate limiting, IP blocking etc, so you should probably ask them about those steps 1,2,4 and 5.
Who is my hosting provider? Would it still be GoDaddy despite them saying they don’t have access to the DNS settings? I phoned them twice already, and explained my issue but they were less than helpful.
Yes, GoDaddy are your hosting provider. They are not known for being the most helpful in these situations. They love blaming everything on Cloudflare!
yes, despite them not having access to your DNS they should still be able to answer the questions. You just may have to ask them these questions (taken from that community tip) very directly!
Are they blocking Cloudflare IPs
Are they blocking or rate limiting requests from the Cloudflare IPs
Unfortunately the support person offered no advise or insights into the hosting package, they said all resources/CPU/bandwidth is fine. They tried to sell me a native SSL/firewall package. They said no Cloudflare IPs had been blocked or rate limited.
I can only assume my Wordpress system (and plugins) are causing the slow requests?
I was thinking of making my site temporarily insecure, going in and disabling the caching plugins, purging cache, and checking that?
What typically causes a slow response time? My website is just a simple blog with under 100 visitors a day.
I don’t know where to see the speed of my requests, but I assume they are slow.
Sigh, everything was working fine with the website (SSL + load times) for the past 10 months. On Sunday I got a notification from Jetpack stating the website was down. It has been two days with the 522 connection timed out code.
I wish Cloudflare support would respond and advise me, as I was enjoying the free plan. I am now in a position where I will need to switch back to HTTP and revert to Godaddy nameservers, rather than lose traffic/business from the website…
I’m seeing that the self-signed certificate is for aronfrost.com and not for your domain. Also, having dealt with sites on GD, it doesn’t take much traffic (if any), to cause it to stop responding especially the shared packages with 1CPU, 512MB ram and 100 entry processes. Throwing more money at it don’t help much either. In most cases, CF buys you time before you really need to consider switching hosts to get more for less.
I have 4 Wordpress sites under the deluxe shared hosting package of GoDaddy, with only this website running through Cloudflare and showing the 522 error. The other 3 websites are HTTP unsecure and work load fine.
So it is likely the few hundred visitors a day, and bigger pages/more plugins, on this URL is causing the slow requests?
With all honesty, I’ve seen sites on the GD deluxe package struggle with just 1 WordPress site and 10~20 (or less) visitors per hour and that’s with every possible optimization.
To test speed and connection reliability, I ran tests which isn’t different than a regular visitors on both and they were affected the same. The static page was slightly faster but it’s only a few lines of code and one image and began to see both sites stopping but with Cloudflare, you get to see the error and again, it’s helping by reducing hits to the origin.
Sorry to be the bearer of bad news but at least your getting an honest answer here. If you do search for another host, let us know your Region/Country and maybe someone here can suggest a better hosting company.
Also, keep an eye out for hosts that offer SSD storage, at least 1~2 GB ram, 1~2 CPU’s, unmetered bandwidth, unlimited hosts/databases (if you plan on having more that 4 sites) and cPanel to make thing easy to setup.
). Most of the steps there involve asking your hosting provider about something, rate limiting, IP blocking etc, so you should probably ask them about those steps 1,2,4 and 5.
I can access the Wordpress site (https in red)
