Hi there,
We have an installation of Jibri on an ubuntu instance, when it starts up we get these logs:
2021-01-14 11:00:26.624 INFO: [1] org.jitsi.jibri.Main.handleCommandLineArgs() Jibri run with args [--config, /etc/jitsi/jibri/config.json]
2021-01-14 11:00:26.709 INFO: [1] org.jitsi.jibri.Main.setupLegacyConfig() Checking legacy config file /etc/jitsi/jibri/config.json
2021-01-14 11:00:27.309 INFO: [1] org.jitsi.jibri.Main.loadConfigFromFile() Parsed legacy config:
JibriConfig(jibriId=null, recordingDirectory=null, singleUseMode=null, enabledStatsD=null, finalizeRecordingScriptPath=null, xmppEnvironments=null)
2021-01-14 11:00:27.736 INFO: [1] org.jitsi.jibri.webhooks.v1.JwtInfo.Companion.fromConfig() got jwtConfig: {}
2021-01-14 11:00:27.737 INFO: [1] org.jitsi.jibri.webhooks.v1.JwtInfo.Companion.fromConfig() Unable to create JwtInfo: com.typesafe.config.ConfigException$Missing: reference.conf @ jar:file:/opt/jitsi/jibri/jibri.jar!/reference.conf: 52: No configuration setting found for key 'signing-key-path'
2021-01-14 11:00:27.754 INFO: [1] org.jitsi.jibri.Main.main() Using port 3333 for internal HTTP API
2021-01-14 11:00:27.781 FINE: [16] org.jitsi.jibri.webhooks.v1.WebhookClient.invokeSuspend() Updating 0 subscribers of status
2021-01-14 11:00:28.110 INFO: [1] org.jitsi.jibri.api.xmpp.XmppApi.updatePresence() Jibri reports its status is now JibriStatus(busyStatus=IDLE, health=OverallHealth(healthStatus=HEALTHY, details={})), publishing presence to connections
2021-01-14 11:00:28.123 INFO: [1] org.jitsi.jibri.Main.main() Using port 2222 for HTTP API
2021-01-14 11:01:27.750 FINE: [16] org.jitsi.jibri.webhooks.v1.WebhookClient.invokeSuspend() Updating 0 subscribers of status
2021-01-14 11:02:27.750 FINE: [16] org.jitsi.jibri.webhooks.v1.WebhookClient.invokeSuspend() Updating 0 subscribers of status
2021-01-14 11:03:06.661 INFO: [35] org.jitsi.jibri.api.http.internal.InternalHttpApi.invokeSuspend() Jibri gracefully shutting down
We have a dockerized Jicofo on another instance, when we try and record it gives us the “No jibris available” error. It doesn’t receive anything in the logs when Jibri starts up. We expecting at least to see that a connection was made from Jibri to Jicofo.
We have checked that all our ports are open.
Here’s our Jibri config file:
{
environments = [
{
// A user-friendly name for this environment
name = "prod environment"
// A list of XMPP server hosts to which we'll connect
xmpp-server-hosts = [ "OUR_DOMAIN" ]
// The base XMPP domain
xmpp-domain = "OUR_DOMAIN"
// The MUC we'll join to announce our presence for
// recording and streaming services
control-muc {
domain = "internal.auth.OUR_DOMAIN"
room-name = "JibriBrewery"
nickname = "jibrinickname"
}
// The login information for the control MUC
control-login {
domain = "OUR_DOMAIN"
username = "jibri"
password = "JIBRI_PASS"
}
// An (optional) MUC configuration where we'll
// join to announce SIP gateway services
sip-control-muc {
domain = "internal.auth.wprod.sendit.media"
room-name = "JibriBrewery"
nickname = "jibrinickname"
}
// The login information the selenium web client will use
call-login {
domain = "OUR_DOMAIN"
username = "recorder"
password = "RECORDER_PASS"
}
// The value we'll strip from the room JID domain to derive
// the call URL
strip-from-room-domain = ""
// How long Jibri sessions will be allowed to last before
// they are stopped. A value of 0 allows them to go on
// indefinitely
usage-timeout = 1 hour
// Whether or not we'll automatically trust any cert on
// this XMPP domain
trust-all-xmpp-certs = true
}
]
}