Chrome Jitsi

Posted on  by admin

We recommend following the quick-install document. The current document describes the steps that are needed to install a working deployment, but steps are easy to mess up, and the debian packages are more up-to-date, where this document is sometimes not updated to reflect latest changes.

This describes configuring a server jitsi.example.com on a Debian-based distribution.
For other distributions you can adapt the steps (especially changing the dependencies package installations (e.g. for nginx) and paths accordingly) so that it matches your host's distribution.
You will also need to generate some passwords for YOURSECRET1, YOURSECRET2 and YOURSECRET3.

There are also some complete example config files available, mentioned in each section.

A simple extension that allows you to schedule Jitsi Meetings and stream your desktop into Jitsi conferences. Jitsi Meetings Extension for meet.runsimple.cloud. Needed for Google Chrome. Jitsi Desktop - Open Source Video Calls and Chat Secure video calls, conferencing, chat, desktop sharing, file transfer, support for your favorite OS, and IM network. All this, and more, in Jitsi - the most complete and advanced open source communicator. You can turn on end-to-end encryption (e2ee) as long as you are using Jitsi Meet on a browser with support for insertable streams. Currently this means any browser based on Chromium 83 and above, including Microsoft Edge, Google Chrome, Brave and Opera. You may also use our Electron client, which supports it out of the box. However, I’ve read that Chrome is better suited for Jitsi. But I cannot get it to work on Chrome at all! The first time I open a meeting, the browser asks me in a popup for permission to use my webcam and microphone, I click on accept, and then nothing happens. The meeting doesn’t start.

There are additional configurations to be done for a scalable installation.

Jitsi

Chrome Jitsi Download

Network description

This is how the network looks:

Install prosody

Configure prosody

Chrome

Add config file in /etc/prosody/conf.avail/jitsi.example.com.cfg.lua :

  • add your domain virtual host section:
Chrome its cycle time decade
  • add domain with authentication for conference focus user:
  • add focus user to server admins:
  • and finally configure components:

Add link for the added configuration

Generate certs for the domain:

Add auth.jitsi.example.com to the trusted certificates on the local machine:

Note that the -f flag is necessary if there are symlinks left from a previous installation.

If you are using a JDK package not provided by Debian, as the ones from adopjdk, you should also make your JDK aware of the new debian certificate keystore replacing or linking the JDK cacerts. Example, if you use JDK from adoptjdk:

Create conference focus user:

Restart prosody XMPP server with the new config

Install Nginx

Add a new file jitsi.example.com in /etc/nginx/sites-available (see also the example config file):

Add link for the added configuration

Install Jitsi Videobridge

Visit https://download.jitsi.org/jitsi-videobridge/linux to determine the current build number, download and unzip it:

Install JRE if missing:

NOTE: When installing on older Debian releases keep in mind that you need JRE >= 1.7.

Create ~/.sip-communicator/sip-communicator.properties in the home folder of the user that will be starting Jitsi Videobridge:

Start the videobridge with:

Or autostart it by adding the line in /etc/rc.local:

Install Jitsi Conference Focus (jicofo)

Install JDK and Maven if missing:

Chrome jitsi no sound

NOTE: When installing on older Debian releases keep in mind that you need JDK >= 1.7.

Clone source from Github repo:

Chrome

Build the package.

Run jicofo:

Deploy Jitsi Meet

Checkout and configure Jitsi Meet:

NOTE: When installing on older distributions keep in mind that you need Node.js >= 12 and npm >= 6.

Edit host names in /srv/jitsi-meet/config.js (see also the example config file):

Verify that nginx config is valid and reload nginx:

Running behind NAT

Jitsi Videobridge can run behind a NAT, provided that both required ports are routed (forwarded) to the machine that it runs on. By default these ports are TCP/4443 and UDP/10000.

If you do not route these two ports, Jitsi Meet will only work with video for two people, breaking upon 3 or more people trying to show video.

TCP/443 is required for the webserver which can be running on another machine than the Jitsi Videobrige is running on.

Chrome Jitsi Web

The following extra lines need to be added to the file ~/.sip-communicator/sip-communicator.properties (in the home directory of the user running the videobridge):

Hold your first conference

You are now all set and ready to have your first meet by going to http://jitsi.example.com

Enabling recording

Jibri is a set of tools for recording and/or streaming a Jitsi Meet conference.