Install jitsi meet debian 10 install#
Install jitsi meet debian 10 update#
Install jitsi meet debian 10 password#

Install jitsi meet debian 10 install#

→ set and enable firewall (UFW): sudo apt install -y ufw Later on you will configure Fail2Ban to work with Prosody (see “Fail2Ban for Prosody” in authentication how-to). → install fail2ban: sudo apt install -y fail2ban

Install jitsi meet debian 10 update#

Update your system (mantain local config files if asked) and reboot: sudo apt update

Install jitsi meet debian 10 password#

→ disable SSH Password login and SSH root login: sudo nano /etc/ssh/sshd_configĬhanging PasswordAuthentication and PermitRootLogin values to no (uncomment if necessary), save and exit, then restart sshd to apply changes (your ssh connection will not be interrupted): sudo service sshd restart Save and exit (alternatively, you may use ssh-copy-id on your client machine).

Login as the newly created user and add your public SSH key(s): mkdir ~/.ssh Usermod -a -G sudo USER_NAME_OF_YOUR_CHOICE → first of all, create a new user, add it to sudoers group and logout as root: apt install -y sudo It is just an internal domain used by jicofo to connect to prosody. NOTE: you do not need to create a DNS record for.

hostname: (change it to the actual domain you are using).

OS: debian 10 minimal (just sshd and base system utilities) - ubuntu 18.04.

Server: should work on 1 core, 1GB RAM - suggested (at least) 2 core, 2GB RAM (scale at your needs).

It is just a WIP proposal, open to discussion, on how a Jitsi-Meet server can be quickly (and legally) deployed in order to host one’s own private videomeetings, based on authors’ practical experiences. JVB 10:42:23.123 SEVERE: .call().278 host-unknown, host:localhost, port:5347Īt .DISCLAIMER: this is not legal nor technical advice. : host-unknownĪt .connect(ExternalComponent.java:219)Īt .addComponent(ExternalComponentManager.java:221)Īt .addComponent(ExternalComponentManager.java:201)Īt $3.call(ComponentMain.java:270)Īt $3.call(ComponentMain.java:255)Īt $n(RetryStrategy.java:193)Īt $RunnableAdapter.call(Executors.java:471)Īt .run(FutureTask.java:262)Īt $ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)Īt $n(ScheduledThreadPoolExecutor.java:292)Īt .runWorker(ThreadPoolExecutor.java:1145)Īt $n(ThreadPoolExecutor.java:615) JVB 10:42:03.042 INFO: () Created user preferences directory. JVB 10:42:01.566 INFO: .info() Initialized TCP harvester on port 4443, using SSLTCP:true

JVB 10:42:01.558 INFO: .TcpHarvester.addLocalAddresses() Not using link-local address /fe80:0:0:0:42:acff:fe11:2%6 for TCP candidates. JVB 10:42:01.558 WARNING: .warn() Failed to initialize TCP harvester on port 443: : Permission denied. JVB 10:42:01.547 WARNING: .() ICE4J does not support sharing of listening endpoints (probably because it is not running on JDK 8). JVB 10:42:01.539 INFO: .TcpHarvester.addLocalAddresses() Not using link-local address /fe80:0:0:0:42:acff:fe11:2%6 for TCP candidates. JVB 10:42:01.530 INFO: .SinglePortUdpHarvester.() Initialized SinglePortUdpHarvester with address 172.17.0.2:10000/udp JVB 10:42:00.927 INFO: ().98 Network Address Manager Service. JVB 10:42:00.517 INFO: .() failed to find jitsi-default-overrides.properties with class loader, will continue without it. JVB 10:42:00.515 INFO: .() failed to find jitsi-defaults.properties with class loader, will continue without it. Stopping jicofo: jicofo doesn't seem to be running. Stopping jitsi-videobridge: jvb doesn't seem to be running. SSL certificate for the Jitsi Meet instance A certificate is available and the files are uploaded on the server Self-signed certificate will be generatedĢ. The defaultįilenames will be /etc/ssl/ for the key and Having a certificate signed by a recognisedĬA, it can be uploaded on the server and point its location. Having no certificate,Ī self-signed one will be generated. Jitsi Meet is best to be set up with an SSL certificate. The jisti-videobridge package needs the DNS hostname of your instance.