PeerTube + S3?

[doodlemania2]

I've seen a couple of nibbles here and there regarding getting PeerTube up and going on S3 backend. A bit stuck, however (it's probably just me).
In addition to the default settings, in production.yaml, I set everything up from what I could find in the docs:

object_storage:
  enabled: true
  endpoint: 'myendpoint'
  credentials:
    access_key_id: 'myaccesskey'
    secret_access_key: 'mysecret'
  max_upload_part: 2GB
  videos:
    bucket_name: 'peertube'
    prefix: 'videos/'
  # Use the same bucket as for webtorrent videos but with a different prefix
  streaming_playlists:
    bucket_name: 'peertube'
    prefix: 'streaming-playlists/'

Now, when I upload a video, it does transcribe and it does move the file from local storage to S3 endpoint - huzzah! But, when I go to watch the video, it just sits there and spins. There's some delightful logs stuff about "hash mismatch" and then the whole application comes crashing down. Sad.

Anyone successfully done this?

[robi]

Is your bucket publicly accessible for https?

[jdaviescoates]

@doodlemania2 said in PeerTube + S3?:

Anyone successfully done this?

Yes, although I struggled for a good while too!

Seems this is what eventually got it working for me:

https://forum.cloudron.io/post/60616

[doodlemania2]

@robi yes, but will revalidate!

[doodlemania2]

@jdaviescoates oh perfect! let me follow these instructions and revert back. I think my only delta from you is that I'm using iDrive but that should be just a simple tweak.

[doodlemania2]

Well, I gave the scaleway examples a try. Looks like iDrive is much more simple (for better or worse). I set the whole region to "share everything with all origins." Still no dice, so I think there must be something else afoot. Will try to catch some more detailed logs and see if I can get something going upstream with the peertube folks. Will report back if I hear anything!

[doodlemania2]

Ohhh, could be my proxy servers not supporting bye-range requests. Hrm, that could be fun!

[doodlemania2]

Confirmed it was CloudFlare doing cloudflary things. Up and going now, but would prefer to get Cloudflare back in front of it. Will keep tinkering, maybe there's a special rule or something (using CloudFlare proxy for safety).