jibri
jibri copied to clipboard
jitsi
jibri configuration file examples and support recording failed to start
I followed the instructions on https://github.com/jitsi/jibri on ubuntu 18.04 LTS with a working jitsi installation, but I can not get recording to work and it fails with "recording failed to start". I can not see error messages in the log files.
/etc/jitsi/jibri/config.json
/etc/jitsi/jicofo/sip-communicator.properties
/etc/prosody/prosody.cfg.lua
/etc/jitsi/meet/meet.example.org-config.js
tail --follow /var/log/jitsi/jibri/log.0.txt 2020-03-27 17:30:21.110 INFO: [19] org.jitsi.xmpp.mucclient.MucClient.log() [MucClient id=meet.example.org hostname=meet.example.org] connected 2020-03-27 17:30:21.246 INFO: [19] org.jitsi.xmpp.mucclient.MucClient.log() Joined MUC: [email protected]
Would somebody be able to help me out, can I run jibri and jitsi on the same server without problems?
Thank you for taking a look, I manage to get some error messages:
config.json.txt jicofo.log log.0.txt meet.example.org-config.js.txt prosody.cfg.lua.txt sip-communicator.properties.txt
It looks like it times out trying to connect to jitsi? The bellow commands connect fine as root user on the server: telnet meet.examlpe.org 5222 telnet meet.examlpe.org 443
2020-03-27 19:18:13.315 FINE: [46] org.jitsi.jibri.selenium.pageobjects.CallPage.visit() Visiting url https://meet.example.org/test02#config.iAmRecorder=true&config.externalConnectUrl=null&config.startWithAudioMuted=true&config.startWithVideoMuted=true&interfaceConfig.APP_NAME="Jibri"&config.analytics.disabled=true&config.p2p.enabled=false 2020-03-27 19:18:44.333 SEVERE: [46] org.jitsi.jibri.selenium.pageobjects.CallPage.visit() Timed out waiting for call page to load
You need to replace the meet.example.org values in the config with the ones for your deployment.
You need to replace the
meet.example.orgvalues in the config with the ones for your deployment.
I replaced the name of my deployment with example for privacy reasons so in my config all the meet.examples.org are meet.workingdomaindeployment.org.
In that case, Jibri is still unable to reach your server so it's timing out when trying to load the page.
