§2024-08-31
Jitsi by Archlinux Wiki is a set of open-source projects that allows you to easily build and deploy secure videoconferencing solutions. At the heart of Jitsi are Jitsi Videobridge and Jitsi Meet, which let you have conferences on the internet, while other projects from the community enable other features such as audio, dial-in, recording, and simulcasting.
試作機器： n2Jammy.yushei.com.tw, running ubuntu jammy
$ curl https://download.jitsi.org/jitsi-key.gpg.key | sudo sh -c 'gpg --dearmor > /usr/share/keyrings/jitsi-keyring.gpg'
$ echo 'deb [signed-by=/usr/share/keyrings/jitsi-keyring.gpg] https://download.jitsi.org stable/' | sudo tee /etc/apt/sources.list.d/jitsi-stable.list > /dev/null
$ sudo apt-get -y install jitsi-meet
Package configuration
┌─────────────────────┤ Configuring jitsi-videobridge2 ├──────────────────────┐
│ The value of the domain that is set in the Jitsi Videobridge installation. │
│ │
│ The domain of the current installation (e.g. meet.jitsi.com): │
│ │
│ n2Jammy.yushei.com.tw______________________________________________________ │
│ │
│ <Ok> │
│ │
└─────────────────────────────────────────────────────────────────────────────┘
Package configuration
┌─────────────────────────────────────────────────────────────────┤ Configuring jitsi-meet-web-config ├──────────────────────────────────────────────────────────────────┐
│ │
│ │
│ Jitsi Meet requires an SSL certificate. This installer can generate one automatically for your using "Let’s Encrypt". This is the recommended and simplest option for │
│ most installations. │
│ │
│ In the event you need to use a certificate of your own, you can configure its location which defaults to /etc/ssl/--domain.name--.key for the key and │
│ /etc/ssl/--domain.name--.crt for the certificate. │
│ │
│ If you are a developer and are only looking for a quick way to test basic Jitsi Meet functionality then this installer can also generate a self-signed certificate. │
│ │
│ SSL certificate │
│ │
│ Let's Encrypt certificates │
│ I want to use my own certificate │
│ Generate a new self-signed certificate │
│ │
│ │
│ <Ok> │
│ │
└────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘
Package configuration
┌───────────────────────────────────────────────────────────────┤ Configuring jitsi-meet-web-config ├────────────────────────────────────────────────────────────────┐
│ To successfully issue Let's Encrypt certificates: │
│ │
│ You need a working DNS record pointing to this machine(for hostname n2Jammy.yushei.com.tw)" │
│ │
│ You need to agree to the ACME server's Subscriber Agreement (https://letsencrypt.org/documents/LE-SA-v1.1.1-August-1-2016.pdf) by providing an email address for │
│ important account notifications. │
│ │
│ We will use the email for creating your JaaS (Jitsi as a Service) account if that option was selected. │
│ │
│ Enter your email: │
│ │
│ rai.sousuke@mac.com_______________________________________________________________________________________________________________________________________________ │
│ │
│ <Ok> │
│ │
└────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘
Package configuration
┌─────────────────────────────────────────────────────────────┤ Configuring jitsi-meet-web-config ├─────────────────────────────────────────────────────────────┐
│ │
│ You can easily add dial-in support to your meetings. To allow this we would need your permission to create a free JaaS (Jitsi as a Service) account for you. │
│ │
│ Add telephony to your Jitsi meetings? │
│ │
│ <Yes> <No> │
│ │
└───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘
You can retry later by executing:
/usr/share/jitsi-meet/scripts/install-letsencrypt-cert.sh rai.sousuke@mac.com
;dOocd;
.dNMM0dKO.
lNMMMKd0K,
.xMMMMNxkNc
dMMMMMkxXc
cNMMMNl..
.kMMMX; Interested in adding telephony to your Jitsi meetings?
;XMMMO'
lNMMWO' Sign up on https://jaas.8x8.vc/components?host=n2Jammy.yushei.com.tw
lNMMM0, and follow the guide in the dev console.
lXMMMK:.
;KMMMNKd. 'oo,
'xNMMMMXkkkkOKOl'
:0WMMMMMMNOkk0Kk,
.cdOWMMMMMWXOkOl
.;dKWMMMMMXc.
.,:cll:'
Selecting previously unselected package jitsi-meet-turnserver.
(Reading database ... 103669 files and directories currently installed.)
Preparing to unpack .../jitsi-meet-turnserver_1.0.8091-1_all.deb ...
Unpacking jitsi-meet-turnserver (1.0.8091-1) ...
Selecting previously unselected package lua-event:arm64.
Preparing to unpack .../lua-event_0.4.6-2_arm64.deb ...
Unpacking lua-event:arm64 (0.4.6-2) ...
Selecting previously unselected package zip.
Preparing to unpack .../zip_3.0-12build2_arm64.deb ...
Unpacking zip (3.0-12build2) ...
Setting up mysql-common (5.8+1.0.8) ...
update-alternatives: using /etc/mysql/my.cnf.fallback to provide /etc/mysql/my.cnf (my.cnf) in auto mode
Setting up libmysqlclient21:arm64 (8.0.39-0ubuntu0.22.04.1) ...
Setting up fonts-lato (2.0-2.1) ...
Setting up lua5.2 (5.2.4-2) ...
update-alternatives: using /usr/bin/lua5.2 to provide /usr/bin/lua (lua-interpreter) in auto mode
update-alternatives: using /usr/bin/luac5.2 to provide /usr/bin/luac (lua-compiler) in auto mode
Setting up libpq5:arm64 (14.13-0ubuntu0.22.04.1) ...
Setting up lua-socket:arm64 (3.0~rc1+git+ac3201d-6) ...
Setting up lua-event:arm64 (0.4.6-2) ...
Setting up lua-expat:arm64 (1.3.0-5) ...
Setting up lua-filesystem:arm64 (1.8.0-2) ...
Setting up zip (3.0-12build2) ...
Setting up lua-cjson:arm64 (2.1.0+dfsg-2.1) ...
Setting up ssl-cert (1.1.2) ...
Setting up lua-basexx (0.4.1-jitsi1) ...
Setting up lua-inspect (3.1.1-2) ...
Setting up libevent-core-2.1-7:arm64 (2.1.12-stable-1build3) ...
Setting up libidn12:arm64 (1.38-4ubuntu1) ...
Setting up lua-bitop:arm64 (1.0.2-5) ...
Setting up lua-luaossl:arm64 (20161214-1ubuntu1) ...
Setting up jitsi-meet-web (1.0.8091-1) ...
Setting up libonig5:arm64 (6.9.7.1-2build1) ...
Setting up sqlite3 (3.37.2-2ubuntu0.3) ...
Setting up libevent-pthreads-2.1-7:arm64 (2.1.12-stable-1build3) ...
Setting up libevent-extra-2.1-7:arm64 (2.1.12-stable-1build3) ...
Setting up lua-sec:arm64 (1.0.2-1) ...
Setting up libjq1:arm64 (1.6-2.1ubuntu3) ...
Setting up libevent-openssl-2.1-7:arm64 (2.1.12-stable-1build3) ...
Setting up prosody (0.11.13-1) ...
Adding user prosody to group ssl-cert
Created symlink /etc/systemd/system/multi-user.target.wants/prosody.service → /lib/systemd/system/prosody.service.
Setting up coturn (4.5.2-3.1~ubuntu22.04.1) ...
Adding group `turnserver' (GID 132) ...
Done.
Adding system user `turnserver' (UID 122) ...
Adding new user `turnserver' (UID 122) with group `turnserver' ...
Not creating home directory `/'.
I: Creating /var/lib/turn/turndb from /usr/share/coturn/schema.sql
Created symlink /etc/systemd/system/multi-user.target.wants/coturn.service → /lib/systemd/system/coturn.service.
Setting up jq (1.6-2.1ubuntu3) ...
Setting up jitsi-meet-prosody (1.0.8091-1) ...
The host 'focus.n2Jammy.yushei.com.tw' is not configured for this server.
The given hostname does not exist in the config
dpkg: error processing package jitsi-meet-prosody (--configure):
installed jitsi-meet-prosody package post-installation script subprocess returned error exit status 1
Setting up jicofo (1.0-1090-1) ...
Updating /etc/jitsi/jicofo/config to use jicofo.conf
Generating an empty jicofo.conf file
useradd: warning: the home directory /usr/share/jicofo already exists.
useradd: Not copying any file from skel directory into it.
dpkg: dependency problems prevent configuration of jitsi-meet-turnserver:
jitsi-meet-turnserver depends on jitsi-meet-prosody; however:
Package jitsi-meet-prosody is not configured yet.
dpkg: error processing package jitsi-meet-turnserver (--configure):
dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
No apport report written because the error message indicates its a followup error from a previous failure.
dpkg: dependency problems prevent configuration of jitsi-meet:
jitsi-meet depends on jitsi-meet-prosody (= 1.0.8091-1); however:
Package jitsi-meet-prosody is not configured yet.
dpkg: error processing package jitsi-meet (--configure):
dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.35-0ubuntu3.8) ...
Processing triggers for ufw (0.36.1-4ubuntu0.1) ...
Processing triggers for man-db (2.10.2-1) ...
Processing triggers for fontconfig (2.13.1-4.2ubuntu5) ...
Errors were encountered while processing:
jitsi-meet-prosody
jitsi-meet-turnserver
jitsi-meet
E: Sub-process /usr/bin/dpkg returned an error code (1)
試作機器： h2jammy.yushei.net running Ubuntu, Jammy
$ sudo apt update && sudo apt -y upgrade
$ curl https://download.jitsi.org/jitsi-key.gpg.key | sudo sh -c 'gpg --dearmor > /usr/share/keyrings/jitsi-keyring.gpg'
$ echo 'deb [signed-by=/usr/share/keyrings/jitsi-keyring.gpg] https://download.jitsi.org stable/' | sudo tee /etc/apt/sources.list.d/jitsi-stable.list > /dev/null
$ sudo apt-get -y update
Hit:1 https://download.docker.com/linux/ubuntu jammy InRelease
Hit:2 https://packages.microsoft.com/repos/vscode stable InRelease
Hit:3 https://brave-browser-apt-release.s3.brave.com stable InRelease
Hit:4 http://security.ubuntu.com/ubuntu jammy-security InRelease
Get:5 https://dl.cloudsmith.io/public/balena/etcher/deb/ubuntu jammy InRelease [2957 B]
Hit:6 http://tw.archive.ubuntu.com/ubuntu jammy InRelease
Get:7 https://download.jitsi.org stable/ InRelease [1682 B]
Hit:8 http://tw.archive.ubuntu.com/ubuntu jammy-updates InRelease
Get:9 https://dl.cloudsmith.io/public/caddy/stable/deb/debian any-version InRelease [8266 B]
Hit:10 http://tw.archive.ubuntu.com/ubuntu jammy-backports InRelease
Get:11 https://download.jitsi.org stable/ Packages [93.1 kB]
Get:12 https://download.jitsi.org stable/ Contents (deb) [36.3 kB]
Fetched 142 kB in 2s (85.3 kB/s)
Reading package lists... Done
sudo apt-get -y install jitsi-meet
...
┌─────────────────────┤ Configuring jitsi-videobridge2 ├──────────────────────┐
│ The value of the domain that is set in the Jitsi Videobridge installation. │
│ │
│ The domain of the current installation (e.g. meet.jitsi.com): │
│ │
│ h2Jammy.yushei.net_________________________________________________________ │
│ │
│ <Ok> │
│ │
└─────────────────────────────────────────────────────────────────────────────┘
...
Package configuration
┌─────────────────────────────────────────────────────────────────┤ Configuring jitsi-meet-web-config ├──────────────────────────────────────────────────────────────────┐
│ │
│ │
│ │
│ Jitsi Meet requires an SSL certificate. This installer can generate one automatically for your using "Let’s Encrypt". This is the recommended and simplest option for │
│ most installations. │
│ │
│ In the event you need to use a certificate of your own, you can configure its location which defaults to /etc/ssl/--domain.name--.key for the key and │
│ /etc/ssl/--domain.name--.crt for the certificate. │
│ │
│ If you are a developer and are only looking for a quick way to test basic Jitsi Meet functionality then this installer can also generate a self-signed certificate. │
│ │
│ <Ok> │
│ │
└────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘
Package configuration
┌──────┤ Configuring jitsi-meet-web-config ├──────┐
│ SSL certificate │
│ │
│ Let's Encrypt certificates │
│ I want to use my own certificate │
│ Generate a new self-signed certificate │
│ │
│ │
│ <Ok> │
│ │
└─────────────────────────────────────────────────┘
Package configuration
┌───────────────────────────────────────────────────────────────┤ Configuring jitsi-meet-web-config ├────────────────────────────────────────────────────────────────┐
│ │
│ To successfully issue Let's Encrypt certificates: │
│ │
│ You need a working DNS record pointing to this machine(for hostname h2Jammy.yushei.net)" │
│ │
│ You need to agree to the ACME server's Subscriber Agreement (https://letsencrypt.org/documents/LE-SA-v1.1.1-August-1-2016.pdf) by providing an email address for │
│ important account notifications. │
│ │
│ We will use the email for creating your JaaS (Jitsi as a Service) account if that option was selected. │
│ │
│ <Ok> │
│ │
└────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘
Package configuration
┌────┤ Configuring jitsi-meet-web-config ├─────┐
│ Enter your email: │
│ │
│ rai.sousuke@mac.com_________________________ │
│ │
│ <Ok> │
│ │
└──────────────────────────────────────────────┘
Package configuration
┌─────────────────────────────────────────────────────────────┤ Configuring jitsi-meet-web-config ├─────────────────────────────────────────────────────────────┐
│ │
│ You can easily add dial-in support to your meetings. To allow this we would need your permission to create a free JaaS (Jitsi as a Service) account for you. │
│ │
│ Add telephony to your Jitsi meetings? │
│ │
│ <Yes> <No> │
│ │
└───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘
...
Issuing the certificate from Let's Encrypt failed, continuing ...
You can retry later by executing:
/usr/share/jitsi-meet/scripts/install-letsencrypt-cert.sh rai.sousuke@mac.com
Account creation failed. Status: 22, response:
Account creation failed. Status: 22, response:
;dOocd;
.dNMM0dKO.
lNMMMKd0K,
.xMMMMNxkNc
dMMMMMkxXc
cNMMMNl..
.kMMMX; Interested in adding telephony to your Jitsi meetings?
;XMMMO'
lNMMWO' Sign up on https://jaas.8x8.vc/components?host=h2Jammy.yushei.net
lNMMM0, and follow the guide in the dev console.
lXMMMK:.
;KMMMNKd. 'oo,
'xNMMMMXkkkkOKOl'
:0WMMMMMMNOkk0Kk,
.cdOWMMMMMWXOkOl
.;dKWMMMMMXc.
.,:cll:'
Selecting previously unselected package jitsi-meet-turnserver.
(Reading database ... 336939 files and directories currently installed.)
Preparing to unpack .../jitsi-meet-turnserver_1.0.8091-1_all.deb ...
Unpacking jitsi-meet-turnserver (1.0.8091-1) ...
Selecting previously unselected package lua-event:amd64.
Preparing to unpack .../lua-event_0.4.6-2_amd64.deb ...
Unpacking lua-event:amd64 (0.4.6-2) ...
Setting up libevent-extra-2.1-7:amd64 (2.1.12-stable-1build3) ...
Setting up lua5.2 (5.2.4-2) ...
update-alternatives: using /usr/bin/lua5.2 to provide /usr/bin/lua (lua-interpreter) in auto mode
update-alternatives: using /usr/bin/luac5.2 to provide /usr/bin/luac (lua-compiler) in auto mode
Setting up libevent-openssl-2.1-7:amd64 (2.1.12-stable-1build3) ...
Setting up lua-socket:amd64 (3.0~rc1+git+ac3201d-6) ...
Setting up jicofo (1.0-1090-1) ...
Updating /etc/jitsi/jicofo/config to use jicofo.conf
Generating an empty jicofo.conf file
useradd: warning: the home directory /usr/share/jicofo already exists.
useradd: Not copying any file from skel directory into it.
Setting up lua-event:amd64 (0.4.6-2) ...
Setting up lua-expat:amd64 (1.3.0-5) ...
Setting up lua-filesystem:amd64 (1.8.0-2) ...
Setting up lua-cjson:amd64 (2.1.0.10-jitsi1) ...
Setting up lua-basexx (0.4.1-jitsi1) ...
Setting up lua-inspect (3.1.1-2) ...
Setting up lua-bitop:amd64 (1.0.2-5) ...
Setting up lua-luaossl:amd64 (20161214-1ubuntu1) ...
Setting up jitsi-meet-web (1.0.8091-1) ...
Setting up sqlite3 (3.37.2-2ubuntu0.3) ...
Setting up libevent-pthreads-2.1-7:amd64 (2.1.12-stable-1build3) ...
Setting up lua-sec:amd64 (1.0.2-1) ...
Setting up prosody (0.11.13-1) ...
Adding user prosody to group ssl-cert
Created symlink /etc/systemd/system/multi-user.target.wants/prosody.service → /lib/systemd/system/prosody.service.
Setting up coturn (4.5.2-3.1~ubuntu22.04.1) ...
Adding group `turnserver' (GID 145) ...
Done.
Adding system user `turnserver' (UID 136) ...
Adding new user `turnserver' (UID 136) with group `turnserver' ...
Not creating home directory `/'.
I: Creating /var/lib/turn/turndb from /usr/share/coturn/schema.sql
Created symlink /etc/systemd/system/multi-user.target.wants/coturn.service → /lib/systemd/system/coturn.service.
Setting up jitsi-meet-prosody (1.0.8091-1) ...
The host 'focus.h2Jammy.yushei.net' is not configured for this server.
The given hostname does not exist in the config
dpkg: error processing package jitsi-meet-prosody (--configure):
installed jitsi-meet-prosody package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of jitsi-meet-turnserver:
jitsi-meet-turnserver depends on jitsi-meet-prosody; however:
Package jitsi-meet-prosody is not configured yet.
dpkg: error processing package jitsi-meet-turnserver (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of jitsi-meet:
jitsi-meet depends on jitsi-meet-prosody (= 1.0.8091-1); however:
Package jitsi-meet-prosody is not configured yet.
dpkg: error processing package jitsi-meet (--configure):
dependency problems - leaving unconfigured
Processing triggers for ufw (0.36.1-4ubuntu0.1) ...
No apport report written because the error message indicates its a followup error from a previous failure.
No apport report written because the error message indicates its a followup error from a previous failure.
Processing triggers for man-db (2.10.2-1) ...
Processing triggers for libc-bin (2.35-0ubuntu3.8) ...
Errors were encountered while processing:
jitsi-meet-prosody
jitsi-meet-turnserver
jitsi-meet
E: Sub-process /usr/bin/dpkg returned an error code (1)
試作機器： hc4Noble.yushei.net <-- failed
- First install the Jitsi repository key onto your system:
- curl https://download.jitsi.org/jitsi-key.gpg.key | sudo sh -c 'gpg --dearmor > /usr/share/keyrings/jitsi-keyring.gpg' --> failed
$ curl -fsSL https://download.jitsi.org/jitsi-key.gpg.key | sudo apt-key add -
[sudo] password for alexlai:
OK
$ echo "deb [signed-by=/usr/share/keyrings/jitsi-keyring.gpg] https://download.jitsi.org stable/" | sudo tee /etc/apt/sources.list.d/jitsi-stable.list
$ sudo apt update
...
Err:4 https://download.jitsi.org stable/ InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B4D2D216F1FD7806
Reading package lists... Done
W: GPG error: https://download.jitsi.org stable/ InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B4D2D216F1FD7806
E: The repository 'https://download.jitsi.org stable/ InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
$ curl -fsSL https://download.jitsi.org/jitsi-key.gpg.key | gpg --dearmor | sudo tee /usr/share/keyrings/jitsi-keyring.gpg
$ sudo apt update
-
Create a sources.list.d file with the repository:
- echo 'deb [signed-by=/usr/share/keyrings/jitsi-keyring.gpg] https://download.jitsi.org stable/' | sudo tee /etc/apt/sources.list.d/jitsi-stable.list > /dev/null Update your package list: sudo apt-get -y update Install the full suite: sudo apt-get -y install jitsi-meet or only the packages you need like for example:
sudo apt-get -y install jitsi-videobridge sudo apt-get -y install jicofo sudo apt-get -y install jigasi
試作機器： h2nas01.yushei.net !! failed !!
% ssh -p 1765 h2nas01.yushei.net
[alexlai@h2nas01 ~]$ sudo pacman -Syyu
sudo pacman -S jitsi-meet ---> orphaned