522 errors

[gliengul]

Misread Yak's earlier post: putting a random query string on the direct image link does actually load the image.
Canada, Residential, Cable, Shared with a user who is unlikely to use FA. Rebooted the modem once since this issue started just to make sure it wasn't buffer shenanigans. No VPN, No Proxy.

Prone to loading large numbers of tabs on FA (especially from the watch list), was under the impression that Firefox pipelined these requests in a way to avoid killing servers.

 

[kiroku]

I really wish I knew more about networking. All my experience is mostly user-side applications.
I have no idea why some users would be locked out whereas others are given free reign.
It seems to be that way if everyone who used a VPN changed their location to a different country.

But still. What are the mechanics behind it? I'm really curious.

So this issue is the CDN or "Content/Cloud delivery network." A CDN is basically redundant servers across different regions/parts of the world that host all the content that you see on the main site (in this case mostly images). CDN is used to make a website load fast for the user no matter where they are in the world. So if I'm in Asia and I load an image, I may be pulling the image from an server located physically closer to me in Asia whereas if you live in Oregon you might be loading that same image from a server in California.

And this error we see now makes perfect sense. The loading issue is server specific so that's why some users can see images just fine while others cannot. Depending on the CDN server it's pulling from, some seem to be having caching issues.

 

[Toby_Morpheus]

So this issue is the CDN or "Content/Cloud delivery network." A CDN is basically redundant servers across different regions/parts of the world that host all the content that you see on the main site (in this case mostly images). CDN is used to make a website load fast for the user no matter where they are in the world. So if I'm in Asia and I load an image, I may be pulling the image from an server located physically closer to me in Asia whereas if you live in Oregon you might be loading that same image from a server in California.

And this error we see now makes perfect sense. The loading issue is server specific so that's why some users can see images just fine while others cannot. Depending on the CDN server it's pulling from, some seem to be having caching issues.

Okay. I thought it might have been something like that, but I've never dealt with that kind of networking before.
Any server I've ever run has been from a single location, generally on the other side of my big ol computer table.

Thanks for an answer. I'll keep it filed away.

 

[ElCid]

Hope I'm not jinxing myself here, but it seems to have finally fixed itself on my end for now.

 

[trionicb]

Yes, Yak is looking into it.

Any idea if they're working on a fix for this? Like, an actual one that'll fix everything going wrong?

 

[ElCid]

Yes, Yak is looking into it.

Whatever's been done, it seems to have worked so far.

 

[trionicb]

Yeap, same here. Things appear back to normal. Thanks Yak and company!

 

[yak]

Thank you all for the feedback. The issue has been with Cloudflare CDN, which they confirmed has now been fixed.