Jitsi is reported not to work with OpenJDK 10: many recommend using OpenJDK 8, but OpenJDK 11 appears to be OK.
You should check which Java version is automatically installed along with jitsi-meet while installing it.
There is an open issue on github about letsencrypt certificates renewal problems ( -meet/issues/2885). However, it does not appear to apply to the standard debian/ubuntu installation described here. In any case, if there are problems with certificates renewal, you will be notified by email; in such case, just run again the command above.
Hey, I`d like to set up Jitsi Meet on my server as well and just learned about and started loving Caddy - but I have little experience with network config. Can I set this all up on a single machine using Caddy? Or am I better served using nginx in this case? Can I run them side-by-side?
I had installed again jitsi meet and it was the same result.
I had open the inbound ports in the firewall (is not a consumer is Sophos SG firewall).
In the firewall log it shows no blocked traffic.
Run something akin to prosodyctl register meet.luminescent-dreams.com for each user you want to add to your system. Looks like an admin has to choose passwords for users instead of letting users set a private password.
So why deploy this on NixOS and not on Debian or with Docker?NixOS has many advantages for running servers.It allows you to configure your whole server declaratively,so you can reuse the same configuration for multiple servers.Also, because it is reproducible,setting up a server with the same NixOS configurationwill ensure that it runs the exact same software with the same configuration.Finally, if an update breaks your setup,NixOS makes rollbacks as easy as running one command or rebooting,so you can minimise downtime.
One is the interface configuration (interface_config.js),which is deprecated but still required to configure some things.It can be modified by setting the NixOS option services.jitsi-meet.interfaceConfig.A commented list of all options and their default values can be found in the Jitsi Meet source code.
Installing Jitsi on the server is straight forward with their Docker container. All it takes is 4 commands on the shell! Yes, 4 commands! This gives you a running Jitsi instance on TCP port 8443 without encryption. A few additional commands give you a Letsencrypt certificate for a domain you own and which you have pointed to the IP address of the VM. This is important to get the Android and iOS apps running as they refuse to connect to the server that respond with a self signed certificate. More about installation in a separate post.
When presenting to a larger audience with only one video stream running, the CPU cores ran at 44%, memory usage dropped to 740 MB and data traffic was 21 Mbit/s out vs. 3.8 Mbit/s. When switching to screen sharing, CPU loads dropped to 20%, memory use to 674 MB and the datarate on the server was negligible at 1 Mbit/s.
I have decided to install jitsi meet on AWS. I have an an elastic beanstalk site with [ Python 3.6 running on 64bit Amazon Linux ] platform.
The EC2 instance is t2.micro, but in production I will have up to 110 users having conferences every day with a maximum of 3 conferences taking place at any given time.
The best guide I could find on how to proceed with the installation on AWS is hereBut obviously I would have to make a new instance to do that. The big difference is that the instructions need ubuntu to be installed on the instance, and I don't have that on my current instance. I am not so familiar with linux, is it possible to translate those instructions meant for Ubuntu into my current instance, so I don't have to pay for a new instance?
I had same problem when I installed Jitsi, this week. I solved the problem by ssh into my server, then then reload the firewall with this command: [ sudo yunohost firewall reload ] That solved the problem for me. Perhaps this might also resolve yours.
Jitsi is a great piece of software but unfortunately the hosting requirements are well beyond what a shared hosting account can manage, you have to run it on its own server. The easiest way to do that would be a one-click server setup through Digital Ocean Jitsi Server DigitalOcean Marketplace 1-Click App
Jitsi Meet is a free encrypted video conferencing software. Jitsi Meet is open source and uses end-to-server/transit encryption, whereby your communication is encrypted before it leaves your device, and is then decrypted on the server, processed, and encrypted again before being sent to the recipient(s). The software itself can be trusted, however it is important to use Jitsi Meet on a trusted server, such as those listed below. When used on a trusted server, this tool can help to reduce the risk of surveillance, interference in calls and the sale and or mishandling of private information of participants.
REMEMBER
It is important to only use Jitsi Meet on trusted servers, so we have recommended some of the servers we trust. If you are planing to use it on another server and are in doubt, please ask digital protection trainers you know whether it is secure. Using Jitsi Meet on untrusted servers may compromise the security the call.
Some servers allow for calling in to a meeting with a regular phone call. However we would discourage this if possible, as if this is done by even one of the participants, the privacy of the whole group conversation can be compromised by the phone company or anyone tapping into the phone call.
In this step, you will configure your Jitsi Meet server to only allow registered users to create conference rooms. The files that you will edit were generated by the installer and are configured with your domain name.
Here, you added guest. to the front of your domain name. For example, the correct name to put here for jitsi.your_domain is guest.jitsi.your_domain. The guest. hostname is only used internally by Jitsi Meet, you will never enter it into a browser or need to create a DNS record for it.
During the installation, you need to enter a hostname for your Jitsi instance. This is the hostname that will appear in the web browser address bar when attendees join your video conference. You can use a descriptive hostname like meet.example.com.
Jitsi Meet listens on several UDP ports. To allow attendees to join a video conference from a web browser, you need to open TCP port 80 and 443. And to transfer video over the network, open UDP port 10000 and TCP port 5349. The Coturn server also needs to open the UDP 3478 port.
The installation of Jitsi meet is done successfully but wen I invite others to the meeting they cannot see me nor hear me nor see the screen I am sharing.
Jitsi meet is installed on Ubuntu 16+ (bionic). please let me know how should I proceed on troubleshooting this issue.
Thanks
Hello, thank you very much for your work. One question. In main subdomain jitsi.example.com works correctly, but in the one I created for guests, guest.jitsi.example.com, the browsers detect an error in the certificate. In fact, when inspecting the certificate, it points to the domain jitsi.example.com but not to the sub-subdomain. Should we run the certbot again for the guest domain and configure it somehow?
Good, you can do a jitsi installation tutorial in 2022 because many things have changed, for example, sudo nano /etc/jitsi/jicofo/sip-communicator.properties is no longer found
and it is complex because in the documentation and in google there is no way to solve it, I appreciate you taking into account my request:
Pdt: Thank you for your knowledge. And there are many people with the same problem-
Translated into english by google translator
To be thorough, in April 2020 there was a snapshot made byarchive.org of the stable repository, which did include thejitsi version 2.10.5550-1 package, dated from 2017. So I can onlyconclude that it was removed for some unknown reason from the stablerepository.
(as the package jitsi-archive-keyring is the same in the unstablerepository and would also install/etc/apt/sources.list.d/jitsi-stable.list with the stable versionurl, it makes sense to use a different file to avoid it beingoverwritten)
In this digital age, video meetings play an increasingly crucial role in business communication and collaboration. Jitsi Meet, an open-source video conferencing solution, provides a powerful and flexible platform for hosting online meetings. On the other hand, Grafana is a widely used monitoring tool for tracking the performance of systems and applications. But did you know that it's possible to integrate Jitsi Meet with Grafana to monitor your video meetings in real-time? In this article, we'll explore this exciting integration and its benefits.
Grafana enables you to store historical data and create customized dashboards to analyze trends and performance of your video meetings over a specific period. This provides a broader visibility and helps you make informed decisions.
If you prefer an installation via the command line, e.g. remote SSH login, all it takes is a simple univention-app install jitsimeet.
Technically, the Jitsi Meet app uses the official docker images of the Jitsi project and starts the services with a configuration adapted to the UCS environment.
(1) Eventhough I add the Jitsi App to the Workspace, Jitsi does not appear on the list of applications.
(2) By chance I discover that on the botton of the window chat (where the users write the new messages), there is one hidden icon between the smile icon and the Send button that opens one meeting request request. If I click on it, it opens Jitsi, but the public instance.