ingress Cannot play url ingress locally

When I start ingress to play audio by local ip address it's not being played, I just wee EOS log

http://192.168.28.149/cms/public/uploads/audios/fa5d1cdc105793d43a64f71032ee6730d7.mp3

I tried to use remote host and http with the same file and it played well

Aug 16 '24 10:08 serhiynovos

After some research I found that this issue not only with local urls but also can happen with remote URLs for audio and video but less frequently.

1.4.0 version is working fine and starting from 1.4.1 version I'm facing this issue. On 1.4.1 release notes I see this PR https://github.com/livekit/ingress/pull/250 which I feel can be root of cause

Aug 20 '24 06:08 serhiynovos

We're running into this as well. It seems not all files cause this issue. I'm not sure what exact property leads to the issue (it doesn't seem to be codecs) but I can share the ffprobe output if needed.

Nov 27 '24 02:11 Yohe-Am

We're running into this as well. It seems not all files cause this issue. I'm not sure what exact property leads to the issue (it doesn't seem to be codecs) but I can share the ffprobe output if needed.

As I understand in 1.4.1 release they added asynchronous room joining which has some sync issue which means as let latency between ingress and http source than more frequently it happen. For me if http source and ingress are running in the same k8s cluster where latency is close to 0 it always happens. In other cases when try to use remote it's more stable but still is not working as solid as 1.4.0

Nov 28 '24 08:11 serhiynovos

Yeah, your diagnosis is correct. The issue completely disappears when I revert the changes made in the PR.

Nov 28 '24 08:11 Yohe-Am

Bump for this issue. It's still a huge problem for us, that URL_INPUT videos are joining the livekit room very delayed or not at all. Audiotracks are fine, but Videotracks are delayed. Would it make sense to allow the user to decide, whether the ingress should join the room asynchronously or not?

Mar 18 '25 09:03 ezBeanie

@ezBeanie go with version 1.4.0, it doesn't have the bug.

Mar 18 '25 10:03 Yohe-Am

@Yohe-Am Thanks for this hint, we did infact revert to 1.4.0 but we dont want to be stuck at that version indefinitely.

Mar 19 '25 08:03 ezBeanie

@Yohe-Am Thanks for this hint, we did infact revert to 1.4.0 but we dont want to be stuck at that version indefinitely.

Yeah it will be a huge problem in the future as at some period of time it it may stop support latest livekit server

Mar 20 '25 12:03 serhiynovos