Nextcloud Talk not connecting calls

[nebulon]

@3246 this is not a real requirement but just depends on which network the clients are on. Some public wifis for example would block most ports besides the common ones. TURN on 443 is just a safe bet, since 443 is basically always open.

[eganonoa]

@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]

@girish @nebulon is there a way for me to hardcode my own TURN server / HPB? I have to manually check and update three Nextcloud sites every day, which is getting a bit tedious

Pretty please

[girish]

@3246 this is coming in 7.2 - https://forum.cloudron.io/topic/6655/what-s-coming-in-7-2 (the last bullet point)

[3246]

@girish said in Nextcloud Talk not connecting calls:

Amazing! Thank you

[Innky]

@doodlemania2

1. 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

[dmikolaj]

@girish where are we at with this solution in 7.2? My nextcloud talk won't work with the default turn settings, it only works when all the devices in the call are on the same local network. looks like my preconfigured by cloudron turn settings in nextcloud are on port 3478.

also if i overwrite my turn settings, where in your documentation are the settings located so i can restore to the cloudron defaults?

[joseph]

@dmikolaj is this spam?

[firmansi]

Actually I also still experience this issue, I can't make proper video call even after configure built-in TURN server, is there any port that should be set in firewall ?

[dmikolaj]

@joseph no this is not spam.

I tried both on your demo server and on my own test VPS to get nextcloud talk to work. The calls only work when both callers are on the same network which tells me that the turn server is not working. I also have a hetzner storage share nextcloud instance in which talk works out of the box in the same test scenario.

The hetzner nextcloud talk settings show their turn/stun server configured to port 443 and it works great.

I was wondering if I was doing something wrong, and have been looking through forums to try and see if there is a fix. So far it sounds like the built in cloudron turn server is not on port 443 which means it doesn't work reliably across all networks.

[nebulon]

It is correct, since Cloudron only has one server, where port 443 is occupied by the nginx reverse proxy, the turn server is not running on port 443. This can impact functionality depending on the local network setup. For this you can disable the usage of Cloudron's built-in turn server in nextcloud. See https://docs.cloudron.io/apps/#turn

Afterwards you can configure an alternative turn server, which works in your setup.

[firmansi]

@nebulon I guess the question (which not really provided in docs) is suggested port numbers that should be kept away from firewall

[nebulon]

@firmansi do you mean something like https://docs.cloudron.io/security/#inbound-ports or referring to something else?

[firmansi]

@nebulon yes, thanks

[andreasdueren]

I can heavily recommend running a dedicated turn server or even better the high performance backend for reliable NC Talk conversations. I have had only problems using the built in turn server.

[jdaviescoates]

@andreasdueren said in Nextcloud Talk not connecting calls:

the high performance backend

remind me, does that come with a turn server built in?

[andreasdueren]

@jdaviescoates I don't think necessarily, but you can use for example this repo which includes a turn server: https://github.com/sunweaver/nextcloud-high-performance-backend-setup

[sitedock]

Hi everyone i experienced the same problem but with an exiting background:
On a Cloudron that was spinned up at Feb 2021 NextCloud talk Calls from outside the local network doesn't work: Not connecting calls.
We just spinned up another Cloudron for another Team with the same configuration and the Nextcloud Talk Calls ran out of the box!
I don't want to attach another Service/Backend and i also don't want to "customize" the Firewall settings, but i would love to have a running NextCloud talk System on the older Cloudron too.
Maybe the Cloudron installation script changed in the last years so that it works now but not before..!?
Does it make sense or does anyone have an idea how to apply the same settings to the old cloudron?
I could maybe provide some infos of both instances. Maybe comparing the iptables settings would make sense?! I'm not a server-expert so a little help here would be much appreciated! Thanks!