They have renamed a bunch of storage related parameters which will break existing installations. So, we have to make a major release.

@AartJansen Good idea, I will bump the default memory limit.

@mdc773 said in Regenerate video thumbnails: i don't fully understand max upload part On S3 compatible storage, you can upload large files, like 5TB. It would be infeasible to upload such large files in a single shot. So, they have APIs to upload files in "parts". Like you upload 10k parts of 5GB each for example to get to 5TB. The number of parts and size of each part depends on the S3 storage. Usually, I leave upload part size to something like 10MB-50MB. There is actually nothing wrong with 100MB part size, but for some reason peertube is complaining about it.

I wish It could be used like for the LAMP containers, apache handling the file access, I'm using it a lot in that context and it works perfectly ! but yeah I get it

Just to say, I think the issue here was that the server just didn't have enough RAM nor CPU in order to process the large video someone tried to upload. Things have been working nicely since moving my Cloudron to a dedicated server.

It turns out that the install source folder name needs to be the exact same as destination name inside the plug-in. My folder name plugin-v1.1.0 was the issue. Thanks

@girish noted

Turns out the Plug-in "Auto import YTB" was the culprit! Thanks a lot for the follow up!

@girish @nebulon https://github.com/Chocobozzz/PeerTube/releases/tag/v5.2.0

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).

So the problem was in the VOD transcoding settings. I also had WebTorrent transcoding enabled and the videos are then saved 2x. Thanks for the help, I think the thread is solved VOD transcoding

@awnzky ah, this was already removed - https://git.cloudron.io/cloudron/peertube-app/-/commit/ec2620275ec46a67697ba1d1d6e7722944f21b8b. I will make a new package.

@robi said in What RTMP Ports to use if I want to use both PeerTube and Owncast?: Then it may be time to ask for a message to not change the peertube port during install/config just like with jitsi, if you do, it won't work. I think that is a good thing to suggest. It will work, if the default port is not selected, but not all of its functionality (namely the livestreaming ability) would be available, as far as I understand. I think it would be worth mentioning upstream to frama too. I don't know why they hardcoded it. Maybe it is a temporary thing.

@imc67 You could use the thread tools at the top right of the thread to mark this as a question and then thread solved.

Glad it got sorted out. Those plugins in so many apps are often at fault unfortunately as many apps under much development keep changing their internals and plugin interfaces.

Also, for those that don't know what HLS is (I didn't prior to running into this issue), here's a link to get you started with "HTTP Live Streaming": **Adaptability ** To enable a player to adapt to the bandwidth of the network, the original video is encoded in several distinct quality levels. The server serves an index, called a "master playlist", of these encodings, called "variant streams". The player can then choose between the variant streams during playback, changing back and forth seamlessly as network conditions change. https://en.wikipedia.org/wiki/HTTP_Live_Streaming#Adaptability

We have pushed a change to fix this for the next release: https://git.cloudron.io/cloudron/box/-/commit/84ca85b315f75870a94abd8fdf749b43f412f721

@ncamacho97 this is not Reclaim Cloud btw as you say here. This is Cloudron. Are you using cloudron or something else?

@jdaviescoates Yes the plugin works just fine for me ! you can see it at work here : ukrainewararchive.eu/