I don’t really understand why nginx is not started, but let’s start it and see if it works. Re-click on the BIG launch button… certificate: OK installing Jitsi: OK reloading services: NOK. It was a problem with the nginx server which were listening only on IPv4, so it was failing for the IPv6 challenge. :sad: Third step - Debugging the roleįirst problem, the challenge for the certificate is failing. I press the BIG launch button, Ansible is starting and… FAIL.
hosts : user : amarok vars : jitsi_meet_server_name : jitsi_meet_lang : fr roles : - role : thefinn93.letsencrypt become : yes letsencrypt_email : jitsi_meet_server_name }}" letsencrypt_cert_domains : - ".crt" dest : "/usr/local/share/ca-certificates/" - name : Run update-ca-certificates for Jicofo become : true command : update-ca-certificates So, I did this little playbook ( jitsi.yml)
#Jitsi meet hosting update#
For Jitsi, I found this project: Įven if the role is not up-to-date (last commit is from 2017), a pull request exists to update the role and is only 2 months old! Let’s try with that patched role. And, to avoid to re-invent the wheel, we use existing ansible roles made by others. Second step - Automate all the thingsĪnsible is used ot automate the installation of our servers. So the next step is to setup the back-up system, monitoring tools and automate the installation of Jitsi and the certificate. Again, we did some tests and the instance was working great. But we saw that the instance was functionnal and we did some conferences with multiple participants.īecause everything seemed to work, I did the same steps (with the auto-signed certificate) but on the final production server (in a clean state). The only big difference between my setup and the final server is that the VM is only available in my local network, so I used an auto-signed certificate instead of our Let’s Encrypt certificate. So, I decided to start to do my own virtual machine, in my local network (bridge mode) to replicate the final server config (a Debian Stretch, 1 Go RAM, 2 CPUs) and I followed the instructions from this page: I arrived in this project at this precise moment. But, after a migration to our final server, we started to see a lot of problems with that instance (due to the migration or the installation of the back-up system or the monitoring tools).
#Jitsi meet hosting manual#
First step - The manual installationįor the story, the first attempt for hosting the instance worked during several weeks. This instance will be available at this address: and this is a little post about how we did it and what problems we encountered. For the local future CHATONS ( Chatons is a french word which means kitten), I am currently helping to host a new Jitsi-meet instance.
0 kommentar(er)
