massi-x.dev
Connection timed out
Connection timed out
DNS not responding/updating
Open massi-x.dev, it would probably fail, or maybe not.
Hi everyone, when trying to access my website at https://massi-x.dev I eventually get a 522 timeout error. I completely understand that the cause is an unresponsive origin server but (I know it’s not easy but you should trust me) this is not the case.
The error keeps happening from a few weeks now, and totally at random. I recently checked and updated DNS records and everything seems fine, but the thing that got me into thinking this is some sort of problem with DND caching or something alike is that when completely disabling proxy I still get the error.
This error appears almost reliably on some internet connection and in some browsers while other perfectly works fine. I cannot understand how is possible I keep getting the cloudflare error screen instead of a generic one when disabling proxy.
Looks like it’s working fine now over HTTPS and proxied 
Could you confirm?
You’ve also got multiple cache systems:
x-cache: HIT
via: 1.1 varnish
x-proxy-cache: MISS
x-served-by: cache-bom4746-BOM
x-turbo-charged-by: LiteSpeed
Hi and thank you for the response. The error is completely random and I’m really can’t find a reason why.
Yes the website is working but this really depends from where you connect. I did experiment connecting with curl and forcing the use of cloudflare IPs (I found the IPs that connects to my origin here and input all of them one by one in the curl command like this curl -v https://massi-x.dev "massi-x.dev:443:ONE_IP_FROM_LIST). The interesting thing is that one of my devices fails when connecting with the IP 104.21.80.1, while the other completely works fine. How is this even possible?
Thank you for feedback.
I wonder, but maybe Cloudflare is or was updating something or rolling out some features such as we’ve experienced in the past related to the Speed brain feature and more, where users started to provide feedback that something was suddenly not working as expected out of nowhere.
I have contacted the hosting provider and they confirmed there is no firewall/ip block or anything on their part. And the strange thing is that as said above, on device connects fine to all cloudflare IPs, while the other (testing again right now) is failing almost on everything (now it only works on .16 and .96 - with error 522).
It seems to me this is triggering some kind of DDoS protections? (Could be I’m making a lot of requests). But if this is the case a 522 error is not a clear indication to me.
I cannot contact cloudflare so I don’t know what to do now.
If true, you’d get a different error 4xx related, not 5xx.
Yep, true. I really don’t know what to do 
Hi Massi-X
Where are your browser getting the 522 located? Spain by chance? We’re getting some weird random 522 only when the Madrid node is involved.
Italy, but some browser (or better, the whole device) can nicely surf, other cannot but only when some proxys are involved. On the other device all the proxies work fine.
Anyway gave up and disabled proxy altogether. Now I’m also in the middle of a server migration 
This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.
