@Chaika this page states issues with Workers KV and pages. Is the R2 issue also included in there or

A

alexandernstOP•10/30/23, 8:13 PM

then why isn't the dashboard of r2 loading?

K

kev-ac•10/30/23, 8:13 PM

Just checked, all my pages sites return 500 right now. I imagine some on-call engineers running in a circle right now.

C

Chaika•10/30/23, 8:13 PM

hopefully not running in circles and more fixing lol

Aalexandernst @Chaika this page states issues with Workers KV and pages. Is the R2 issue also ...

C

Chaika•10/30/23, 8:14 PM

Dashboard is included in that incident, but not in the name of it

C

Chaika•10/30/23, 8:14 PM

This incident affects: Cloudflare Sites and Services (Access, Dashboard, Pages, Workers KV).

SShervanator same here our r2 bucket is down, and can't access the dashboard

E

ElGato•10/30/23, 8:14 PM

same here

S

Sid•10/30/23, 8:15 PM

Your buckets should continue working, but the dashboard would be down currently.

E

ElGato•10/30/23, 8:22 PM

ah seems to be back online

E

ElGato•10/30/23, 8:22 PM

or almost

SShervanator https://milkshake.app is just a static site on a bucket, the whole site has gone...

U

Unsmart•10/30/23, 8:27 PM

Do you use KV at all on that? Afaik R2 was not at all affected from this incident

S

siliconsjang•10/31/23, 1:51 AM

Seems like https://r2.dev has been blocked AGAIN by Korean Goverment

S

siliconsjang•10/31/23, 1:53 AM

and I asked for the reason why did they blocked it and if there is any minutes of meetings of the website r2.dev to the goverment, they have answered me (It took 1 month) with the answer:

S

siliconsjang•10/31/23, 1:53 AM

The information is judged to be likely to cause significant disruption to the safety of the country or society, such as being targeted by a cyberattack, if disclosed, or there is a substantial reason to believe that disclosure would significantly impair the fair performance of business.

The information is judged to be likely to cause significant disruption to the safety of the country or society, such as being targeted by a cyberattack, if disclosed, or there is a substantial reason to believe that disclosure would significantly impair the fair performance of business.

The information is judged to be likely to cause significant disruption to the safety of the country or society, such as being targeted by a cyberattack, if disclosed, or there is a substantial reason to believe that disclosure would significantly impair the fair performance of business.

The information is judged to be likely to cause significant disruption to the safety of the country or society, such as being targeted by a cyberattack, if disclosed, or there is a substantial reason to believe that disclosure would significantly impair the fair performance of business.

S

siliconsjang•10/31/23, 1:55 AM

so anyway this means: Cloudflare R2 is the malicious website to the Korean Government, so we blocked it to Koreans

S

siliconsjang•10/31/23, 1:57 AM

yup, it can be used for that purpose, but I asked the reason why they blocked the entire R2.DEV including all subdomains. and they answered that. (however they are not blocking aws)

S

siliconsjang•10/31/23, 2:03 AM

yes. in that case it will be very serious. I just wanted to let Cloudflare know that r2.dev is the malicious thing at least Korean Gov knows.

E

EyyubovKamran•10/31/23, 7:09 AM

Hi all, can anybody help me with adding custom domain to R2. It stucks with status "Unknown"

G

goofysystem•11/1/23, 6:00 AM

what is the url to use when using local dev with R2? Using

https://${accountId}.r2.cloudflarestorage.com/${bucketName}/${key}

https://${accountId}.r2.cloudflarestorage.com/${bucketName}/${key}

https://${accountId}.r2.cloudflarestorage.com/${bucketName}/${key}

https://${accountId}.r2.cloudflarestorage.com/${bucketName}/${key} has not worked for me. When using

wrangler pages dev

wrangler pages dev

I get broken images in dev after successful uploads, so I have to deploy it and test with the public r2.dev url to see the image uploads working. Any help would be greatly appreciated.

