Jibri Issue 5765-1 && 5390-3

Yeah that resolves to the web container with the Docker internal DNS.

Ok… @tusharsonawane do you have any way of validating that it’s resolving correctly?

@bbaldino

I installed the latest release 5765-1 ( docker version )

Integrated jibri.yaml , copied .asoundrc and made changes in config.js like

hiddenDomain: recorder.meet.jitsi and fileRecordingsEnabled: true

I still get the same error

2021-04-25 18:04:25.515 FINE: [112] org.jitsi.jibri.selenium.pageobjects.CallPage.log() Not joined yet: Cannot read property 'isJoined' of undefined
2021-04-25 18:04:25.520 SEVERE: [112] org.jitsi.jibri.selenium.pageobjects.CallPage.log() Timed out waiting for call page to load
2021-04-25 18:04:25.520 INFO: [112] org.jitsi.jibri.selenium.JibriSelenium.log() Transitioning from state Starting up to Error: FailedToJoinCall SESSION Failed to join the call
2021-04-25 18:04:25.520 INFO: [112] org.jitsi.jibri.service.impl.FileRecordingJibriService.log() File recording service transitioning from state Starting up to Error: FailedToJoinCall SESSION Failed to join the call
2021-04-25 18:04:25.520 INFO: [112] org.jitsi.jibri.api.xmpp.XmppApi.log() Current service had an error Error: FailedToJoinCall SESSION Failed to join the call, sending error iq <iq to='jibribrewery@internal-muc.meet.jitsi/focus' id='Chm6w-80' type='set'><jibri xmlns='http://jitsi.org/protocol/jibri' status='off' failure_reason='error' should_retry='true'/></iq>

Here are the logs

Sorry, but I don’t have any other information for you. Jibri is trying to validate that it has joined the call by executing APP.conference._room.isJoined(); in the browser (see here). There are a number of reasons why that may be failing (page not resolving, auth problems, etc.). You’ll have to try and validate each of those things (I would start by trying to verify that Jibri is able to load the page correctly) to try and figure out what’s going wrong.