Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Recording option in jitsi meet mobile view #556

Open
1 of 11 tasks
Harshavardhan77300 opened this issue Jan 3, 2025 · 22 comments
Open
1 of 11 tasks

Recording option in jitsi meet mobile view #556

Harshavardhan77300 opened this issue Jan 3, 2025 · 22 comments

Comments

@Harshavardhan77300
Copy link

Harshavardhan77300 commented Jan 3, 2025 •
edited
Loading

What happened?

In jitsi meet, recording option is not visible for mobile view. How can i enable the recording option

Platform

  • Chrome (or Chromium based)
  • Firefox
  • Safari
  • Other desktop browser
  • Android browser
  • iOS browser
  • Electron app
  • Android mobile app
  • iOS mobile app
  • Custom app using a mobile SDK

Browser / app / sdk version

jitsi-meet-2.0.9909-1, jitsi-meet-prosody-1.0.8302-1,

Relevant log output

No response

Reproducibility

  • The problem is reproducible on meet.jit.si

More details?

No response
@saghul
Copy link
Member

saghul commented Jan 3, 2025

Did you deploy Jibri? It it functional on the web version?

@Harshavardhan77300
Copy link
Author

yes jibri also deployed

@saghul
Copy link
Member

saghul commented Jan 10, 2025

Does it work in the desktop web version? Note that local recordings are not using Jibri so while you may see that it's not an indication of recordings working.

@Harshavardhan77300
Copy link
Author

Yes in desktop Web version it is working, but in mobile view even recording icon also not displayed.

@saghul
Copy link
Member

saghul commented Jan 11, 2025

Can you share a screenshot of what you see on the desktop web?

@Harshavardhan77300
Copy link
Author

image
image

@Harshavardhan77300
Copy link
Author

Harshavardhan77300 commented Jan 11, 2025 •
edited
Loading

even in 3dots (more icon) also there is no recording button
but in desktop is was displaying

@saghul
Copy link
Member

saghul commented Jan 11, 2025

That's not our UI though. Does the vanilla UI work?

@Harshavardhan77300
Copy link
Author

now i got that recording icon but it was not starting getting error
UnhandledPromiseRejection: [object Element] StackTrace: undefined
no Jibris available

bu the jibri server is in active only
image

@damencho
Copy link
Member

Check jibri logs.

@Harshavardhan77300
Copy link
Author

image

@damencho
Copy link
Member

Hard to figure out from a screenshot snippet whether it connected to the control room.

@Harshavardhan77300
Copy link
Author

then could please tell what i need to share now?

@damencho
Copy link
Member

The whole file.

@Harshavardhan77300
Copy link
Author

