KThose both work for me, so my guess is you just need to purge your Cloudflare cache
KBut also: You did not upload this file with the correct
https://img.poisondrop.ru/upload/item_sku/img/desktop/125685AEyXoBOTNIUu.jpeg
Content-Typeapplication/octet-streamhttps://img.poisondrop.ru/upload/item_sku/img/desktop/125685AEyXoBOTNIUu.jpeg
AThanks a lot! I will investigate the issue
CCaused by: java.lang.Throwable: Acquire operation took longer than the configured maximum time. This indicates that a request cannot get a connection from the pool within the specified maximum time. This can be due to high request rate.
Consider taking any of the following actions to mitigate the issue: increase max connections, increase acquire timeout, or slowing the request rate.
Increasing the max connections can increase client throughput (unless the network interface is already fully utilized), but can eventually start to hit operation system limitations on the number of file descriptors used by the process. If you already are fully utilizing your network interface or cannot further increase your connection count, increasing the acquire timeout gives extra time for requests to acquire a connection before timing out. If the connections doesn't free up, the subsequent requests will still timeout.
If the above mechanisms are not able to fix the issue, try smoothing out your requests so that large traffic bursts cannot overload the client, being more efficient with the number of times you need to call AWS, or by increasing the number of hosts sending requests.
its possible that fix?
Consider taking any of the following actions to mitigate the issue: increase max connections, increase acquire timeout, or slowing the request rate.
Increasing the max connections can increase client throughput (unless the network interface is already fully utilized), but can eventually start to hit operation system limitations on the number of file descriptors used by the process. If you already are fully utilizing your network interface or cannot further increase your connection count, increasing the acquire timeout gives extra time for requests to acquire a connection before timing out. If the connections doesn't free up, the subsequent requests will still timeout.
If the above mechanisms are not able to fix the issue, try smoothing out your requests so that large traffic bursts cannot overload the client, being more efficient with the number of times you need to call AWS, or by increasing the number of hosts sending requests.
its possible that fix?
SWe’re looking at storage tiers in general currently, but the “intelligent” bit is probably going to take a while to land.
CClear!! Thanks for letting me know 
JI need some help -- I'm trying to generate a presigned upload URL with R2 and I keep getting this error:
"The request signature we calculated does not match the signature you provided. Check your secret access key and signing method."
My go code is as follows:
func CreatePreSignedUploadURLR2() (string, error) {
iSess, err := session.NewSession(cloudflareR2Config)
if err != nil {
return "", err
}
sess := session.Must(iSess, nil)
svc := s3.New(sess)
r, := svc.PutObjectRequest(&s3.PutObjectInput{
ACL: aws.String("public-read"),
Bucket: aws.String("bucket-name"),
Key: aws.String("file.png"),
})
url, err := r.Presign(10 * time.Hour)
return url, err
}
I have similar code where I use the same R2 config and upload files like this and it works fine:
uploader := s3manager.NewUploader(sess)
, err = uploader.Upload(&s3manager.UploadInput{
ACL: aws.String("public-read"),
Bucket: bucket,
Key: key,
Body: bytes.NewReader(file),
ContentType: aws.String(ContentType),
})
Any ideas what I could be doing wrong?
This is what the pre-signed URL looks like:
https://accountid.r2.cloudflarestorage.com/bucket-name/file.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=b4053e91cf47c2e60fc0913379392611%2F20230815%2Fauto%2Fs3%2Faws4_request&X-Amz-Date=20230815T005722Z&X-Amz-Expires=36000&X-Amz-SignedHeaders=host%3Bx-amz-acl&X-Amz-Signature=cdfeef86ea408de67dfe70ce89444dc6ad5957fcd938507f0cd0d672679fccbf
"The request signature we calculated does not match the signature you provided. Check your secret access key and signing method."
My go code is as follows:
func CreatePreSignedUploadURLR2() (string, error) {
iSess, err := session.NewSession(cloudflareR2Config)
if err != nil {
return "", err
}
sess := session.Must(iSess, nil)
svc := s3.New(sess)
r, := svc.PutObjectRequest(&s3.PutObjectInput{
ACL: aws.String("public-read"),
Bucket: aws.String("bucket-name"),
Key: aws.String("file.png"),
})
url, err := r.Presign(10 * time.Hour)
return url, err
}
I have similar code where I use the same R2 config and upload files like this and it works fine:
uploader := s3manager.NewUploader(sess)
, err = uploader.Upload(&s3manager.UploadInput{
ACL: aws.String("public-read"),
Bucket: bucket,
Key: key,
Body: bytes.NewReader(file),
ContentType: aws.String(ContentType),
})
Any ideas what I could be doing wrong?
This is what the pre-signed URL looks like:
https://accountid.r2.cloudflarestorage.com/bucket-name/file.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=b4053e91cf47c2e60fc0913379392611%2F20230815%2Fauto%2Fs3%2Faws4_request&X-Amz-Date=20230815T005722Z&X-Amz-Expires=36000&X-Amz-SignedHeaders=host%3Bx-amz-acl&X-Amz-Signature=cdfeef86ea408de67dfe70ce89444dc6ad5957fcd938507f0cd0d672679fccbf
JThis is what the token permission looks like as well...so it should work for this
KYou add an R2 subdomain in the settings for your bucket
SYou need to link to the file, for example, ABC.xyz.com/example.png
SDo you mind DMing me the link so I can test it
SMight be a cache issue
SDo you have a DNS record for it?
SYep tested it
SIt works for me
SSo check again and if it doesn't work then try refreshing your browser's cache
SThe direct link should show up as this
SYes the link you sent me works
STry using mobile data
SThat might be an issue
SYeah it was a DNS propagation issue then
CIf I put the CDN in front of the bucket, does it caches the images to decrease the amount of reads? Or every single call is threated as a read
EIt caches the images and decreases the amount of reads
CPerfect! Thanks!
KAnyone can help me?
I cannot connect R2 to the domain.
Only the
Thanks
I cannot connect R2 to the domain.
Only the
dl1.tanphongthan.comThanks
KI try
removere-addErrorThe response i got as the bellow.
EK@Erisa | Support Engineer Thank for your response.
It can be access, but the response is not corrected. The very old version of data was returned.
It can be access, but the response is not corrected. The very old version of data was returned.
Ktry https://dl1.tanphongthan.com/version.json vs https://dl2.tanphongthan.com/version.json response and compare it, you will see what I said
Cbro the music is like 24kbps, can't get any lower than that.
II just tried to purge my whole bucket with 
rclonerclone purge r2-updates-prod:r2-updates-prod/I got internal server errors while trying to push to it while it was in this 'deleted' state. It also had a domain connected, which is down now and had some issues, had to reconnect it, but taking a while now to update.
CHey there a quick (dumb) question about R2. Is it possible to progrmatically create temporary access tokens that allow clients to upload directly to buckets?
YWe want to see the location of our buckets, is this possible now?
YWe asked a couple of months ago but it wasn't possible. Now we noticed the location hints
KR2 supports GetBucketLocation via the S3 API
Ythanks, so no way to see it in the UI right?