Video recording is broken or not working

I have an issue with my video recording on my local server. Any help will be appreciated.
Jitsi connection is not working on all server for and I don’t know why.

What exactly is the problem you’re having?

There few issues 1. People log in to wrong rooms… 2. the video show this error.

Currently we have 1 jitsi and 2 jibri server: They only support few number of users. Is there a way to scale and have more users? What are the current number of users on local jitsi server?. We are a non-profit that teaches women about tech. Any help you can give will go along to assist us.

How many simultaneous meetings and participants do you need?

120 I am willing to pay to develop a scaling system. May using container technology.

meetings or participants?

120 meetings as well as participants.

What will be the maximum number of participants in a single meeting?

It looks like there are two separate issues here:

  1. Jibri is not recording
  2. Questions around the maximum number of people/conferences you can have on your server

For the first part, can you share your jibri.conf file? 7 out of 10 times, that’s usually where the problem is.

And for the second part, what are your server specifications (CPU, memory, bandwidth e.t.c…)?

jitsi/jibri1 is aws t2 medium for the two and jibri2 is aws t1 micro

jibri.con file

// NOTE: this is a SAMPLE config file, it will need to be configured with
// values from your environment

// Where recording files should be temporarily stored

// The path to the script which will be run on completed recordings
“finalize_recording_script_path”: “”,
“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”: [
// The xmpp domain we’ll connect to on the XMPP server
“xmpp_domain”: “”,
// Jibri will login to the xmpp server as a privileged user
“control_login”: {
// The domain to use for logging in
“domain”: “”,
// The credentials for logging in
“username”: “jibri”,
“password”: “Jibriss”
// 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”: “”,
“room_name”: “JibriBrewery”,
“nickname”: “jibri-nickname”
// 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”: “”,
“username”: “recorder”,
“password”: “jibrirecorderp”
// 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”: “conference.”,
// 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”

Same as above.

Next time, please state the exact stats, when requested.

I looked up AWS t2 medium (2 vCPUs, 4GB RAM) and AWS ti micro (1 vCPU, 1GB RAM) and these are markedly insufficient resources for Jibri. So that’s your first problem. Jibri requires about 4CPUs and 8GB or RAM, although you may get away with half of that (no guarantees). There is however no way you can run Jitsi AND Jibri on 2vCPUs and 4GB of RAM. Same goes for Jibri alone on 1vCPU and 1GB RAM).

The other issues are moot because without the right infrastructure, it’s already a non-starter. But just for academic purposes, it’s worth noting that what you posted looks more like config.json configuration (which is being deprecated); Jibri.conf has a different format.

So yes, you’ll need better infrastructure to even start the process.

1 Like

I have been running it for over 5 months already I noticed the no recording. That stirred me to find out what is going on.

Are you saying it was working for 5 months OR you never recorded for 5 months and when you tried now you noticed the issue?

Yes! I have been recording all this time although difficult at times. But now the error is there and I am not able to record now.

I don’t know how you managed to get Jibri to record at all with that spec, so that’s interesting on its own. But check out this tutorial for tips on how to solve your issue (outside insufficient resources) - TUTORIAL: Jibri Overview, Troubleshooting Tips & Tricks - Solve your Jibri Problems, Quickly!