okay I found the solution :
In Postgres, you have to set "storage" to "0" (in videoStreamingPlaylist) with the video id

I think I figured it out. Apparently there's a really low default if you don't explicitly set a max size via client_max_body_size. Setting that explicitly seemed to work.

Thanks folks. Sometimes you just need to bounce stuff off people to get to the right place.

I forgot to update this topic, sorry. But the problem has been fixed (I changed the object storage server)

False alarm, Sorry for the noise. User error. CDN setting and a typo in the env file on a system. Actually surprising that it was working except for the downloads, which I had not tested. Thanks anyway!

I've reverted the image which missed the migrate command helper and pushed a new package with it. For users which upgraded to 3.0.0-1 directly just run the migrate as mentioned.

I had this, it'll likely be plugins, see my post here https://forum.cloudron.io/post/92283

@jdaviescoates said in Post update to 8.0.3 one of my PeerTube instances is Not Responding:

But it's a bit odd that bridport.tv is still running fine (that also uses OIDC)

I guess the issue was actually an incompatibility with that plugin and other plugins, not with the OIDC plugin itself.

Because I managed to use to the File Manager to edit /app/data/storage/plugins/package.json to remove all references to other plugins and now uniteddiversity.tv is back up and running again! 🙂

I now only have this (which I copy/ pasted from the running bridport.tv) :

(Although for some odd reason after editing the file the owner had changed from 'cloudron' to 'root' so I just changed that back to 'cloudron).

Stupidly I didn't make a copy of previous package.json to easily know which plugins I was previously using... if I had I could turn them on one by one to find the culprit... I guess I could extract that info out of a backup, but I doubt I'll bother now...

I saw this post as still being "unsolved".

Yesterday i succefully downloaded a exported backup from my Peertube instance (35GB).

So that's working fine now 👌

Did not yet import it to another instance. But will try to do that in a short matter of time...

This time the update went perfect. I must say that i removed some plugins before the update this time, so certainly there was a plugin that bothered with the update.

Yep probably. I thought there might be a way to have an app password, that I was unfamiliar with.

@LoudLemur Peertube uses Prosody XMPP server for its livechat:

brave_nVI8zBZyPd.png

As far as I understood, those are all optional and you can set them as you like. However one storage related change was required and I've put that into the start.sh to get added.

Yep. Bunny has those too.
You can encrypt the videos for each session.
You restrict the videos to play on only some domains etc.

@scooke you could also experiment with taking off the https:// from your endpoint as I don't think that's supposed to be there 🙂

I found the issue with some help from their Git. I'm posting it here because it's not well-documented and doesn't seem to be mentioned anywhere else. (EDIT: Hats off to the dev, who upon seeing my Git post went and updated the documentation to specifically recommend reviewing this directive!)

Peertube DOES throttle network speed! A fresh install is limited to 5 MB/s. This is fine for 1080P but barely adequate for typical 30 FPS 4K footage, and unworkable for high-quality 4K or 4K at 60 FPS. For perspective, YouTube recommends nearly 9 MB/s for 60FPS 4K video.

You can adjust this hard limit by modifying peertube.conf and adjusting the values listed below:

You should take your network performance, desired video quality, and download functionality into consideration before modifying these. For most people, 10M should give you ample 4K quality without excessive buffering. If you want to allow downloads, consider setting them to 25M or higher.

I'm glad this wasn't a Cloudron issue, but I appreciate the effort of anyone who took the time to stop and think about this one. I suspect this value was different in previous versions and carries over with upgrades; this may only affect new installations.

I fixed the docs, thanks for reporting.

@LoudLemur said in How to setup Object Storage for Peertube on Cloudron (iDrive e2):

Do you think this might be to enable other instances following / subscribing to your own, so they might need access to those files?

Good question, possibly, but I've really no idea.

Try subscribing to https://uniteddiversity.tv and/ or https://bridport.tv and let's see what happens...?

@jdaviescoates Good catch, I meant AWS S3 as that seems to be the standard and most tuts use that, and most S3-compatible also use similar phrasing for their options, but as the number of posts eve just here on this forum say, non AWS S3 is a crapshoot.