GNU nano 7.2 /var/log/jitsi/jibri/log.0.txt
2025-01-13 17:39:38.398 INFO: [1] MainKt.handleCommandLineArgs#188: Jibri run with args [--config, /etc/jitsi/jibri/config.json]
2025-01-13 17:39:38.511 INFO: [1] MainKt.setupLegacyConfig#213: Checking legacy config file /etc/jitsi/jibri/config.json
2025-01-13 17:39:39.075 SEVERE: [1] JibriConfigKt.loadConfigFromFile#198: A required config parameter was missing: Instantiation of [simple type, class org.jitsi.jibr>
2025-01-13 17:39:39.076 INFO: [1] MainKt.setupLegacyConfig#221: Parsing legacy config file failed
2025-01-13 17:39:39.101 INFO: [1] MainKt.main#55: Jibri starting up with id
2025-01-13 17:39:39.111 FINE: [1] MetricsContainer.registerCounter#152: Counter 'sessions_started' was renamed to 'sessions_started_total' to ensure consistent metric>
2025-01-13 17:39:39.117 FINE: [1] MetricsContainer.registerCounter#152: Counter 'sessions_stopped' was renamed to 'sessions_stopped_total' to ensure consistent metric>
2025-01-13 17:39:39.117 FINE: [1] MetricsContainer.registerCounter#152: Counter 'errors' was renamed to 'errors_total' to ensure consistent metric naming.
2025-01-13 17:39:39.117 FINE: [1] MetricsContainer.registerCounter#152: Counter 'busy' was renamed to 'busy_total' to ensure consistent metric naming.
2025-01-13 17:39:39.118 FINE: [1] MetricsContainer.registerCounter#152: Counter 'xmpp_connected' was renamed to 'xmpp_connected_total' to ensure consistent metric nam>
2025-01-13 17:39:39.118 FINE: [1] MetricsContainer.registerCounter#152: Counter 'xmpp_reconnecting' was renamed to 'xmpp_reconnecting_total' to ensure consistent metr>
2025-01-13 17:39:39.118 FINE: [1] MetricsContainer.registerCounter#152: Counter 'xmpp_reconnection_failed' was renamed to 'xmpp_reconnection_failed_total' to ensure c>
2025-01-13 17:39:39.118 FINE: [1] MetricsContainer.registerCounter#152: Counter 'xmpp_ping_failed' was renamed to 'xmpp_ping_failed_total' to ensure consistent metric>
2025-01-13 17:39:39.118 FINE: [1] MetricsContainer.registerCounter#152: Counter 'xmpp_closed' was renamed to 'xmpp_closed_total' to ensure consistent metric naming.
2025-01-13 17:39:39.118 FINE: [1] MetricsContainer.registerCounter#152: Counter 'xmpp_closed_on_error' was renamed to 'xmpp_closed_on_error_total' to ensure consisten>
2025-01-13 17:39:39.118 FINE: [1] MetricsContainer.registerCounter#152: Counter 'stopped_on_xmpp_closed' was renamed to 'stopped_on_xmpp_closed_total' to ensure consi>
2025-01-13 17:39:39.446 INFO: [1] JwtInfo$Companion.fromConfig#176: got jwtConfig: {}

2025-01-13 17:39:39.446 INFO: [1] JwtInfo$Companion.fromConfig#186: Unable to create JwtInfo: com.typesafe.config.ConfigException$Missing: reference.conf @ jar:file:/>
2025-01-13 17:39:39.453 FINE: [1] RefreshingProperty.getValue#46: Refreshing property jwt (not yet initialized or expired)...
2025-01-13 17:39:39.500 INFO: [1] MainKt.main#128: Using port 3333 for internal HTTP API
2025-01-13 17:39:39.529 FINE: [27] WebhookClient$updateStatus$1.invokeSuspend#109: Updating 0 subscribers of status
2025-01-13 17:39:39.858 INFO: [1] XmppApi.updatePresence#203: Jibri reports its status is now JibriStatus(busyStatus=IDLE, health=OverallHealth(healthStatus=HEALTHY, >
2025-01-13 17:39:39.866 INFO: [1] MainKt.main#154: Using port 2222 for HTTP API
2025-01-13 17:40:39.465 FINE: [27] WebhookClient$updateStatus$1.invokeSuspend#109: Updating 0 subscribers of status
2025-01-13 17:41:39.466 FINE: [27] WebhookClient$updateStatus$1.invokeSuspend#109: Updating 0 subscribers of status
2025-01-13 17:42:39.465 FINE: [27] WebhookClient$updateStatus$1.invokeSuspend#109: Updating 0 subscribers of status
2025-01-13 17:43:39.465 FINE: [27] WebhookClient$updateStatus$1.invokeSuspend#109: Updating 0 subscribers of status
2025-01-13 17:44:39.466 FINE: [27] WebhookClient$updateStatus$1.invokeSuspend#109: Updating 0 subscribers of status
2025-01-13 17:45:39.466 FINE: [27] WebhookClient$updateStatus$1.invokeSuspend#109: Updating 0 subscribers of status
2025-01-13 17:46:39.465 FINE: [27] WebhookClient$updateStatus$1.invokeSuspend#109: Updating 0 subscribers of status
2025-01-13 17:47:39.465 FINE: [27] WebhookClient$updateStatus$1.invokeSuspend#109: Updating 0 subscribers of status

