jitsi
Recording option in jitsi meet mobile view
What happened?
In jitsi meet, recording option is not visible for mobile view. How can i enable the recording option
Platform
- [x] 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
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.
Yes in desktop Web version it is working, but in mobile view even recording icon also not displayed.
even in 3dots (more icon) also there is no recording button but in desktop is was displaying
now i got that recording icon but it was not starting getting error
UnhandledPromiseRejection: [object Element] StackTrace: undefined
bu the jibri server is in active only
Hard to figure out from a screenshot snippet whether it connected to the control room.
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
Seems you don't have any shards configured in your config. Share jibri config and mask any private information.
{
"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"
}
}
}
The format of the config is wrong: https://github.com/jitsi/jibri?tab=readme-ov-file#config-files
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
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:error
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?