HTTP 403 Errors + IP Restrictions on Forum

Hi!
So, this bug started for me yesterday. I try and leave forum posts, and comments and I get “error 403”
image

“drafts offline” is also a constant error.
Steps to reproduce:

  • Make a topic, comment, anything.
  • You SHOULD get a warning saying “Drafts Offline” or “403 error.”
    Also, check the second comment from me.

Browser: MS Edge (2020), up to date
System Info:

  • Windows 11 Pro Dev Release (22499.1000 (rs_prerelease))
  • NVIDIA GeForce GTX 1660 Super
  • Intel Core i5 @ 4.15GHz Clock
  • 24gb Memory
  • 4TB SSD, 1TB HDD, 3TB External Backup HDD
  • Intel Wifi AX200
  • Generic LAN Adapter
4 Likes

Both of these started around the same time, probably related. Different error messages though.
DevForum Acting Weird 2

1 Like

I got all the errors today, still a constant issue.



image

my devforum was just down, and it just got back on
image
im not sure why

1 Like

I’m noticing a pattern here, Were all on W11? I kept getting this issue as well throughout the day, If you don’t mind me asking what OS were you guys on?

  • Windows 7
  • Windows 8
  • Windows 10
  • Windows 11

0 voters

This is occurring on ALL OS systems. It’s also confirmed to be happening on iOS and OSX. Check the other thread for this.

2 Likes

So now this happens loading summary.json.

Hi, is this still happening?

It now seems to happen in this area.
Can’t Access devforum.roblox.com Directly - Forum Help / Forum Bugs - DevForum | Roblox

So you are no longer seeing the 403 error discussed in this thread as much as before?

No, t’s just the direct accessing.

1 Like

Following up, has this been resolved for you now?

Yes.

1 Like

This topic was automatically closed after 6 days. New replies are no longer allowed.

I reopened this, because I’m having a very similar, if not the same issue on an alt.

I have no problems on Edge, but Firefox will often result in this:
image

As you can see in my previous replies, I think its specifically @discobot now maybe?

The page on which it occurs and the error itself are clearly very different from first post. (403 vs 502, no pop-up error) You should file a new bug report with all required details.

1 Like