Jibri: cannot read property isJoined of undefined, Error: FailedToJoinCall SESSION Failed

Hi, I am using jitsi docker installation and using selft signed for meet.jitsi domain and my own cert for public domain. While starting recording service fails with ‘Error: FailedToJoinCall SESSION Failed’ ending error iq

I checked nginx log for web:

/xmpp-websocket path send https 403

172.29.0.1 - - [21/Dec/2020:18:16:05 +0000] “GET /xmpp-websocket?room=meet2 HTTP/1.1” 403 284 “-” “Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.97 Safari/537.36”

Is this the reason of error? or How can I solve it?

Please, don’t tag people when creating a post for help, unless they’re already assisting you with the issue.

Per your problem, can you share your jibri.conf configuration?

Sure, these are default files for docker installation inside jibri container.

jibri.conf:

jibri {
}

config.json:

{
“recording_directory”:"/config/recordings",
// The path to the script which will be run on completed recordings
“finalize_recording_script_path”: “/config/finalize.sh”,
“xmpp_environments”: [
{
// A friendly name for this environment which can be used
// for logging, stats, etc.
“name”: “prod environment”,
// The hosts of the XMPP servers to connect to as part of
// this environment
“xmpp_server_hosts”: [
“xmpp.meet.jitsi”
],
“xmpp_domain”: “meet.jitsi”,
// Jibri will login to the xmpp server as a privileged user
“control_login”: {
“domain”: “auth.meet.jitsi”,
// The credentials for logging in
“username”: “jibri”,
“password”: “9e32a4a060feb4d74eca5c93daa32aad”
},
// Using the control_login information above, Jibri will join
// a control muc as a means of announcing its availability
// to provide services for a given environment
“control_muc”: {
“domain”: “internal-muc.meet.jitsi”,
“room_name”: “jibribrewery”,
// MUST be unic for every instanse
“nickname”: “jibri-instanse-527257484”
},
// All participants in a call join a muc so they can exchange
// information. Jibri can be instructed to join a special muc
// with credentials to give it special abilities (e.g. not being
// displayed to other users like a normal participant)
“call_login”: {
“domain”: “recorder.meet.jitsi”,
“username”: “recorder”,
“password”: “01284f9220f76fafcd00e3aab04e9a91”
},
// When jibri gets a request to start a service for a room, the room
// jid will look like:
// roomName@optional.prefixes.subdomain.xmpp_domain
// We’ll build the url for the call by transforming that into:
// https://xmpp_domain/subdomain/roomName
// So if there are any prefixes in the jid (like jitsi meet, which
// has its participants join a muc at conference.xmpp_domain) then
// list that prefix here so it can be stripped out to generate
// the call url correctly
“room_jid_domain_string_to_strip_from_start”: “muc.”,
// The amount of time, in minutes, a service is allowed to continue.
// Once a service has been running for this long, it will be
// stopped (cleanly). A value of 0 means an indefinite amount
// of time is allowed
“usage_timeout”: “0”
}
]
}

Okay, you’re still using config.json; this will be a problem. The new jibri relies on jibri.conf and the configuration is slightly difference. Check out this post on how to configure jibri.conf (look at the sample configuration for jibri.conf) - TUTORIAL - How to Install the NEW JIBRI

Also, I just read over your post again and you mentioned using a self-signed certificate. Jibri does not work with self-signed certificates. You will need to add --ignore-certificate-errors to the flags in your jibri.conf.

1 Like

Thanks for your reply. I am using jitsi docker. If you read the thread https://github.com/jitsi/docker-jitsi-meet/issues/240, you will find something "Actually, I think a self-signed already works, that’s how I tested it. I’ll try to fix this tomorrow by having a self-signed cert for meet.jitsi’ by @saghul. Thats why I tested with self signed cert.

Anyway I will try the link TUTORIAL - How to Install the NEW JIBRI