R

Raiyan•11/1/23, 8:16 AM

?r2-roadmap

F

Flare•11/1/23, 8:16 AM

These features are now available!!

Object Lifecycles: https://developers.cloudflare.com/r2/buckets/object-lifecycles/
Public buckets, with custom domains: https://developers.cloudflare.com/r2/data-access/public-buckets/#enable-public-access-for-your-bucket
Presigned URLs in the S3-compatible API
Location Hints (e.g. 'EU')
Object Migration (S3->R2)

A

avocade•11/1/23, 10:28 AM

Having some trouble enabling Sippy for my new EU-buckets… I'm just getting a "The specified bucket does not exist." error.

K

kian•11/1/23, 10:33 AM

Are you hitting the EU subdomain?

K

kian•11/1/23, 10:33 AM

i.e

accountid.eu.r2.cloudflarestorage.com

accountid.eu.r2.cloudflarestorage.com

accountid.eu.r2.cloudflarestorage.com

accountid.eu.r2.cloudflarestorage.com

A

avocade•11/1/23, 10:40 AM

This is just for enabling sippy

curl -X PUT https://api.cloudflare.com/client/v4/accounts/{account_id}/r2/buckets/{bucket_name}/sippy \
--header "Authorization: Bearer <API_TOKEN>" \
--data '{"provider": "AWS", "bucket": "<AWS_BUCKET_NAME>", "zone": "<AWS_REGION>","key_id": "<AWS_ACCESS_KEY_ID>", "access_key":"<AWS_SECRET_ACCESS_KEY>", "r2_key_id": "<R2_ACCESS_KEY_ID>", "r2_access_key": "<R2_SECRET_ACCESS_KEY>"}'

curl -X PUT https://api.cloudflare.com/client/v4/accounts/{account_id}/r2/buckets/{bucket_name}/sippy \
--header "Authorization: Bearer <API_TOKEN>" \
--data '{"provider": "AWS", "bucket": "<AWS_BUCKET_NAME>", "zone": "<AWS_REGION>","key_id": "<AWS_ACCESS_KEY_ID>", "access_key":"<AWS_SECRET_ACCESS_KEY>", "r2_key_id": "<R2_ACCESS_KEY_ID>", "r2_access_key": "<R2_SECRET_ACCESS_KEY>"}'

curl -X PUT https://api.cloudflare.com/client/v4/accounts/{account_id}/r2/buckets/{bucket_name}/sippy \
--header "Authorization: Bearer <API_TOKEN>" \
--data '{"provider": "AWS", "bucket": "<AWS_BUCKET_NAME>", "zone": "<AWS_REGION>","key_id": "<AWS_ACCESS_KEY_ID>", "access_key":"<AWS_SECRET_ACCESS_KEY>", "r2_key_id": "<R2_ACCESS_KEY_ID>", "r2_access_key": "<R2_SECRET_ACCESS_KEY>"}'

curl -X PUT https://api.cloudflare.com/client/v4/accounts/{account_id}/r2/buckets/{bucket_name}/sippy \
--header "Authorization: Bearer <API_TOKEN>" \
--data '{"provider": "AWS", "bucket": "<AWS_BUCKET_NAME>", "zone": "<AWS_REGION>","key_id": "<AWS_ACCESS_KEY_ID>", "access_key":"<AWS_SECRET_ACCESS_KEY>", "r2_key_id": "<R2_ACCESS_KEY_ID>", "r2_access_key": "<R2_SECRET_ACCESS_KEY>"}'

A

avocade•11/1/23, 10:40 AM

Is there a EU-specific modifier somewhere that's not in the docs?

A

avocade•11/1/23, 10:41 AM

All the credentials seem to work at least, verified by f-in them up and getting

invalid upstream creds

invalid upstream creds

invalid upstream creds

invalid upstream creds etc.

K

kian•11/1/23, 10:41 AM

Ohh, Sippy

A

