Setup the Jitsi-meet and Jibri on two separate server following the instruction as per below documents
# Jitsi Meet quick install
This document describes the required steps for a quick Jitsi Meet installation on a Debian based GNU/Linux system. Debian 8 (Jessie) or later, and Ubuntu 14.04 or later are supported out-of-the-box.
Debian Wheezy and other older systems may require additional things to be done. Specifically for Wheezy, [libc needs to be updated](http://lists.jitsi.org/pipermail/users/2015-September/010064.html).
Also note that a recent default Ubuntu installation has only the `main` repository enabled, and Jitsi Meet needs packages from `universe`. Check your `/etc/apt/sources.list` file, and if `universe` is not present refer to [Ubuntu's documentation](https://help.ubuntu.com/community/Repositories/Ubuntu) on how to enable it. (Usually it amounts to copying the `main` lines and changing to `universe`.)
N.B.:
a.) All commands are supposed to be run by root. If you are logged in as a regular user with sudo rights, please prepend ___sudo___ to each of the commands.
b.) You only need to do this if you want to ___host your own Jitsi server___. If you just want to have a video conference with someone, use https://meet.jit.si instead.
## Basic Jitsi Meet install
### Add the repository
```sh
echo 'deb https://download.jitsi.org stable/' >> /etc/apt/sources.list.d/jitsi-stable.list
wget -qO - https://download.jitsi.org/jitsi-key.gpg.key | apt-key add -
This file has been truncated. show original
Jicofo log file show Unable to find an available Jibri, can’t start error.
Please help.[jibri.log.1.txt (603 Bytes) jicofo.log (5.0 KB) ](http://)
Please attach Jibri and Jicofo logs.
Here are my jibri and jicofo log files.
jibri.log.1.txt (603 Bytes) jicofo.log (5.0 KB)
Hm, that Jibri log doesn’t actually appear to be a Jibri log, it’s a capture of some bash output? Also, jibri.log.0.txt
will be the most recent one.
It’s pretty much laid out there, it’s an xmpp auth exception. You might try setting always_trust_certs
in the config to see if that fixes it (though you may not want that long term). But otherwise you should be able to google that error and get it sorted, it’s not really a Jibri-specific thing.
@bbaldino plz can you let me know in which config i suppose to put it?
nfc
April 22, 2020, 7:29pm
#10
I have the same problem that charanv had, I’ll post the error in the jibri log so other people can see it. Since the image of the log is very difficult to read
org.jitsi.xmpp.mucclient.MucClientManager.log() Failed to initialize and start a MucClient:
org.jivesoftware.smack.sasl.SASLErrorException: SASLError using SCRAM-SHA-1: not-authorized
1 Like