Jitsi Meet
-
For jitsi to work properly, we would need a coturn instance on Cloudron, which unfortunately has to run on port 80/443 to work reliably on public wifis (other ports are often blocked there). So far we haven't found a solution to make turn work with our nginx reverse proxy, which also has to run on the same ports. If anyone finds a solution here, which we can try, I am happy to give it a shot.
-
For jitsi to work properly, we would need a coturn instance on Cloudron, which unfortunately has to run on port 80/443 to work reliably on public wifis (other ports are often blocked there). So far we haven't found a solution to make turn work with our nginx reverse proxy, which also has to run on the same ports. If anyone finds a solution here, which we can try, I am happy to give it a shot.
@nebulon damn, guess that means Jitsi wont be coming to Cloudron any time soon
wish I could help, but have no idea! -
For jitsi to work properly, we would need a coturn instance on Cloudron, which unfortunately has to run on port 80/443 to work reliably on public wifis (other ports are often blocked there). So far we haven't found a solution to make turn work with our nginx reverse proxy, which also has to run on the same ports. If anyone finds a solution here, which we can try, I am happy to give it a shot.
-
For jitsi to work properly, we would need a coturn instance on Cloudron, which unfortunately has to run on port 80/443 to work reliably on public wifis (other ports are often blocked there). So far we haven't found a solution to make turn work with our nginx reverse proxy, which also has to run on the same ports. If anyone finds a solution here, which we can try, I am happy to give it a shot.
@nebulon said in Jitsi Meet:
For jitsi to work properly, we would need a coturn instance on Cloudron, which unfortunately has to run on port 80/443 to work reliably on public wifis (other ports are often blocked there)
Perhaps an interim solution would be to use other ports? I'm mean, it'd be great if people could join using open public WiFi, but I think in many use cases Jitsi not working on such networks wouldn't be too much of an issue. Eg. Like right now the need is for people in covid_19 coronavirus lockdown using their own private WiFi to be able to use it.
I note @iqweb has managed to install a coturn server on the same VPS as their Cloudron, for use with Nextcloud Talk, could that be part of the solution to getting Jitsi working too? https://forum.cloudron.io/post/4207
-
Before everyone jumps to conclusions
So far, @nebulon has been trying to make coturn to be part of the app itself. This is indeed quite hard.So, I think what this means is that we have to integrate the turn server into the platform code base itself. So, it would become an addon/service just like the databases and other things. And then nextcloud, jitsi, kopano meet etc can just use this coturn service. Integrating coturn into cloudron is not very hard but will require a new release of Cloudron.
-
Before everyone jumps to conclusions
So far, @nebulon has been trying to make coturn to be part of the app itself. This is indeed quite hard.So, I think what this means is that we have to integrate the turn server into the platform code base itself. So, it would become an addon/service just like the databases and other things. And then nextcloud, jitsi, kopano meet etc can just use this coturn service. Integrating coturn into cloudron is not very hard but will require a new release of Cloudron.
@girish said in Jitsi Meet:
So, I think what this means is that we have to integrate the turn server into the platform code base itself. So, it would become an addon/service just like the databases and other things. And then nextcloud, jitsi, kopano meet etc can just use this coturn service. Integrating coturn into cloudron is not very hard but will require a new release of Cloudron.
That'd be totally awesome!
Which I guess is what we've come to expect from Cloudron
It also sounds like having a turn server service/ addon that can be used by nextcloud talk/ jitsi meet/ kopano meet etc, would be a much better solution anyway, so I'm actually really glad that making it part of the app is hard!
-
LDAP seems to be supported out of the box in dockerized Jitsi Meet!
-
Sounds like end to end encryption coming to jitsi soon (although also sounds like perhaps only for chromium/ chrome):
-
Any news on a Jitsi app on Cloudron?
The Privacy Authority of The Netherlands published a overview of video-call apps (https://autoriteitpersoonsgegevens.nl/nl/nieuws/keuzehulp-privacy-bij-videobel-apps) and here (https://autoriteitpersoonsgegevens.nl/sites/default/files/atoms/files/keuzehulp_privacy_videobellen.pdf) you see that it looks like Jitsi is the best choice!
-
No major news on this so far, unfortunately it is quite the beast to package with a lot of undocumented configuration options, even their own debian packaging scripts are a hit and miss in our experience. Surely it would be good to have and hopefully eventually we will get there.
-
No major news on this so far, unfortunately it is quite the beast to package with a lot of undocumented configuration options, even their own debian packaging scripts are a hit and miss in our experience. Surely it would be good to have and hopefully eventually we will get there.
-
Office topic: Jitsi gets integrated in the Brave Browser - https://www.ghacks.net/2020/05/27/brave-launches-brave-together-video-calling-in-latest-nightly-version/amp/
-
+1 for Jitsi Meet Server on Cloudron
-
+1 for Jitsi Meet Server on Cloudron
Especially with user manegement
-
+1 for Jitsi Meet on Cloudron
I'm using Kopano and I don't find it to be as reliable for establishing connections as the public Jitsi server. I would far prefer to use my own machine though.
Is this being actively worked on? Can I help at all, say by testing?
Would it help if there was a small bounty for getting it working (if that is appropriate in this community)?
