Nextcloud Talk not connecting calls
-
@nebulon adding stream support is done by enabling the module config.
See:
https://jitsi.github.io/handbook/docs/devops-guide/turnHence you can rev/fwd proxy anything as long as you can pass in the servername for nginx to pivot on.
FYI the stream_core_module is included in Ubuntu enginx-core packages.
P.S. It would be useful for @staff to be aware of the other modules for mail and other services that are available for multi-cloudron functionality.
-
I'm playing with https://markus-blog.de/index.php/2020/11/20/how-to-run-nextcloud-talk-high-performance-backend-with-stun-turnserver-on-ubuntu-with-docker-compose/ on a Scaleway VM now to see how it works. It would be ace to get Cloudron's proxy to be able to proxy to the TURN/STUN server. Maybe my set up is too complicated (double NAT) and it works more smoothly to run Cloudron on a dedicated VM in a data centre somewhere
-
@nebulon said in Nextcloud Talk not connecting calls:
@micmc unfortunately the TURN server on Cloudron cannot run on port 443, which is the most reliable one for webrtc
Yeah, true I always forget this 'limitation' that TURN needs to run on port 443.
We may have to provide a feature to select which TURN server should be used for apps, internal or external, similar to how we deal with email sending.
While being at it that would be a great solution, and for several apps at the same time. +1
-
@nebulon I just noticed that my custom TURN settings are being overwritten when the app is updated
stun_server turn_server TURN server schemes turn_secret
Looks like
signaling_secret
is not affected.I assume this is the expected behaviour but as a user who customises this, I would like my own settings to be honored, please
-
@micmc said in Nextcloud Talk not connecting calls:
Yeah, true I always forget this 'limitation' that TURN needs to run on port 443.
Where does this come from or where you being sarcastic? (sorry, my translator is not enabled today)
I run my own TURN and STUN servers on port 3478. Maybe I am misunderstanding?
-
-
@3246 @girish mentioned public wifis. I think biggest reason for setting up turn on 443 is that very many (most?) academic and corporate IT systems block everything but 443 for ordinary users. So you'll never get a good connection if you have users accessing the internet there.
Cloudron does indeed overwrite the turn server setting in Nextcloud upon reboot/update of the app. Thankfully with Nextcoud you don't need to reboot to add the turnsever back in. So adding it works.
Sadly that's not the case with other apps - notably matrix - which means those apps will be limited in their videoconferencing capability until the ability to add an external turnserver is added to cloudron.
@girish from my perspective I don't think you need a per-app choice there. Just a global option which turnserver to use across apps. My sense is that people who need an external turnserver for one app (because of users in an academic/corporate setting or using Cloudflare, etc) will need it for them all.
- list item
-
@3246 this is coming in 7.2 - https://forum.cloudron.io/topic/6655/what-s-coming-in-7-2 (the last bullet point)
-
- Do I need to install the turn server on the same server I installed the nextcloud
Or a different server?
My nextcloud works fine just that I can not call users on a different network.
How do I do this right, for I call users who are not on the same networks?
Thank you