Cloudflare

I'm not familiar with peertube. But to make it short: Use the S3-endpoint for uploads and the custom domain for user access to play videos.

captura-de-pantalla-2023-03-01-a-las-16-21-54

In our config file we don´t see any anything to set custom domamin

```
[
  {
    "AllowedOrigins": [
      "*"
    ],
    "AllowedMethods": [
      "GET",
      "HEAD"
    ],
    "AllowedHeaders": [
      "*"
    ],
    "ExposeHeaders": [],
    "MaxAgeSeconds": 3600
  }
]
```

I've never seen a HEAD request for video delivery.

Is there any way we can authenticate requests to R2 that don't rely on a static long lived token? Something like OIDC federation would be awesome. Short of that, an API to rotate the secrets? Anything on the roadmap

I hope that something like this is on the roadmap. But most important would be bucket-scoped tokens.. 
Maybe you can roll something yourself by using the API to create and remove tokens on-fly.

Would still have a single point where you need a long-lived token but it surely limits the exposure of this token.

For some reason I had Cors issues with PeerTube and r2 until I added HEAD

I added this cors policy, and is not working neither

How have you set custom domain in production.yaml in peertube server?

Yeah, it’s working at https://urbanists.video

*posted this in the wrong channel woops, so posting it here correctly this time*
Anyone else getting a "The specified key does not exist. (Code: 10007)" when trying to view via the dashboard for something uploaded this morning?
https://www.bghddevelopment.com/cdn-cgi/imagedelivery/6pDiUJVklyFQ8zDPATvmkQ/ed4ad625-0673-4149-85b4-4f7c8ef45000/public
The files exist but then clicking any of them send the error above:
https://www.bghddevelopment.com/cdn-cgi/imagedelivery/6pDiUJVklyFQ8zDPATvmkQ/2f7d9189-b5a2-4d06-a74d-7d1b876f6500/public

Okay should work now! Sorry about the downtime

All good! Working fine. <@136415155016826880>

Yes. Just fyi there’s two major issues with 5.0.1: ACL update nulling out objects, and uploads >500mb not respecting range requests https://github.com/Chocobozzz/PeerTube/issues/5646

Could you please let me know where have you configured custom domain in production.yaml?

I tried before setting custom domain in base url

Perhaps becuase of the head in cors thing

Quick update to this, seems to send for ANY uploaded file in the dashboard regardless of when I uploaded it. If I had to guess this is possibly related to the dashboard API error status page that was happening earlier, though that was marked resolved.