Recording Failed To Start After Changing Room Names Into Specific Names

Hi all,
We use Jitsi and Jibri in our application on seperate servers. Our main goal is opening rooms with formatted room names. We also want to disable welcome page of jitsi, and if any request coming to this page should be redirected to another page.In order to do that we followed following practices;

  1. On domain.com-config.js file, we set enableWelcomePage value = false. After that, Jitsi started to open random room name.

  2. On domain.com.conf nginx file, we added location part with som regex,

location ~ "someregexishere.+$" {
        try_files $uri @root_path;
    }

After these changes, random pages returns 404, this is tolarable for us. We are able to open room names which matches with our regex. But the problem is, after implementing regex on ngix conf file, jibri started to fail to record. Here are some logs of jibri.log0.txt

2022-09-22 08:52:37.729 INFO: [5780] org.jitsi.jibri.selenium.pageobjects.HomePage.log() Visiting url https://domain.com
2022-09-22 08:52:38.582 INFO: [5780] org.jitsi.jibri.selenium.pageobjects.HomePage.log() Waited 853ms for driver to load page
2022-09-22 08:52:38.609 INFO: [5780] org.jitsi.jibri.selenium.pageobjects.CallPage.log() Visiting url https://domain.com/roomname>
2022-09-22 08:52:38.653 INFO: [5780] org.jitsi.jibri.selenium.pageobjects.CallPage.log() Waited 43.7ms for driver to load page
2022-09-22 08:52:38.660 FINE: [5780] org.jitsi.jibri.selenium.pageobjects.CallPage.log() Not joined yet: APP is not defined

Any help would be apprecitated.
Thanks.

Did you check Nginx logs for jibri requests which may conflict with your regex?

1 Like

Well you were right. We figured out that, regex was case-sensitive, that’s why recording was failing. For now, we don’t fail in recording, but we still see request with random random name. How is it possible?