Api request failed?

There is no JS issue in the code, as stated previously twice now the site works perfectly when I move it to another domain.

If everything works when I view it on another domain but doesn’t work on the domain that is giving API errors when I try to manage it in the CF panel, then how is it unclear that this is a CF issue?

And that is?


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 :wink:

1 Like

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.

The dashboard is unrelated to your site and so are errors.

Again, if you can reveal the origin (also in private if you prefer) that would be a starting point, otherwise you’d need to debug that yourself. I have already given you two starting points for that.


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.

Beyond that, if you see the 521 again, you could walk through the first half-dozen quick fix ideas in this tip just to cross them off the troubleshooting list: Community Tip - Fixing Error 521: Web server is down.

I don’t see a 521, perhaps clear cache if you’re still seeing it or try from a different/mobile browser.


It will allow me to verify your claim that the issue only appears in the context of Cloudflare.


check the domain test.lionhacks.best. It points to the exact same origin and works perfectly, further cementing that this is probably a CF issue.

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.

1 Like

Like I said previously, the 521 is apparently luck of the draw. My uptime monitor catches it about every 4th scan (which is done every 60 seconds).

What im saying is that for some reason or another cloudflare is having trouble with this domain. BUGS HAPPEN!!!

No reason to yell.

Bugs certainly happen and every couple of months people actually experience them here too. Every couple of months.

But again, there really is not more that I can say at this point. You dont even seem to have Rocket Loader enabled.

1 Like

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.

Im really not concerned with rocket loader at this point if CF can’t even make my site work properly due to what im sure is a really dumb bug.

Im also, tired of talking to end users who are unable to solve an issue within CF.

So unless someone has something constructive to add that would explain why this issue is happening, or you work for CF, I’m done reading comments.

Pardon me, I forgot my magic wand

1 Like

So you understand the reason I’m flagging this. I find it offensive that you a) assume I’ve not read everything. I have. b) You label me a “spammer”. That is most offensive.

1 Like

The API errors are still there.

I believe enough is enough.

1 Like

I agree, but the same applies to this thread in general.

Enough is enough, and I have had quite enough of people giving the same misguided feedback that we have already determined isn’t a factor.

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.

Anyhow, nothing justifies personal attacks.

1 Like