@damencho
Copy link
Member

Seems you don't have any shards configured in your config. Share jibri config and mask any private information.

@damencho damencho transferred this issue from jitsi/jitsi-meet Jan 13, 2025
@Harshavardhan77300
Copy link
Author

Harshavardhan77300 commented Jan 13, 2025 •
edited by damencho
Loading 

{
    "recording_directory": "/srv/recordings",
    "finalize_recording_script_path": "/opt/jitsi/upload-to-s3.sh",
    "xmpp_environments": [
        {
            "name": "prod environment",
            "xmpp_server_hosts": [
                "meet.aairavx.com"
            ],
            "xmpp_domain": "meet.aairavx.com",
            "control_login": {
                "domain": "auth.meet.aairavx.com",
                "username": "jibri",
                "password": "jibri123"
            },
            "control_muc": {
                "domain": "internal.auth.meet.aairavx.com",
                "room_name": "JibriBrewery",
                "nickname": "jibri-nickname"
            },
            "call_login": {
                "domain": "recorder.meet.aairavx.com",
                "username": "recorder",
                "password": "recorder123"
            },
                      "usage_timeout": 0
        }
    ],
    "auto_record": false,
     "recording": {
        "storage": "s3",
        "s3": {
            "bucket": "clinicspots-examine-videos",
            "access-key": "xxxxxx",
            "secret-key": "xxxxxxx",
            "region": "ap-south-1",
            "endpoint": "s3.amazonaws.com"
        }
    }
}

@damencho
Copy link
Member

The format of the config is wrong:
https://github.com/jitsi/jibri?tab=readme-ov-file#config-files

@Harshavardhan77300
Copy link
Author

Harshavardhan77300 commented Jan 13, 2025 •
edited by damencho
Loading 

jibri {
        recording {
        enabled = false
        recordings_directory = "/srv/recordings"
        finalize_recording_script_path = "/opt/jitsi/upload-to-s3.sh"
        bucket = "clinicspots-examine-videos"  // Replace with your S3 bucket name
        region = "ap-south-1"         // Replace with your S3 bucket region
        credentials {
            accessKeyId = "xxxxxx"        // Replace with the IAM Access Key ID
            secretAccessKey = "xxxxxx" // Replace with the IAM Secret Access Key
        }
       }
     api {
       xmpp {
        environments = [
        {
            name = "prod environment"
            xmpp-server-hosts = ["meet.aairavx.com"],
            xmpp-domain = "meet.aairavx.com"
            control-muc = {
                domain = "internal.auth.meet.aairavx.com"
                room-name = "JibriBrewery"
                nickname = "jibri-nickname"
            }
            control-login = {
                                             domain = "auth.meet.aairavx.com"
                username = "jibri"
                password = "jibri123"
            }
            call-login = {
                domain = "recorder.meet.aairavx.com"
                username = "recorder"
                password = "recorder123"
            }
           strip-from-room-domain = "conference."
           trust-all-xmpp-certs = true
           usage-timeout = 0

         }
      ]
     }
   }
}

i have changed according to the link but again getting same error
image

@damencho
Copy link
Member

Show the jibri log with the new config.

@Harshavardhan77300
Copy link
Author

