Replying to @pegasusepsilon
Sorry to hear If you could, can you try another browser and/or device to see if you continue running into this issue? I'd also suggest clearing your cache and cookies! ^BT

Jan 22, 2023 · 4:39 PM UTC

1
19
Replying to @MojangSupport
It seems to be a transient and fairly rare failure. If you have a server farm back there running the site, I suspect one of the many is misconfigured and serving 403 all day instead of 200 like it should. Good luck to you.