Peertube buffering (and possible upgrade to HLS playback)

I’m not sure if this is the right place for this, but I’m experiencing problems watching the videos on the scanlines peertube. It seems kind of random because sometimes it works fine but other times even short videos wont buffer at all. Does anyone else have similiar issues?

yeah… peertube is tricky. we have changed the configuration a couple times, and it seems like all of the videos that people have uploaded since the last change are working, so there might just be problems with certain videos.

if anyone has issues with videos uploaded in the past week or so going forward, definitely let us know. as for the older ones, i’m not sure how we could fix them, but it would probably take a long time as our server would have to re-process them.


thanks! I’ll check the newer ones!

The Peertube player has some issues with this video by @hypermosh, at least for me, as it only plays from 00’:04" onwards.

same for me - this is a weird one

This video can not be started at 0 seconds: But 2 seconds as starting point is OK.

And it did not play until end. Stopped at 12 seconds.

1 Like

gonna have to take a deepr look into these when i get the chance. thank for posting any problems you find out there !

When I upload videos, these videos are not played in the player afterwards.
If you take a closer look at the progress bar, you can see that the beginning of the video is not loaded. This area is marked in red.
If I click on the green marked area in the progress bar, the video can be played from this position.

But I can’t get the video to start on its own.
And, even when clicking at the left beginning of the progress bar, I can’t see the beginning of the video.

This effect is observed in at least two of my videos.

I confirm @Kandid 's report, but I can’t find any clues in the Peertube logs of our instance.

I couldn’t either find any existing bug report in the Peertube issue tracker. It’d be great if someone else could try searching too. If no existing bug reports about this show up, I’ll be happy to file a bug report.

not even sure this makes sense but maybe it’d help if someone downloaded the original file by @Kandid (should be this link), check it and confirm this issue has nothing to do with the file itself (keyframes, etc)?

another useful attempt could be to upload this same video to another Peertube instance (best if managed by someone who’s open to look into this and discuss with us) and compare the results

I’ve been making more tests and looks like this same issue affects different videos on our instance and it seems that duration, size, ratio or audio don’t matter.

affected files seem to all be mp4 files, encoded in h264, yuv420p Pixel format, “High” Profile. they also all seem to have bitrate > 1-2 mbps.
but other videos on our instance (including this one with a 4 mbps bitrate) are encoded in the same way, and they seem to play fine.

let’s build a list of files affected by this problem.
please check the following videos and confirm whether they’re affected by the same issue, or if they play correctly for you.

Now I have uploaded the video “color 2 sound: Der Hirsch” for a test at On this instance it can be played from the beginning.

This video was recorded with SimpleScreenRecorder as H.264.

Here is the output from ffprobe:

Input #0, mov,mp4,m4a,3gp,3g2,mj2, from ‘color2sound-hirsch-2021-05-24_18.36.18.mp4’:
major_brand : isom
minor_version : 512
compatible_brands: isomiso2avc1mp41
encoder : Lavf58.20.100
Duration: 00:01:31.25, start: 0.000000, bitrate: 5324 kb/s
Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709), 1024x1024 [SAR 1:1 DAR 1:1], 5193 kb/s, 25.01 fps, 25 tbr, 12800 tbn, 50 tbc (default)
handler_name : VideoHandler
Stream #0:1(und): Audio: mp3 (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 128 kb/s (default)
handler_name : SoundHandler

1 Like

thank you both for helping to troubleshoot this. the example videos are playing ok for me but i’m on my phone so it’s likely playing a lower quality rendition for me.

unfortunately things are too hectic for me to help troubleshoot from a computer right now, but i will try to look into this issue when i am able to (likely after i finish moving). one thing i have found helpful is to look at the javascript console in developer tools in the browser, sometimes peertube will spit out helpful information in there.

This is the Debug Console in Firefox 78.10.0esr (64-bit). On a Debian 10 system.
However, the “HLS.js error: mediaError - fatal: false - fragParsingError” is also listed in the console for videos that can be played from the beginning.

This is a speculation:

It is possible that the problem is not directly related to But with the connection of the browser on the local PC with the provider of the cloud storage.

As I understand it, the video stream is not loaded directly from ( / digitalocean?) but from Wasabi. seems to be a server in Amsterdam Netherlands.

7 ( 25.164 ms 24.305 ms 24.482 ms
8 ( 32.149 ms 33.312 ms 33.443 ms
9 ( 32.605 ms 33.121 ms ( 35.917 ms

revers whois:
network:Org-Name:Wasabi Technologies, Inc

Domain names on IP address
IP Owner: PSINet, Inc
IP Location: Netherlands Amsterdam, North Holland, Netherlands

When I record the connection to while the video should start (but did nor start), I see some strange TCP packets.

First: “Alert Message: Encrypted Alert” sent by the browser
Then the browser tries to disconnect from

1 Like

that’s right, the storage is wasabi, we don’t have nearly enough storage on the digitalocean droplet to host all the video content.

it does seem like there might be issues with the “handshake” between wasabi, the peertube client, and the user. the hls stream / peer to peer functionality seems to be pretty complex and tricky to debug -_-


i found this issue that looks like it might be related.

@cyberboy666 are you able to check the ffmpeg version we have installed? i can’t find any indication through the UI.


i just ssh’d into the droplet and checked with ffmpeg -v :

ffmpeg version 3.4.8-0ubuntu0.2

so yeap this might be the problem - i can try updating the ffmpeg version now.

another thing we could do just to narrow down the problem is disable the wasabi static object storage for a moment and test uploading some videos directly to disk. and then see if the problem is still there ? if not then atleast we know the problem is in the static object storage somewhere

ok updated we are on ffmpeg version 4.3.2-0york0~18.04 now


4 posts were split to a new topic: Login issues at