Jibri browser isn't hidden


I’ve installed jitsi+jibri for recording on a local server using the docker setup (version stable-4548-1). When I press the record button, I get the audio message that the recording has started but the jibri browser appears visible in the meeting. The video is correctly recorded but with the jibri “participant” appearing both in the video and in the meeting/room.

Here is part of the config.js:

hiddenDomain: ‘recorder.redacted.com’,

And here is the urls that the jibri browser is using (from the jibri logs):


Any clues on how to further debug the issue?

Nuno Fernandes


I encountered the same problem. solved now.
I had not correctly registered the jibri accounts as indicated here https://github.com/jitsi/jibri/blob/master/README.md

Setup the two accounts jibri will use.
prosodyctl register jibri auth.yourdomain.com jibriauthpass
prosodyctl register recorder recorder.yourdomain.com jibrirecorderpass
hoping it will help you.


First of all, thank you so much for the feedback.

I checked and I do have the accounts created:

-rw-r----- 1 prosody prosody 217 May 24 14:51 /config/data/auth%2eredacted%2ecom/accounts/focus.dat
-rw-r----- 1 prosody prosody 217 May 24 14:51 /config/data/auth%2eredacted%2ecom/accounts/jibri.dat
-rw-r----- 1 prosody prosody 217 May 24 14:51 /config/data/auth%2eredacted%2ecom/accounts/jvb.dat
-rw-r----- 1 prosody prosody 217 May 24 14:51 /config/data/recorder%2eredacted%2ecom/accounts/recorder.dat

Any other ideas?


Did you add the hiddendomain in /etc/jitsi/meet/meet.myfirewall.org-config.js ?


It seems to be this, right?

# curl -s https://redacted.com/config.js|grep -i hiddenDomain:
hiddenDomain: 'recorder.redacted.com',

yup… can you please let me know which file it is? it needs to be the one in the directory i mentioned


As I’m using docker based version (from https://github.com/jitsi/docker-jitsi-meet), the file is located at /config/config.js inside the docker image.

Hope that helps,
Nuno Fernandes

sorry, i’m not familiar with Docker install.

@Nuno_Fernandes Could you able to solve this issue?

Yes… I was able to fix it.

As far as I can tell, the issue was in jibri container (browser) accessing the web container via the external (public ip) endpoint. Because jibri accessed the external endpoint, it also used an external IP and that connection arriving on the web container from a public IP, made the jibri user appear on the web interface.

Once I added a mechanism to update /etc/hosts on the jibri container to map redacted.com to the internal (private ip) of the web container, it worked.

Thanks for prompt response.
I am also facing the same issue . I tried almost all the possible workarounds to get it fixed.
In my case, I have 1 instance of web container(Jitsi-meet) and another instance of jibri container, both are running on 2 different hosts . I also tried your solution but didn’t work.

instance 1--------- jitsi-meet-------privateip=xxx.xxx.xx
instance 2---------jibri------------/etc/hosts file has below entry
xxx.xxx.xx mydomainname

is that what you have done?
I appreciate your response.

Can you check the jitsi-meet web container logs and see if the requests are arriving with a private ip?

I am receiving the request from Jibri container’s Private IP.