2025-01-13 18:22:35.999 INFO: [1] MainKt.handleCommandLineArgs#188: Jibri run with args [--config, /etc/jitsi/jibri/config.json]
2025-01-13 18:22:36.098 INFO: [1] MainKt.setupLegacyConfig#213: Checking legacy config file /etc/jitsi/jibri/config.json
2025-01-13 18:22:36.685 SEVERE: [1] JibriConfigKt.loadConfigFromFile#198: A required config parameter was missing: Instantiation of [simple type, class org.jitsi.jibr>
2025-01-13 18:22:36.685 INFO: [1] MainKt.setupLegacyConfig#221: Parsing legacy config file failed
2025-01-13 18:22:36.706 INFO: [1] MainKt.main#55: Jibri starting up with id
2025-01-13 18:22:36.714 FINE: [1] MetricsContainer.registerCounter#152: Counter 'sessions_started' was renamed to 'sessions_started_total' to ensure consistent metric>
2025-01-13 18:22:36.720 FINE: [1] MetricsContainer.registerCounter#152: Counter 'sessions_stopped' was renamed to 'sessions_stopped_total' to ensure consistent metric>
2025-01-13 18:22:36.720 FINE: [1] MetricsContainer.registerCounter#152: Counter 'errors' was renamed to 'errors_total' to ensure consistent metric naming.
2025-01-13 18:22:36.720 FINE: [1] MetricsContainer.registerCounter#152: Counter 'busy' was renamed to 'busy_total' to ensure consistent metric naming.
2025-01-13 18:22:36.720 FINE: [1] MetricsContainer.registerCounter#152: Counter 'xmpp_connected' was renamed to 'xmpp_connected_total' to ensure consistent metric nam>
2025-01-13 18:22:36.720 FINE: [1] MetricsContainer.registerCounter#152: Counter 'xmpp_reconnecting' was renamed to 'xmpp_reconnecting_total' to ensure consistent metr>
2025-01-13 18:22:36.721 FINE: [1] MetricsContainer.registerCounter#152: Counter 'xmpp_reconnection_failed' was renamed to 'xmpp_reconnection_failed_total' to ensure c>
2025-01-13 18:22:36.721 FINE: [1] MetricsContainer.registerCounter#152: Counter 'xmpp_ping_failed' was renamed to 'xmpp_ping_failed_total' to ensure consistent metric>
2025-01-13 18:22:36.721 FINE: [1] MetricsContainer.registerCounter#152: Counter 'xmpp_closed' was renamed to 'xmpp_closed_total' to ensure consistent metric naming.
2025-01-13 18:22:36.721 FINE: [1] MetricsContainer.registerCounter#152: Counter 'xmpp_closed_on_error' was renamed to 'xmpp_closed_on_error_total' to ensure consisten>
2025-01-13 18:22:36.721 FINE: [1] MetricsContainer.registerCounter#152: Counter 'stopped_on_xmpp_closed' was renamed to 'stopped_on_xmpp_closed_total' to ensure consi>
2025-01-13 18:22:37.054 INFO: [1] JwtInfo$Companion.fromConfig#176: got jwtConfig: {}

