Just a +1 on the 500 internal error when doing a PutObject. Weird coincidence as I was just trying out R2 for the first time so not sure if it's on me or still the outage.
Hey all, I'm seeing extremely degraded performance on R2. Nothing like the authentication errors, but videos stored there seem to just not want to load.
Hi, I just operated R2 bucket through the dashboard. I have linked a custom domain for public access and disabled it before. But its current Status is "Unknown". When I click "Enable the domain", "Access to Bucket" beside the "Status" column became "allowed" but at the top banner, "Public URL Access" is still "Not allowed", I can't get access to objects. When I click "Remove domain", it reports an error "We encountered an internal error. Please try again. (Code: 10001)" and nothing changed. But if i link a new domain, everything works fine including enable, disable and remove the new domain.
Learn how the location of data stored in R2 is determined and about the different available inputs that control the physical location where objects in …
Returns the Region the bucket resides in. You set the bucket's Region using the LocationConstraint request parameter in a CreateBucket request. For more information, see CreateBucket .
Interesting, they are gone. I had this exact thing this day for another bucket but did not think much about it. Last week I‘ve created two token sets for a new application and sent them out to the dev. They‘re also gone. And were definitely created without expiration
Hi, I am still encountering the "unauthorized" error when using R2. To provide some context, I have never experienced issues with the token in the past; I had been using it for a year without any problems. However, upon inspecting my logs, I noticed that the token stopped working at midnight (I suspect it might have expired). I went ahead and generated a new token, but I am still encountering the same error.