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.



  • @nebulon damn, guess that means Jitsi wont be coming to Cloudron any time soon šŸ˜• wish I could help, but have no idea!



  • @nebulon That is very unfortunate, but thank you for explaining these underlying issues. Do I understand it correctly that if there's a solution, the TURN server would need to be a part of the Cloudron software itself, not an app?



  • @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.



  • Thanks for the added clarity, @girish - certainly look forward to this and other apps such an addition would enable!



  • @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! šŸ™‚



  • Great thinking @girish! In addition to Nextcloud Talk, Jitsi Meet and Kopano, the Matrix app will also benefit from this.



  • On the app packaging level, has there been efforts to include LDAP support? Iā€™d like for Cloudron users to be the ones able to create rooms, then able to invite whoever: users and guests alike.



  • LDAP seems to be supported out of the box in dockerized Jitsi Meet! šŸŽ‰


Log in to reply