No offence, but I wont analyse the issue based on your blank statements. Another domain can have a completely different configuration.
In 99 out of a 100 cases these issues are site related and should this turn out to be an actual Cloudflare issue, the congratulations you’d be one of the few who actually experience such one every couple of months
Any time I go to manage this domain on CF I get multiple errors just from loading the page for the domain in the dashboard. This coupled with the weird ■■■■ going on when the domain is accessed and the fact that using another domain that has the exact same routing works fine, leads me to more than believe that this is cloudflare’s problem.
Giving you my origin isn’t going to accomplish anything other than publicly exposing a server that I am contractually obligated to prevent the exposure of. You’re not going to be able to troubleshoot anything from there. What I can do is point a subdomain from one of my other domains to act as an alternate.
I have set up test.lionhacks.best to point to the same place as adshare.club and everything works fine there.
^Hi @Stage4000, that error is unrelated to the 521 error your origin is passing to Cloudflare. If you’re still seeing that API error (I am not seeing that in your account at the moment), please let Support know. The team found & fixed that a few weeks ago and if you’re seeing it now, they’ll want to know about it.
That host also points to Cloudflare, which would actually prove that it is not a Cloudflare issue unless you are trying to suggest Cloudflare’s proxies return content differently based on the host name in the request.
Anyhow, I am afraid there is not much more I can do. As I said earlier I would suggest you check out the developer tools, if that doesnt work for whatever reason I could only refer you to support.
Bugs do happen. Hence Sandro’s suggestion to analyze your site’s coding. It’s one thing to simply use .css and .js from third parties; it’s quite another to actually understand what they do and and don’t do; if they’re necessary or not. Your site is very weighed down with excess scripts some of which do throw errors. Simply because it may “work locally” for you does not mean it should function fine when online.
We havent, you have determined something but nobody can verify that.
If you are convinced it is an issue with Cloudflare and you dont want the community’s help your only option is to either debug it yourself - as I suggested quite a few times - or to contact support. It is your choice.