on the bright side my CORS settings are correct it seems

can anyone help me to answer it: https://discord.com/channels/595317990191398933/1104075421047336970

Oh I'm having the same issue today lmao, except a presigned putobject

I want to congratulate the @User team for shipping the bare minimum S3 compatibility. Making their R2 service almost unusable.

None of us are on the R2 team :p

but seriously, that isn't how you report issues... tagging employees being rude won't solve any problems.

If you have any useful and productive feedback, the R2 team actively follow this chat and would love to hear about your issues 🙂

^ just to confirm I am using a put request on the frontend

It seems that that the access-control-allow-origin isn’t being sent back, resulting in the issue, my cors is setup correctly though

Are you actually using a PUT? POST uploads aren’t supported at the moment (but should be soon). The easiest way to debug CORS issues is to inspect your outgoing request (the presigned PUT in your case) 1. Check if the Origin header of your outgoing PUT request matches one of the CORS origins you’ve set up 2. Another common source of problems is extra headers. If you see any extra headers in your outgoing requests, you’ll want to add them to your CORS policy as well. A quick way to debug is to allow “*” in AllowedHeaders and see if that fixes things. If it does, try replacing the wildcard with explicit headers you’re sending. I wouldn’t recommend leaving he wildcard in there permanently

Sorry, by “extra headers”, I mean additional headers you’re signing

I've been trying to figure out if there's a way to create API tokens that are only valid for a specific bucket in my account, but in the API tokens page it only seems to allow you to select "Workers R2 Storage" and "Edit/Read", without any further granularity. Is that accurate?

That is currently accurate, yes. Dane mentioned on Twitter that bucket scoped tokens would be coming this quarter, so hopefully we'll hear more about them soon.

As the title of the post, I’m using the PHP AWS SDK package to connect to CF R2. The connection is successful, and I’ve tried uploading and deleting a file, which both worked fine. However, when I try to copy a file from one location to another on R2, it doesn’t work. There are no errors or logs available. I'm using Laravel, so below is my code filesystem.php

'disks' => [
        's3' => [
            'driver' => 's3',
            'key' => env('R2_ACCESS_KEY_ID'),
            'secret' => env('R2_SECRET_ACCESS_KEY'),
            'region' => env('R2_DEFAULT_REGION'),
            'bucket' => env('R2_BUCKET'),
            'url' => env('R2_URL'),
            'endpoint' => env('R2_URL'),
        ],

    ],

Code try to copy an object

try {
            $s3 = Storage::disk('s3');
            $client = $s3->getDriver()->getAdapter();
            $client->getClient()->getCommand('CopyObject', [
                'Bucket' => 'thangnm',
                'Key'    => 'tmp/2023/5/5/c48df6b206a58d0360c55f3932260fd6.png',
                'CopySource' => 'p/2251799814000360/c48df6b206a58d0360c55f3932260fd6.png'
            ]);
        } catch (Throwable $ex) {
            var_dump($ex->getMessage());
        }

What could be causing this issue, and if someone has experienced this before, could you please guide me on how to resolve it? Thank you very much.

Hello Guys I was confussed with billing. If I will never exceed storage usage of 500GB in a month and I perform delete and upload and maintain the 500GB limit of total storage usage then what will be monthly cost ?

500GB-mont?

Like I will perform many upload and delete operation but overall storage usage will be under 500GB

It uses the peak storage usage everyday and averages that over the month

Please help out here. So I have moved alot of our data from S3 to using R2. Now everything is working, on django I have made a custom storage class, and some models are using it. While everything is working there is one small issue. I am trying to get the file size but when I try to get the file size I get the 400 head object error. And this happens on the endpoint url and not on the custom domain. How to force botocore to use the custom domain, else where its using custom domain as it is...so why here.

class R2Storage(S3Boto3Storage):   
    ------
    endpoint_url = settings.R2_ENDPOINT_URL
    ------

yes I am saying if that peak never cross the 500 gb then it means I have to pay for 500GB-month or below then this right?

yes

Ok thanks for the help, I have one more issue that is not related to R2 but related to Cloudflare ips , cause recently in my many Indian users reported that in their country cloudflare protected sites are taking too much time to load and sometimes not working. what you think about it?

I think India sometimes bans cloudflare ips not really anything anyone but the government can fix

yea it can be possible

is it normal for it to take 1.6 seconds to upload a 1.2mb file to r2 this is my code:? i posted this before in https://discord.com/channels/595317990191398933/846453104382836766/1103035968296075394 but got no response so im asking here too https://github.com/ascellahost/ascellav3/blob/master/src/api.ts#L126-L252

Have you benchmarked just the R2 code?

It looks like there's a DB and KV involved here which will definitely add overhead

yeah small files are still 700ms

the 2 db queries are prob 200ms each not sure about the kv one tho