500 Error from Cloudflare's R2 S3 Api
Hi, can someone who works at cloudflare help, or point me to somehow i can contact someone who works at cloudflare? I've been getting 500 errors when trying to use the R2 S3 API. This started at the beginning of the month and hasn't changed. It was working for me before with no issues, and i didn't change anything. It just started giving me 500 errors. I can see the API hits in the Metrics tab of the web interface but nothing gets stored or retrieved.
I have tried creating a new bucket, and also creating new R2 API keys. Still no change
4 Replies
thanks, i did and got crickets 🙂
There is some R2 people that monitor that channel, but none that watch this.
It would probably be helpful to include a few more things:
This is constant, not just a few errors, right? Every request fails
Your API Key doesn't have anything special on it, no expiration, no IP Filtering, etc? Personally I've had issues in the past using Client IP Filtering.
You're using rclone or what specific tool? Including a rayid if you can might help
Creating things from the dashboard/etc works fine?
thanks, ok i'll try posting there with more specifics
oh and account id (not sensitive, right side of R2) would probably be smart to add as well, it'd be the first thing they ask for
That's strange though, if it's for an entire account across all buckets sounds like something borked on setup or something. If they don't reply, we could try going the ticket route as well
Hmm the two apps you use are interesting. The S3 compat works well, but sometimes some clients implement it lazily which AWS itself accepts but R2 is more strict on. I believe Cyberduck was confirmed to be working before, but might be worth trying something that R2 offically supports like rclone or @aws-sdk/client-s3/aws-sdk