Easy way to create a Jitsi cluster

Hello,

I made some tools, installer and documentation to create a Jitsi cluster in an easy way. I really mean “easy”. For detailed information, please see the link below:

Easy way to create a Jitsi cluster based on Debian Buster (Debian 10)

These are the steps:

  • Jitsi Meet Server (JMS) installation

    • download the installer
    • set the hostname
    • run the installer
    • get a Let’s Encrypt certificate
  • Adding an additional Jitsi Videobridge (JVB) node to the cluster

    • copy the JMS’s public key to the node (newly installed Debian machine)
    • run the add-jvb-node command on JMS
  • Adding an additional Jibri node to the cluster

    • copy the JMS’s public key to the node (newly installed Debian machine)
    • run the add-jibri-node command on JMS

Please send me feedback if you have an issue

@emrah

Thanks for this, we have ran the script and come up with the following errors;

This is right at the end of the install process, I ran the script twice, the first time as a sudo user and got this error at the set-letsencrypt-cert meet.mydomain.com stage, the 2nd time I ran as root and got the same error at the end of the install script.

We are running a Azure VM with 5.5.0-0.bpo.2-amd64 #1 SMP Debian 5.5.17-1~bpo10+1 (2020-04-23) x86_64 GNU/Linux

lxc-attach: eb-jitsi: attach.c: lxc_attach: 1095 Failed to get init pid

Something went wrong. The installation couldn’t be completed!

Thanks

Can you paste the output of the following commands?

lxc-ls -f
lxc-start -n eb-jitsi
lxc-attach -n eb-jitsi -- bash -c 'ls'

ip a

NAME STATE AUTOSTART GROUPS IPV4 IPV6 UNPRIVILEGED
eb-buster STOPPED 0 - - - false
eb-jibri-template RUNNING 1 eb-group, eb-jibri 172.22.22.223 - false
eb-jitsi STOPPED 1 eb-group, onboot - - false

No output

bin boot dev etc home lib lib64 media mnt opt proc root run sbin srv sys tmp usr var

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:0d:3a:d9:80:ec brd ff:ff:ff:ff:ff:ff
inet 10.0.2.4/24 brd 10.0.2.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::20d:3aff:fed9:80ec/64 scope link
valid_lft forever preferred_lft forever
3: eb0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether fe:28:e0:b2:5a:db brd ff:ff:ff:ff:ff:ff
inet 172.22.22.1/24 brd 172.22.22.255 scope global eb0
valid_lft forever preferred_lft forever
inet6 fe80::cf1:3eff:febf:222a/64 scope link
valid_lft forever preferred_lft forever
7: vethJ7E07N@if6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master eb0 state UP group default qlen 1000
link/ether fe:28:e0:b2:5a:db brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet6 fe80::fc28:e0ff:feb2:5adb/64 scope link
valid_lft forever preferred_lft forever
9: veth3SSI1K@if8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master eb0 state UP group default qlen 1000
link/ether fe:60:20:0a:f4:ab brd ff:ff:ff:ff:ff:ff link-netnsid 1
inet6 fe80::fc60:20ff:fe0a:f4ab/64 scope link
valid_lft forever preferred_lft forever

Hello @Greenzom,

I sent you a private message. I can connect to the server and check it if it is OK for you.

Hello @Greenzom,

I deleted the containers and I started the installer again.

To delete the containers:

lxc-stop -n eb-jitsi
lxc-stop -n eb-jibri-template
lxc-destroy -n eb-jitsi
lxc-destroy -n eb-jibri-template

It’s working now