Difference between revisions of "Jitsi - Host your own video conference server and have control over your own data"
(Created page with "Installation tutorial for Ubuntu 18.04 with Nginx. <br> An privacy friendly and more secure alternative to existing video conference software. You can host your own video con...")
Latest revision as of 23:54, 4 April 2020
Installation tutorial for Ubuntu 18.04 with Nginx.
An privacy friendly and more secure alternative to existing video conference software. You can host your own video conference server easily with Jitsi. The installation process does not take long. Please use the root user or add the sudo command to the here mentioned commands.
1. Install the requirements
add-apt-repository ppa:openjdk-r/ppa apt install openjdk-8-jre-headless -y
As well Nginx to access your Jitsi video conferencing web interface.
apt install nginx
2. Install and configure Jitsi
wget -qO - https://download.jitsi.org/jitsi-key.gpg.key | apt-key add - echo 'deb https://download.jitsi.org stable/' >> /etc/apt/sources.list.d/jitsi-stable.list
Update your apt repository and install the software.
apt update && apt install jitsi-meet -y
During the installation process you will be asked to enter the domain name that referenced to the server, that will host Jitsi. In this example we will use the domain name "myserver.tld". Click on "Generate new self-signed certificate..." to create a self signed SSL certificate.
You can now create an authenticated SSL certificate for your Jitsi server.
Note: Do not forget to open the port 80, 443 and the port range between 10000 and 20000 in your firewall settings.
Run this command to enable the access the web interface Jitsi (required):
ln -s /etc/nginx/sites-available/myserver.tld.conf /etc/nginx/sites-enabled
Now, restart your Nginx server.
service nginx restart
After that you can now access your Jitsi server through the domain name that you have added during the Jitsi installation process.
3. Important: If your Nginx does not start, then you have to delete this file in the Nginx config folder.
This must be a bug, because the config file blocks the start of Nginx.