5xx error specially 520 error. I have bought the domain, added to Cloudflare. But it shows 520 error for no reason. I said no reason because I have two other websites proxied by Cloudflare hosted on the same server. Yet, I contacted my hosting provider, they checked thoroughly but found no issue or nothing on error log. Yet I thought the problem is somehow happening for the sever. So I bought another hosting package from another hosting provider. There I have encountered the same issue. Then I host another website wpforweb [dot] com on the same server and added it to Cloudflare. wpforweb works fine but wppassion doesn’t. So I have come to a strange conclusion that maybe Cloudflare blocklisted or rate limited or restricted my doamin. As a free user I have no right to create a support ticket. Is there any support agent in this community who can invesitigate the issue?
520 usually means the response from your origin is unexpected. Set the DNS record to “DNS only” to see what you get back from your server when bypassing the Cloudflare proxy.
Check that you are not blocking any Cloudflare proxy IP addresses at your origin. I’m not able to reach the site when using Cloudflare WARP as it times out.
No Cloudflare IP is blocked. That’s what the hosting provider told me. To confirm it, I’ve added wpforweb.com on the same server and proxied it by Cloudflare. It works fine. If the Cloudflare IP was blocked, wpforweb wouldn’t work either.
Right now, it’s flexible. If I want to set “Full (strict)”, I need to use Orgin certificate. Do I must need to do it in order to investigate the issus?
You should always use an origin certificate and “Full (strict)” otherwise the connection is not secure.
I’m not sure if my inability to connect over WARP is the same as why Cloudflare can’t connect to your origin, but using WARP I can connect to your origin on port 80 and 443 OK, sends the headers but then there is no response from the origin. Look in your origin logs to see if you can see the requests I’m making that do that.
curl -ivv http://wppassion.com
* Host wppassion.com:80 was resolved.
* IPv6: (none)
* IPv4: 115.187.18.37
* Trying 115.187.18.37:80...
* Connected to wppassion.com (115.187.18.37) port 80
> GET / HTTP/1.1
> Host: wppassion.com
> User-Agent: curl/8.7.1
> Accept: */*
>
* Request completely sent off
[connection hangs with no response from the origin]
[add] Some WARP connection to the other hostname…
curl -ivv http://wpforweb.com --connect-to ::115.187.18.37
* Connecting to hostname: 115.187.18.37
* Trying 115.187.18.37:80...
* Connected to 115.187.18.37 (115.187.18.37) port 80
> GET / HTTP/1.1
> Host: wpforweb.com
> User-Agent: curl/8.7.1
> Accept: */*
>
* Request completely sent off
< HTTP/1.1 200 OK
HTTP/1.1 200 OK
< Connection: Keep-Alive
Connection: Keep-Alive
< Keep-Alive: timeout=5, max=100
Keep-Alive: timeout=5, max=100
< content-type: text/html
content-type: text/html
< last-modified: Sun, 18 May 2025 09:19:06 GMT
last-modified: Sun, 18 May 2025 09:19:06 GMT
< accept-ranges: bytes
accept-ranges: bytes
< content-length: 113
content-length: 113
< date: Mon, 19 May 2025 09:24:51 GMT
date: Mon, 19 May 2025 09:24:51 GMT
< server: LiteSpeed
server: LiteSpeed
< Server-Timing: cfReqDur;dur=179.181
Server-Timing: cfReqDur;dur=179.181
< Cf-Team: 27897550290000cd5874f35400000001
Cf-Team: 27897550290000cd5874f35400000001
<
<html>
<head>
<title>Test for New site</title>
</head>
<body>
<p>This is a test for New site</p>
</body>
* Connection #0 to host 115.187.18.37 left intact
</html>%
So there is different behaviour at your origin from my WARP connection for some reason.
Let me change DNS record to proxied from dns only for wppassion. I have no problem for wpforweb. I just want to make wppassion works on Cloudflare network.
Ok I have changed from dns only to proxied. Please check to see if there is any luck.
No need, the above test was done directly to the same origin IP address. For that host I can connect OK when using WARP, for the other host, I cannot. Without WARP I can connect to both. No idea why that might be at the moment.
Update: I have proxied the IP. Do you know any way I can contact Cloudflare authority to check if they have banned the domain for the previous owner? As the I am the current owner, the ban should be removed.
There is no ban. A 520 error means Cloudflare can’t get a response from your origin, and as I showed above, if I connect from WARP direct to your origin, I can’t either for that hostname. Check the logs on your origin to see if they show anything.
5xx error specially 520 error. I have bought a domain, added to Cloudflare. But it shows 520 error for no reason. I said no reason because I have two other websites proxied by Cloudflare hosted on the same server. Yet, I contacted my hosting provider, they checked thoroughly but found no issue or nothing on error log. Yet I thought the problem is somehow happening for the hosting. So I bought another hosting package from another hosting provider. There I have encountered the same issue. Then I host another website wpforweb [dot] com on the same server and added it to Cloudflare. wpforweb works fine but wppassion doesn’t. So I have come to a strange conclusion that maybe Cloudflare blocklisted my doamin. As a free user I have no right to create a support ticket. Is there any support agent in this community who can invesitigate the issue?
The REST API encountered an error and Your site could not complete a loopback request. Both errors are showing the reason: cURL error 28: Connection timed out after 10002 milliseconds (http_request_failed). I wouldn’t create a new topic but when I paused Cloudflare, the issues are gone. When I unpaused Cloudflare, the issues are back again.
If the IP address is still the same, as it was above, then your origin isn’t providing a valid certificate for wppassion.com, but one that has been issued for a completely different domain name.
What I see on the URL from your screenshot, is that Cloudflare is displaying a “525 SSL handshake failed”, after waiting ~ 45 seconds, which indicates a problem with establishing a secure connection to your origin.
If the origin IP has changed in the meantime, please provide the new one.
