if its resolved theres probably not much point me looking into it

yea

sorry about the ping

no problemo

Does R2 have version history for files?

Nope, not yet

I solved the problem 🙂

Thing is that I was restarting server with sudo systemctl restart nginx and this command wasn´t making get effect the new changes

I was testing and rebooting anytime I did any changes in production file until I made it work

Thanks

Is anyone getting upload stuck with videos larger than 200mb in peertube through R2?

Set max_upload_part 100 or 200mb max

is there going to be support natively with custom domains and brotli (br) right now i get this file.js.br This can happen if build compression was enabled but web server hosting the content was misconfigured to not serve the file with HTTP Response Header "Content-Encoding: br" present. Check browser Console and Devtools Network tab to debug. with my custom Worker and adding content-encoding it works fine -> with custom domains it appears no support today

I changed it to 100MB. The problems remains, I´m trying to upload a video of 211mb, and is always getting stuck at 9.78%, no more no less

is it possible to get any stats or analytics on the individual objects in a bucket? or can you only see per-bucket aggregate statistics?

You probably can with the GraphQL API but that’s just a guess

The thing is that when I installed peertube instances for testing without having the domain in cloudflare, I never had an issue uploading large files. Whenever I mapped the domain to cloudflare is when I always have this issues while uploading...so perhaps is not an issue from peertube but from cloudflare? Not sure yet

I find out that Cloudflare has an upload limit of 100mb in their free and pro plans, 200mb for business and 500mb for enterprise...perhaps this is the reason. However I just unproxy my domain and still is not uploading videos larger than 200mb

using custom domains with R2 -> is there a way to pass cache-control: no-transform to prevent compression?

i attempted a CF header modification and it applied the no-transform but content-encoding still occurred today i use a CF worker in front of an R2 bucket to do this but trying to avoid a CF worker

what if you put a request header modification to overwrite the accept-encoding header?

to make it think the client can't support it

Aww let me try that

cant change it per CF

sad

Yup switched back to cf worker for everything and sent all my feedback to cf for where direct linking with custom domains is lacking. It’s real close but not there yet Thanks all for the help!

is cloudflare still accepting performance items? for example obtaining a file is 50% slower than Vercel for example

What do you mean by that? Vercel isn't an S3 type provider 🤔

well true i should say compared to google storage behind scenes i know this runs on AWS anyone else notice a difference in speed?

Does cache private reserve work for worker + r2 or do I need to code in cache on my worker?