This message was deleted.

@freezing-portugal-5573 when does that error come up? Could you share what you are trying to do?

Hey @dry-elephant-14928, this happens when when I try to make the room composite egress to mux. First it connects and streams for a few seconds but then it disconnects with the mentioned error. I tried to do this numerous times but same result every time. I have a web app that connects to a room and I would like to send that room to mux for live streaming

Are you using LiveKit Cloud? if so could you share an example session or Egress where this has happened?

Yes I am using it. By example, do you mean the session id (

RM_3Zp2ksCxh57k

) and Egress id (

EG_L8y4QEgXVRMu

) or something else?

@freezing-portugal-5573, sorry for the delayed response here. I think this is actually an issue with Mux. We've received several reports of this where the RTMP connection appear to be terminated on their side. We'll work with them to get to the bottom of it as it appears to be impacting quite a few folks

No worries @dry-elephant-14928 and thank you for taking care of it. And if you can please notify me when the issue has been resolved.

Hey @freezing-portugal-5573 can you give me an example of the request you were using? Mux is asking for more recent examples (past 7 days) so I am trying to reproduce

Hey @able-gigabyte-21598 no problem! So, I’m using

livekit-server-sdk@1.2.7

with nestjs backend and in the

EgressClient

I’m calling

startRoomCompositeEgress

function with my currently live room and output set to RTMP (

<mux://stream-key>

). It then tries to connect to Mux and it does sometimes, but after up to 10 seconds, it disconnects and stops egress

For the

startRoomCompositeEgress

request, are you using any specific options like presets, resolutions, etc or all defaults?

I’m trying a minimum example so I only use

layout: 'single-speaker'

We need an example from within 7 days to send to mux to investigate - if you have any recent reproductions, please send me the mux stream IDs

I have reproduced it now again.. here are IDs, let me know if you need anything else. mux live stream id:

rBcrqewWYghaz9rPHavABqG9SrbqASkv83RI3yIzLqA

session id:

RM_77YuXsW7vRbL

egress id:

EG_3DHhztnoMT7d

The stream key you used was for live stream id

Xfw63RVmePhdT9anLLayLK4UoXQwws4aFkhkCW5i8I00

, which was deleted on Jan 11

Hey @able-gigabyte-21598! I am facing the same issue here! I have a recent case to share, hopefully Mux will have enough time to investigate it: • LiveKit Session ID:

RM_9mSKFXb8jFEJ

. • LiveKit Egress IDs:

EG_4pJoa42X67TQ

and

EG_a39KEXC77qGw

◦ Both failed with the same message: “Connection error: connection closed remotely”. • Mux ID:

00rNOrk8m01DMxw8mo2yoojOmlX7Na3fuN

. • Stream Date:

2024-03-06

. I am also trying to start a Room Composite Egress. Here is the code in Ruby:

egress = egress_client.start_room_composite_egress(
        room_name,
        LiveKit::Proto::StreamOutput.new(
          protocol: LiveKit::Proto::StreamProtocol::RTMP,
          urls: ["mux://#{live_event.stream_key}"]
        ),
        layout: 'speaker'
      )

Here are the screenshots from Mux and LiveKit dashboards:

I’ll pass this along and let you know!

Thank you!

It looks like this is because they didn’t receive any keyframes for the first 10 seconds. I’ll have to do more debugging and try to reproduce it