2025-01-13 18:22:37.056 INFO: [1] JwtInfo$Companion.fromConfig#186: Unable to create JwtInfo: com.typesafe.config.ConfigException$Missing: reference.conf @ jar:file:/>
2025-01-13 18:22:37.063 FINE: [1] RefreshingProperty.getValue#46: Refreshing property jwt (not yet initialized or expired)...
2025-01-13 18:22:37.100 INFO: [1] MainKt.main#128: Using port 3333 for internal HTTP API
2025-01-13 18:22:37.124 FINE: [27] WebhookClient$updateStatus$1.invokeSuspend#109: Updating 0 subscribers of status
2025-01-13 18:22:37.470 INFO: [1] XmppApi.updatePresence#203: Jibri reports its status is now JibriStatus(busyStatus=IDLE, health=OverallHealth(healthStatus=HEALTHY, >
2025-01-13 18:22:37.492 INFO: [1] XmppApi.start#150: Connecting to xmpp environment on meet.aairavx.com with config XmppEnvironmentConfig(name=prod environment, xmppS>
2025-01-13 18:22:37.493 INFO: [1] XmppApi.start#168: The trustAllXmppCerts config is enabled for this domain, all XMPP server provided certificates will be accepted
2025-01-13 18:22:37.529 INFO: [41] [hostname=meet.aairavx.com id=meet.aairavx.com] MucClient.initializeConnectAndJoin#288: Initializing a new MucClient for [ org.jits>
2025-01-13 18:22:37.564 WARNING: [41] MucClient.createXMPPTCPConnectionConfiguration#117: Disabling certificate verification!
2025-01-13 18:22:37.585 INFO: [41] [hostname=meet.aairavx.com id=meet.aairavx.com] MucClient.initializeConnectAndJoin#350: Dispatching a thread to connect and login.
2025-01-13 18:22:37.960 FINE: [41] JibriMetrics.incrementStatsDCounter#41: Incrementing statsd counter: xmpp-connected:xmpp_server_host:meet.aairavx.com
2025-01-13 18:22:37.960 INFO: [41] [hostname=meet.aairavx.com id=meet.aairavx.com] MucClient$2.connected#321: Connected.
2025-01-13 18:22:37.961 INFO: [41] [hostname=meet.aairavx.com id=meet.aairavx.com] MucClient.lambda$getConnectAndLoginCallable$9#646: Logging in.
2025-01-13 18:22:38.090 INFO: [41] [hostname=meet.aairavx.com id=meet.aairavx.com] MucClient$2.authenticated#327: Authenticated, b=false
2025-01-13 18:22:41.544 WARNING: [57] org.jivesoftware.smack.AbstractXMPPConnection.callConnectionClosedOnErrorListener: Connection XMPPTCPConnection[[email protected].>
org.jivesoftware.smack.XMPPException$StreamErrorException: system-shutdown You can read more about the meaning of this stream error at http://xmpp.org/rfcs/rfc6120.ht>
stream:errorReceived SIGTERM</stream:error>
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.parsePackets(XMPPTCPConnection.java:984)
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.access$700(XMPPTCPConnection.java:916)
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader$1.run(XMPPTCPConnection.java:939)
at java.base/java.lang.Thread.run(Thread.java:1583)
2025-01-13 18:22:41.549 WARNING: [41] [hostname=meet.aairavx.com id=meet.aairavx.com] MucClient.lambda$getConnectAndLoginCallable$9#671: Failed to join the MUCs.
org.jivesoftware.smack.SmackException$NotConnectedException: The connection XMPPTCPConnection[[email protected]/Z4lK5gqdRLSp] (0) is no longer connected whi>
stream:errorReceived SIGTERM</stream:error>
at org.jivesoftware.smack.StanzaCollector.nextResultOrThrow(StanzaCollector.java:276)
at org.jivesoftware.smackx.muc.MultiUserChat.enter(MultiUserChat.java:408)
at org.jivesoftware.smackx.muc.MultiUserChat.createOrJoin(MultiUserChat.java:546)
at org.jivesoftware.smackx.muc.MultiUserChat.createOrJoin(MultiUserChat.java:521)
at org.jitsi.xmpp.mucclient.MucClient$MucWrapper.join(MucClient.java:758)
at org.jitsi.xmpp.mucclient.MucClient.joinMucs(MucClient.java:370)
at org.jitsi.xmpp.mucclient.MucClient.lambda$getConnectAndLoginCallable$9(MucClient.java:667)
at org.jitsi.retry.RetryStrategy$TaskRunner.run(RetryStrategy.java:167)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
at java.base/java.lang.Thread.run(Thread.java:1583)
Caused by: org.jivesoftware.smack.XMPPException$StreamErrorException: system-shutdown You can read more about the meaning of this stream error at http://xmpp.org/rfcs>
stream:errorReceived SIGTERM</stream:error>
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.parsePackets(XMPPTCPConnection.java:984)
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.access$700(XMPPTCPConnection.java:916)
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader$1.run(XMPPTCPConnection.java:939)
... 1 more
2025-01-13 18:22:41.551 FINE: [57] JibriMetrics.incrementStatsDCounter#41: Incrementing statsd counter: xmpp-closed-on-error:xmpp_server_host:meet.aairavx.com
2025-01-13 18:22:41.554 WARNING: [57] [hostname=meet.aairavx.com id=meet.aairavx.com] MucClient$2.connectionClosedOnError#341: Closed on error:
org.jivesoftware.smack.XMPPException$StreamErrorException: system-shutdown You can read more about the meaning of this stream error at http://xmpp.org/rfcs/rfc6120.ht>
stream:errorReceived SIGTERM</stream:error>
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.parsePackets(XMPPTCPConnection.java:984)
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.access$700(XMPPTCPConnection.java:916)
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader$1.run(XMPPTCPConnection.java:939)
at java.base/java.lang.Thread.run(Thread.java:1583)
2025-01-13 18:22:46.670 FINE: [41] JibriMetrics.incrementStatsDCounter#41: Incrementing statsd counter: xmpp-connected:xmpp_server_host:meet.aairavx.com
2025-01-13 18:22:46.671 INFO: [41] [hostname=meet.aairavx.com id=meet.aairavx.com] MucClient$2.connected#321: Connected.
2025-01-13 18:22:46.671 INFO: [41] [hostname=meet.aairavx.com id=meet.aairavx.com] MucClient.lambda$getConnectAndLoginCallable$9#646: Logging in.
2025-01-13 18:22:46.732 INFO: [41] [hostname=meet.aairavx.com id=meet.aairavx.com] MucClient$2.authenticated#327: Authenticated, b=false
2025-01-13 18:22:46.732 INFO: [41] [hostname=meet.aairavx.com id=meet.aairavx.com] MucClient$MucWrapper.join#751: Leaving a MUC we already occupy.
rg.jivesoftware.smackx.muc.MultiUserChatException$MucNotJoinedException: Client not currently joined [email protected]
at org.jivesoftware.smackx.muc.MultiUserChat.leave(MultiUserChat.java:769)
at org.jitsi.xmpp.mucclient.MucClient$MucWrapper.leave(MucClient.java:722)
at org.jitsi.xmpp.mucclient.MucClient$MucWrapper.join(MucClient.java:752)
at org.jitsi.xmpp.mucclient.MucClient.joinMucs(MucClient.java:370)
at org.jitsi.xmpp.mucclient.MucClient.lambda$getConnectAndLoginCallable$9(MucClient.java:667)
at org.jitsi.retry.RetryStrategy$TaskRunner.run(RetryStrategy.java:167)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
at java.base/java.lang.Thread.run(Thread.java:1583)
2025-01-13 18:22:51.733 WARNING: [41] [hostname=meet.aairavx.com id=meet.aairavx.com] MucClient.lambda$getConnectAndLoginCallable$9#671: Failed to join the MUCs.
org.jivesoftware.smack.SmackException$NoResponseException: No response received within reply timeout. Timeout was 5000ms (~5s). StanzaCollector has been cancelled. Wa>
at org.jivesoftware.smack.SmackException$NoResponseException.newWith(SmackException.java:124)
at org.jivesoftware.smack.SmackException$NoResponseException.newWith(SmackException.java:104)

@damencho
Copy link
Member

org.jivesoftware.smack.AbstractXMPPConnection.callConnectionClosedOnErrorListener: Connection XMPPTCPConnection[[email protected].>
org.jivesoftware.smack.XMPPException$StreamErrorException: system-shutdown You can read more about the meaning of this stream error at http://xmpp.org/rfcs/rfc6120.ht>
stream:errorReceived SIGTERM</stream:error>
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.parsePackets(XMPPTCPConnection.java:984)
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.access$700(XMPPTCPConnection.java:916)
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader$1.run(XMPPTCPConnection.java:939)
at java.base/java.lang.Thread.run(Thread.java:1583)
2025-01-13 18:22:41.549 WARNING: [41] [hostname=meet.aairavx.com id=meet.aairavx.com] MucClient.lambda$getConnectAndLoginCallable$9#671: Failed to join the MUCs.
org.jivesoftware.smack.SmackException$NotConnectedException: The connection XMPPTCPConnection[[email protected]/Z4lK5gqdRLSp] (0) is no longer connected whi>
stream:errorReceived SIGTERM</stream:error>

This is strange, so when you restarted jibri at the same time you restarted prosody?

What are the logs without restarting prosody at that time?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@saghul @damencho @Harshavardhan77300