Hi, when I create a live stream in jitsi meet using the RTMP URL data from the peertube instance, I get an error. It tells me that the stream could not be started. However, if I try to start a stream with the OBS software, the peertube stream works without problems. Attached are screenshots of the peertube and jitsi configurations, plus the URL to the peertube documentation for creating live streams. I hope you can help me. Thanks
Unfortunately I have a similar problem. I can stream to my own PeerTube instance via ffmpeg directly or via OBS. I can also stream from the Jitsi public instance. Unfortunately I can’t stream from my own Jitsi instance to my PeerTube instance. I used the URL format shared above rtmp://domain.com:1935/live/stream-code on all occasions. I relied on Self-Hosting Guide - Docker · Jitsi Meet Handbook and as far as I can tell worked well so far. Suggestions appreciated.
I’m sure I can do that @bbaldino . I tried docker logs docker-jitsi-meet_jvb_1 but didn’t see anything useful there. What command should I run to share the most useful logs to debug this specific situation?
Getting this still despite the URL working with Obs. Is there something to enable on the Jitsi Docker configuration to enable streaming to custom instances?
I checked logs via Docker on all 4 containers but nothing our of the ordinary. What I see though client side is Uncaught (in promise) iq id="e5ce0dd9-1153-4b73-8645-d2262cbdde13:sendIQ" to="c43327ff-81d8-4433-8dbe-…firstname.lastname@example.org/Sf0qyy7G" type="error" xmlns="jabber:client" from="email@example.com/focus"
Could it be related to jibri specifcally as asked by @bbaldino? I assumed it was started by default due to the button being available in the web interface but this line of the documentation If you want to use jibri too, first configure a host as described in JItsi BRoadcasting Infrastructure configuration section and then run Docker Compose and the lack of Jibri appearing in docker ps makes me think it is not.
Well I enabled Jibri as suggested above. I updated my kernel to have the audio loopback on the host. I rebooted and had the module properly loaded verified via lsmod | grep snd_aloop. I have Jibri running in Docker and see no error in the log. Unfortunately… still (!) the same error.