Hi,
I installed Peertube on Kubernetes (Microk8s). The installation works fine, except for live streaming.
RTMP is now exposed on port 30xxx. I can start a stream (from OBS, e.g.) and the Peertube-Player starts loading after 30s, but doesn't get any data. On server level I can see a file beeing created under storage/streaming-playlists/hls, max size of that file is always around 400K.
Any ideas, why the player is not getting any data?
Peertube-Image: 3.1.0
Hi,
I installed Peertube on Kubernetes (Microk8s). The installation works fine, except for live streaming.
RTMP is now exposed on port 30xxx. I can start a stream (from OBS, e.g.) and the Peertube-Player starts loading after 30s, but doesn't get any data. On server level I can see a file beeing created under storage/streaming-playlists/hls, max size of that file is always around 400K.
Any ideas, why the player is not getting any data?
Peertube-Image: 3.1.0
Indeed it's odd, if you hav the Peertube UI, then the ingress works fine, and if OBS sends data correctly, then the exposure of TCP works too.
Perhaps it's something regarding the web socket, in live streaming the player refresh the "fragment playlist" with new .mp4 very often.
Does the browser console (f12 to get is usually on majority of browser) tell you anything wrong, like 404, or any other 50X errors?
Could you also confirm that you have enabled HLS in Peertube admin console and not webtorrent? (HLS is mandatory for streaming)
Another thing that could help, I remember an old bug in Peertube, using streaming-playlistS in configuration, but streaming-playlist (without s) on disk, perhaps try to check if what you see in the browser (something like your_url/streaming_playlist) and the real directory on disk has the exact same name.
Hope it helps!
Do not hesitate to come back if these ideas does not solve the problem 💪
Hello,
Indeed it's odd, if you hav the Peertube UI, then the ingress works fine, and if OBS sends data correctly, then the exposure of TCP works too.
Perhaps it's something regarding the web socket, in live streaming the player refresh the "fragment playlist" with new .mp4 very often.
Does the browser console (f12 to get is usually on majority of browser) tell you anything wrong, like 404, or any other 50X errors?
Could you also confirm that you have enabled HLS in Peertube admin console and not webtorrent? (HLS is mandatory for streaming)
Another thing that could help, I remember an old bug in Peertube, using streaming-playlist**S** in configuration, but streaming-playlist (without **s**) on disk, perhaps try to check if what you see in the browser (something like `your_url/streaming_playlist`) and the real directory on disk has the exact same name.
Hope it helps!
Do not hesitate to come back if these ideas does not solve the problem 💪
the console hint put me on the right track. There was some misconfiguration in my nginx/peertube.conf and the streaming-playlists/hls/xxx/master.m3u8 was not reachable. I left out all optional performance parts for now in the nginx conf and streaming works.
Still I get two types of errors from time to time:
Hi,
the console hint put me on the right track. There was some misconfiguration in my nginx/peertube.conf and the streaming-playlists/hls/xxx/master.m3u8 was not reachable. I left out all optional performance parts for now in the nginx conf and streaming works.
Still I get two types of errors from time to time:
- HLS.js error: mediaError - fatal: false - bufferStalledError
- Access error to wss://domain.com/tracker/socket
So I will dig a little.
Main problem solved, thanks a lot!
Not sure but the "bufferStalledError" could be this bug in Peertube, because of slow disk or the browser requesting the playlist file at the wrong moment.
No real solution at the moment, mainly workaround, but still it could help!
Good luck, do not hesitate to reopen if you need more help about that :-)
Good news!
Not sure but the "bufferStalledError" could be [this bug](https://github.com/Chocobozzz/PeerTube/issues/3979) in Peertube, because of slow disk or the browser requesting the playlist file at the wrong moment.
No real solution at the moment, mainly workaround, but still it could help!
Good luck, do not hesitate to reopen if you need more help about that :-)
Hi,
I installed Peertube on Kubernetes (Microk8s). The installation works fine, except for live streaming.
RTMP is now exposed on port 30xxx. I can start a stream (from OBS, e.g.) and the Peertube-Player starts loading after 30s, but doesn't get any data. On server level I can see a file beeing created under storage/streaming-playlists/hls, max size of that file is always around 400K.
Any ideas, why the player is not getting any data?
Peertube-Image: 3.1.0
Hello,
Indeed it's odd, if you hav the Peertube UI, then the ingress works fine, and if OBS sends data correctly, then the exposure of TCP works too.
Perhaps it's something regarding the web socket, in live streaming the player refresh the "fragment playlist" with new .mp4 very often.
Does the browser console (f12 to get is usually on majority of browser) tell you anything wrong, like 404, or any other 50X errors?
Could you also confirm that you have enabled HLS in Peertube admin console and not webtorrent? (HLS is mandatory for streaming)
Another thing that could help, I remember an old bug in Peertube, using streaming-playlistS in configuration, but streaming-playlist (without s) on disk, perhaps try to check if what you see in the browser (something like
your_url/streaming_playlist
) and the real directory on disk has the exact same name.Hope it helps!
Do not hesitate to come back if these ideas does not solve the problem 💪
Hi,
the console hint put me on the right track. There was some misconfiguration in my nginx/peertube.conf and the streaming-playlists/hls/xxx/master.m3u8 was not reachable. I left out all optional performance parts for now in the nginx conf and streaming works.
Still I get two types of errors from time to time:
So I will dig a little.
Main problem solved, thanks a lot!
Good news!
Not sure but the "bufferStalledError" could be this bug in Peertube, because of slow disk or the browser requesting the playlist file at the wrong moment.
No real solution at the moment, mainly workaround, but still it could help!
Good luck, do not hesitate to reopen if you need more help about that :-)