Wiki.roblox.com is giving 403 errors

How come these two sound very different from each other? Surely if there are enough details known that cause the issue it can be reproduced or at least diagnosed.

MisterNeutron has been on vacation for the past week, so he might not fully be in the loop on the backend situation.

And an other week has passed, still having issues :frowning:

2 Likes

At this point, for me at least, refreshing up to 10 times makes it go away. It’s still obscenely annoying.

If the wiki gets DDoSed 4 times a day I’d still be able to access it more often than with all this DDoS protection.

2 Likes

Unforunately it really is ringing hollow at this point, it’s been 1 year long and now we deserve an response to what is being done, what is being looked into because the excuse of

We are looking into it, looked into, looking into etc

Is really disappointing after 2 months we are still only “looking into it” I really hope the wiki gets fixed within a matter of days now because this is unfair and crippling developers. We as developers should be provided more information to what is happening and what’s being done about it and if any changes have even been made and it shouldn’t be covered/plastered over with “looking into it, we are looking it” because it seems to heavily increasingly become a unhealthily norm now :frowning:

1 Like

This post I made last November still holds true to this day. The attitude of more ddos protection == more better causes the wiki to be unreachable most of the time. I’m just going to call the wiki situation gross incompetence at this point, its been inconveniencing developers for over a year now.

1 Like

Thank you on behalf of the entire community for being the squeaky wheel. I escalated this issue again, and shared with our team this thread to help them understand the urgency.

As a result, we made changes today that should address the 403 problem users were having. My understanding is that we also confirmed with someone in the community who was experiencing this problem that the issue is indeed fixed. If you have a different experience please let me know in this thread so that we can further investigate.

Let me renew my apologies that it has taken this long to address. We will strive to do better in the future.

8 Likes

And it’s back! On the blog right now…

@MisterNeutron

2 Likes