You beat me to it, @bbaldino, I was just typing the same thing. I think you might have made a change in your xorg display settings @anindita.sadhukhan
Capture area 1280x720 at position 0.0 outside the screen size 640x480
Hi Please refer the attached file, this is the xorg config file of that server. I have changed the extension to txt for uploading purpose. In server it is xorg-video-dummy.conf
Thanks,xorg-video-dummy.txt (6.2 KB)
Hi, did you get any chance to look into this attached config file?
Hi, I am having trouble configuring jibri… Can you help me configuring it? I am will to pay for it. Thanks
● jibri.service - Jibri Process
Loaded: loaded (/etc/systemd/system/jibri.service; enabled; vendor preset:>
Active: failed (Result: exit-code) since Tue 2021-03-02 08:17:45 UTC; 9min>
Process: 3080 ExecStart=/opt/jitsi/jibri/launch.sh (code=exited, status=1/F>
Main PID: 3080 (code=exited, status=1/FAILURE)
Please Help me for this issue
Not enough information. But still I would go ahead and guess. java version may be an issue. It needs to be java8.
And I believe you have already gone through the post.
I am new to this service Could You please provide me docs or videos about jitsi and jibri installation in aws
Thanks in advance
jitsi: Self-Hosting Guide - Debian/Ubuntu server · Jitsi Meet Handbook
jibri: GitHub - jitsi/jibri: Jitsi BRoadcasting Infrastructure
Following these you should be able to install both. There are videos on youtube too.
Or you may use this GitHub - pregalla/jitsi: Installer for Jitsi, Jigasi, and Jibri or some other script.
Dear emrah,
followed your script, installation was smoothly, jibri recording is working, thank you VERY much!
I was just confused about the requirement of your script for a turn server domain name (this is not mentioned in other installation schemas like this one: Set Up Jibri for Jitsi Recording/Streaming – Nerd on the Street
as your script is not allowing to set same name as meet server I just added fictional name (kind of name extension of my real meet server) and installation also worked, including the recording with jibri.
I am using server at vultr.com and follow installation steps from forum/internet (I am not too advanced).
Is there any shortcoming of adding any domain name for turn server?
kind regards, MS
I’m not sure if I understand your question correctly. Do you want to change the host address (FQDN) used for TURN?
I apologise in advance, but most probably/for sure I don´t understand the purpose of a TURN server in general (just read in internet that it is required if server is behind firewall or NAT).
If I have my domain for my Jitsi Meet server “meet.jitsiserver.com” (and also the letsencrypt script makes the certificate for it) - which domain name I should set for the turn server?
(I am using vultr.com for my virtual Jitsi Meet servers (so far always working great but now would like to add Jibri functionality). Using Vultr I provide the host address (FQDN) in beginning before installation the own droplet (e.g. Debian 10) - how I handle the “turn server” if I use your script?
(so far adding a turn server was not required - or it is done automatically in the background?)
Not the server, the client… If the client is behind a restricted firewall and if it cannot connect to the server using UDP/10000 or to the other peer then TURN solves this issue
TURN and Jitsi run behind Nginx and Nginx can only route the requests correctly if they use different domain names. Any domain name which points to your server can be used for TURN but it must be different than the one which Jitsi uses
1 Like
thank you VERY much for your time and your clear answer:
“accidentally” I have done the same (giving different domain name for TURN than for Jitsi), therefore jibri is working fine so far (still have to test it with colleagues)
WARNING: [27] org.jitsi.xmpp.mucclient.MucClient.log() [MucClient id=meet.mashvirtual.info hostname=meet.mashvirtual.info] error connecting
org.jivesoftware.smack.SmackException$ConnectionException: The following addresses failed: ‘meet.mashvirtual.info:5222’ failed because: meet.mashvirtual.info/182.72.176.216 exception: java.net.SocketTimeoutException: connect timed out
at org.jivesoftware.smack.SmackException$ConnectionException.from(SmackException.java:278)
at org.jivesoftware.smack.tcp.XMPPTCPConnection.connectUsingConfiguration(XMPPTCPConnection.java:619)
at org.jivesoftware.smack.tcp.XMPPTCPConnection.connectInternal(XMPPTCPConnection.java:902)
at org.jivesoftware.smack.AbstractXMPPConnection.connect(AbstractXMPPConnection.java:383)
at org.jitsi.xmpp.mucclient.MucClient.lambda$getConnectAndLoginCallable$7(MucClient.java:668)
at org.jitsi.retry.RetryStrategy$TaskRunner.run(RetryStrategy.java:193)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
Dear emrah,
I have installed on Ubuntu 20.04 LTS Jitsi+Jibri with your jitsi-jibri-installer:
so far everything working nicely, recording tested so far (with 2 participants on 4 CPU machine) is running smoothly, thank you VERY much.
one question:
checking Java version on this installation yielded version 11, but not 8 (which was described several times in the forum to be essentially required for Jibri, because Java >8 causes problems):
jitsiadmin@server:~$ java -version
openjdk version “11.0.10” 2021-01-19
OpenJDK Runtime Environment (build 11.0.10+9-Ubuntu-0ubuntu1.20.04)
OpenJDK 64-Bit Server VM (build 11.0.10+9-Ubuntu-0ubuntu1.20.04, mixed mode, sha ring)
Question: do I need to install Java 8 to be on save side or is current version ok?
thanks a lot!
MS
(I have to record several interviews (each >1 hour) this week and aware that interruption of recording leads to corrupted mp4 files, which cannot be used)
The installer installs both versions (Java 11 and Java 8). The default one is Java 11 and Java appalications use this one as a default.
But jibri uses Java 8.
1 Like
Thank you very much!
very brief (hypothetical) questions:
- a new stable version will be released soon (what I have hear in TheCall last Monday): will the update affect functionality of Jibri-Java8 ?
- similar: In case I would change Jitsi repository to from stable to testing: will functionality jibri-java8 be retained after updating?
AFAIK the new coming Jibri will run with Java 11 too. So you can use Java 8 or Java 11 without any problem.
Thank you!!!