Streaming - can I set bit rate?

I am using the public jitsi server to stream pour meeting to youtube.
On the youtube Studio screen I received frequenct notifications that the bitrate is too low:
The stream’s current bit rate (2118.46 Kbps) is lower than the recommended bit rate. We recommend that you use a stream bit rate of 4500 Kbps.

Can I change this?

1 Like

That is network-dependent. It has to do with your available bandwidth, more especially, your upload speed.

Thanks, Freddie.
I have about 50 Mbps upload capacity from the PC on which I am running Jitsi.
Not sure how the data is forwarded to youtube. Is that from my system or from the Jisti server (I am using the public server at
If the latter is the case, would it help to run Jitsi locally on a private server?


What about the specs of the PC - CPU, RAM? Those will also affect bitrate because they determine encoding speed. But yeah, a dedicated (self-hosted) system helps since you won’t have competition from others for the resources.

The PC is only two months old. It has a Gigabyte Z590 Vision motherboard, Intel Core I7 11700 processor (8 cores, 16 Mb cache), 32 Gb RAM and a 2 TB SSD.

I’ll rig up a host using a Dell PowerEdge. It is an older system, but we’ll se how that works.

Hello Freddie,
I’ve installed jitsi with jibri on a Dell PowerEdge R210 with a fresh Ubuntu 22.04. The streaming, however,is not working: I get the message “Live Streaming Unavailable”.
In the jicofo log I see the message “Failed to start a Jibri session, no Jibris available”

Looking at the running processes I see that jibri has been started with:
java -Djava.util.logging.config.file=/etc/jitsi/jibri/ -Dconfig.file=/etc/jitsi/jibri/jibri.conf -jar /opt/jitsi/jibri/jibri.jar --config /etc/jitsi/jibri/config.json
The file “/etc/jitsi/jibri/config.json” does not exist.

For the jibri installation I followed your tutorial (
I could not load java 8, but from the remarks I understand java 11 should work as well.
Any suggestions?

Can you share all jibri logs?

Good morning,
I rebooted my jitsi server this morning and tried to stream to youtube. The logs are attached (server name changed to

jibri.log (3.8 KB)
jicofo.log (13.4 KB)
jvb.log (8.1 KB)

Are you able to host a 3-party call?
If you’re behind a router, is port 5222 properly forwarded?

Also, share your jibri.conf.

Hello Freddie,
I have not tried to run a three party call using my jitsi server yet. Will try that later today.
I am behind a firewall, but no nat. The jitsi server has its own public IP address, so no port forwarding is needed.
I will try and open the firewall temporarily to check if that makes a difference.

jibri.conf.txt (3.5 KB)

jibri {
jibri {
// A unique 

Is this a copy-paste error? If no, the syntax is wrong.

Well spotted, emrah.
Don’t know how that happened. I’ve changed it and rebooted the system.
It seems to go a bit further know, but still does not record or stream.
I’ve attached the logs from after the boot.

jvb.log.txt (9.2 KB)
jitsi_2.log.txt (15.5 KB)
Jicofo_2.log.txt (17.8 KB)

Prosody is still not able to connect. Do you have something else running on port 5222? Check with netstat.

I don’t think so. Here’s the output from netstat and lsof:

root@jitsi:~# netstat -tulpn | grep 5222
tcp 0 0* LISTEN 1883/lua5.2
tcp6 0 0 :::5222 :::* LISTEN 1883/lua5.2

root@jitsi:~# lsof -i -P -n | grep 5222
java 652 jicofo 115u IPv6 18378 0t0 TCP> (ESTABLISHED)
java 829 jibri 58u IPv6 30317 0t0 TCP> (ESTABLISHED)
java 1880 jvb 130u IPv6 28988 0t0 TCP> (ESTABLISHED)
lua5.2 1883 prosody 8u IPv4 30312 0t0 TCP *:5222 (LISTEN)
lua5.2 1883 prosody 9u IPv6 30313 0t0 TCP *:5222 (LISTEN)
lua5.2 1883 prosody 14u IPv4 28110 0t0 TCP> (ESTABLISHED)
lua5.2 1883 prosody 15u IPv4 31885 0t0 TCP> (ESTABLISHED)
lua5.2 1883 prosody 16u IPv4 31887 0t0 TCP> (ESTABLISHED)

Looking at the lsof output - it appears jibri is using ipv6. I only use ipv4.

Sofar I have not been able to get streaming using jibri to work.
I experimented with streaming the jitsi screen using OBS, which seems to work fine.
So - at least for the time being - I am abandoning the jibri route.

Thanks for the assistance.