avocade•11/1/23, 10:41 AM

Not great error msgs, so I guess "missing bucket" could mean that the S3 bucket doesn't exist, but it surely does (and the IAM has access).

K

kian•11/1/23, 10:43 AM

Try adding

cf-r2-jurisdiction: eu

cf-r2-jurisdiction: eu

cf-r2-jurisdiction: eu

cf-r2-jurisdiction: eu as a request header.

A

avocade•11/1/23, 10:44 AM

Yep, verified that this is EU-bucket specific: I created a regular bucket and now it worked fine enabling Sippy… For f's sake sippy should work with both bucket types, or at least the docs should mention that EU-buckets don't work in the beta

A

avocade•11/1/23, 10:44 AM

@kian thanks I'll try that!

K

kian•11/1/23, 10:44 AM

Lemme know if it works - the rest of the API uses it, but Sippy might not be hooked up to it.

A

avocade•11/1/23, 10:45 AM

@kian That did it! plz tell the CF peeps to update their docs with this nugget of wisdom

and thanks.

K

kian•11/1/23, 10:45 AM

cc @Sid | R2

A

avocade•11/1/23, 10:45 AM

Yo @Sid | R2

A

avocade•11/1/23, 10:46 AM

Ok will do

K

kian•11/1/23, 10:48 AM

https://github.com/cloudflare/cloudflare-docs/pull/11594

K

kian•11/1/23, 10:49 AM

The docs cover the API but the dashboard needs to be updated to include EU in the bucket list and whatnot

A

avocade•11/1/23, 10:49 AM

Boom: https://github.com/cloudflare/cloudflare-docs/issues/11595

GitHub

R2 buckets in EU needs additional header flag to enable sippy (and ...

Which Cloudflare product does this pertain to? R2 Existing documentation URL(s) https://developers.cloudflare.com/r2/data-migration/sippy/ https://blog.cloudflare.com/sippy-incremental-migration-s3...

A

avocade•11/1/23, 10:49 AM

D

duffann•11/1/23, 11:44 AM

Hello, aws js example has this code inside, isn't it a problem because it can be seen by any client?:
const s3 = new S3({
endpoint:

https://${accountid}.r2.cloudflarestorage.com

https://${accountid}.r2.cloudflarestorage.com

https://${accountid}.r2.cloudflarestorage.com

https://${accountid}.r2.cloudflarestorage.com,
accessKeyId:

${access_key_id}

${access_key_id}

${access_key_id}

${access_key_id},
secretAccessKey:

${access_key_secret}

${access_key_secret}

${access_key_secret}

${access_key_secret},
signatureVersion: 'v4',
});

C

ChoboAvenger•11/1/23, 12:05 PM

Hi, I'm adding a file from my bitbucket repo to my R2 bucket using wrangler in a pipeline. The line in the pipeline which adds it is this:

npx wrangler r2 object put bucket-name/$CLOUDFLARE_BUCKET_TOKEN object-cache-latest.zip --file object-cache-latest.zip

Everything works great except, the file in the bucket is named some random string of numbers and characters instead of "object-cache-latest.zip". The file itself is the correct file, and it is going to the correct bucket, only the filename is wrong.

Why is this happening? How can I fix it?

CChoboAvenger Hi, I'm adding a file from my bitbucket repo to my R2 bucket using wrangler in a...

H

Hello, I’m Allie!•11/1/23, 12:16 PM

It should be

$ wrangler r2 object put bucket-name/object-cache-latest.zip --file object-cache-latest.zip

$ wrangler r2 object put bucket-name/object-cache-latest.zip --file object-cache-latest.zip

$ wrangler r2 object put bucket-name/object-cache-latest.zip --file object-cache-latest.zip

$ wrangler r2 object put bucket-name/object-cache-latest.zip --file object-cache-latest.zip

@Chaika this page states issues with Workers KV and pages. Is the R2 issue also included in there or

Similar Threads

Similar Threads

Similar Threads