Cloudserver Brazil ban

[loramin]

Originally Posted by LongTallMatt [You must be logged in to view images. Log in or Register.]

I also cannot upload auction tracker pricing. Same error. US, both VPN to New Jersey and no VPN.

Yeah, it's a corollary of this:

Originally Posted by loramin [You must be logged in to view images. Log in or Register.]

This is the same error the wiki gets when you try to edit (or even preview an edit) on certain pages (eg. https://wiki.project1999.com/index.p...&action=submit).

What CloudFlare (aka CloudFront, aka CloudFormation ... I'll just call it CF) does is make a copy of a webpage, so when someone visits our wiki, CF can save the wiki some effort by displaying its copy (and then CF watches the original, and updates its copy when the original changes). This form of caching is a common web optimization practice, and it happens behind the scenes on tons of websites you use (you just never notice it).

However, anything dynamic (like editing pages, or providing auction data) can't be cached. If things were working properly, CF wouldn't try to get involved, and would just let requests for those things through to the wiki server. It actually still does that, for some pages.

But for dynamic pages and some static pages, it's not working, and that's why we get the errors. I can't really explain why some pages work and others don't without knowing more about Rogean's architecture, but the long story short version is that we need Rogean to fix things, and then we'll stop seeing those error pages.

[LongTallMatt]

Originally Posted by loramin [You must be logged in to view images. Log in or Register.]

Yeah, it's a corollary of this:



What CloudFlare (aka CloudFront, aka CloudFormation ... I'll just call it CF) does is make a copy of a webpage, so when someone visits our wiki, CF can save the wiki some effort by displaying its copy (and then CF watches the original, and updates its copy when the original changes). This form of caching is a common web optimization practice, and it happens behind the scenes on tons of websites you use (you just never notice it).

However, anything dynamic (like editing pages, or providing auction data) can't be cached. If things were working properly, CF wouldn't try to get involved, and would just let requests for those things through to the wiki server. It actually still does that, for some pages.

But for dynamic pages and some static pages, it's not working, and that's why we get the errors. I can't really explain why some pages work and others don't without knowing more about Rogean's architecture, but the long story short version is that we need Rogean to fix things, and then we'll stop seeing those error pages.

So no ETA on the fix?

[boomslang]

Originally Posted by LongTallMatt [You must be logged in to view images. Log in or Register.]

So no ETA on the fix?

Need Rogean / staff to acknowledge its broken first.