Now I was able to complete the installation. The error I made is that I forgot to uncomment The first Jitsi server I created at the end of the last year worked without these “modifications” however I only had “conferences” with one more participiciant. I have now set up a second Jitsi server with the latest docker files () and this only worked with the two “modifications” I mentioned above.
#Jitsi ports password
And you will not be asked for the username and password if you have configured “ENABLE_AUTH = 1”. If not, you will not be able to enable the camera and the microphone when you start a conference. You can do this by choosing “WebSocket” from the Dropdown-List “Create”. “Connection” with the value “$connection_upgrade”. “Upgrade” with the value “$http_upgrade” and 2. In the configuration window of the reverse proxy it is necessary to define two user defined headers: 1.
#Jitsi ports manual
If I understood the manual correctly this is necessary if you want to establish a conference with more than two participiciants.Ģ. These are the ports 10000 (UDP) and 4443 (TCP). In the router you have to open two more ports besides of port 443 (HTTPS). 2020 – Edited after Mchl Grdlv comments.įirst of all: Thank you for this tutorial. I use a letsencrypt certificate but you can also import one.Ĭonfigure the certificate to be presented for (Security > Certificates > Configure)Īfter completing these steps you should have a working private videoconferencing solution, with authenticated host and guest access activated on your Synology NAS.ĩ Sept.
#Jitsi ports install
You need also to generate a certificate and install it on your NAS (Security > Certificates > Create) This is mandatory to have a fully working solution. You can use the Synology NAS reverse proxy to redirect your domain HTTPS to your container on port 8443 (Application Portal > Reverse Proxy > Create). Prosodyctl -config /config/ register TheDesiredUsername meet.jitsi TheDesiredPassword To protect access to your meeting solution connect to the prosody container:ĭocker exec -it docker-jitsi-meet-master_prosody_1 /bin/bash You can now create and run the docker containers: I use afraid DNS route my personal domain to my NAS public IP. env file and change the line CONFIG=~/.jitsi-meet-cfg to CONFIG=/volume1/docker/docker-jitsi-configĮnable authentication, guest access and internal authentication:Ĭustomize the lines related to your environment and the docker host IP (your NAS interface). Mkdir -p /volume1/docker/docker-jitsi-config/Įdit the. Mkdir /volume1/docker/docker-jitsi-config/ Go to the folder you just created it will be something like:Ĭd /volume1/docker/docker-jitsi-meet-masterĬreate a folder where to store the configuration files: In my installation it is the folder /volume1/docker Upload and extract on your NAS the content of the zip file. I assume that you are familiar with docker, SSH access & certificate installation/request. All explanations below are coming from the Jitsi github page, with a little customization to fit my needs. I wanted to implement this on my Synology NAS (DS918) using docker containers. In these days of physical isolation I wanted to spend my free time to check and implement a videoconferencing solution for my private use.Īfter googling I found Jitsi and in few minutes I was able to setup a test environment on my computer using docker.