Livekit egress BUG. the signal not receiving from self hosted livekit server in on-prem kubernetes server

Open Manivannanj127 opened this issue 10 months ago • 1 comments

Describe the bug error: "Start signal not received" error_code: 412.

Egress Version egress v-1.9.0

Additional context The LiveKit server is running, and the recording has started, but the recording is not being stored in the S3 bucket. It shows the error: 'Start signal not received' with error code 412. The S3 credentials have been cross-checked and are correct. The same configuration works fine when using the LiveKit console with the WebSocket URL, API key, and API secret, and it stores the recording in the S3 bucket. However, when running it with self-hosting, the error appears. Can anyone provide a solution to resolve this issue?

Logs file { filename: "recordings/.mp4" started_at: 1739527031659582157 ended_at: 1739527031659734247 duration: 152090 } error: "Start signal not received" started_at: 1739527024816835412 ended_at: 1739527031659577507 room_name: "" file_results { filename: "recordings/******************.mp4" started_at: 1739527031659582157 ended_at: 1739527031659734247 duration: 152090 } updated_at: 1739527031659577507 error_code: 412

Kindly share some solution . what is the issue. should i need to configure additionally?

Feb 14 '25 11:02 Manivannanj127

It's almost always a networking/firewall issue

Mar 03 '25 07:03 frostbyte73