When i start a record with Jibri, start recording button doesn't turn back to stop recording

[afreisinger]

What happened? Description:

When i start a record on a Jitsi meet with Jibri, the "start recording" button doesn't turn back to "stop recording". I can't stop.

Record works perfectly, and is saved on my server, The only issue is the web interface that doesn't refresh the record button.

Steps to reproduce: Start a meet and a record with Jibri Release: stable-10133-1

Expected behavior: The start/stop recording button toggle nicely

Actual behavior: Record button doesn't change to "Stop recording" when i start it.

Each service required by Jitsi (such as jitsi-meet, prosody, jicofo, jvb, and jibri) is running on its own VM. Each service was deployed using Docker.

Platform Chrome (or Chromium based) Firefox

[saghul]

@Calinteodor didn't you look into something similar not too long ago?

[Calinteodor]

This commit fixed the issue that I encountered: https://github.com/jitsi/jitsi-meet/commit/8745f07052db630d30cc6e8736e5333a683b00a5

[saghul]

Thanks! @afreisinger can you please try with version 10169?

[afreisinger]

I updated to the indicated version (10169) and didn’t observe any changes. When I start a recording, I hear the audio message confirming it has started, but the recording button doesn’t change to allow stopping it. If I press the button again, it simply notifies me that a recording is already in progress.

However, when I leave the video conference, the recording file is generated correctly.

We’re running a distributed Jitsi setup where all services are deployed using Docker. Specifically: jitsi-meet, prosody, jicofo, and HAProxy are all running in containers on the same VM. We have five Jitsi Video Bridges (JVB), each deployed in a Docker container on its own separate VM. Jibri is also running in a Docker container on a dedicated VM.

[afreisinger]

Only change the button to 'Stop Recording' if the local recording mode(Beta) is selected.

[saghul]

Just to confirm, you updated all components to that version, correct?

[afreisinger]

Yes, I updated all components to the stable-10184 version and everything remains the same, as indicated in the following issue #15897

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.