Talk only working locally (once again)
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.2k
- Forks
- 586
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 333
Description
Hi,
I feel this problem has been posted a million times but I can't get this working:
My NC has been up and running for a while and for third (or so) time I'm trying to get Talk to work as well. I have Jitsi Meet running flawlessly, but I can't get Talk to also work.
My NC sits behind a pfSense firewall with HAProxy that proxies various subdomains to various VMs (e.g. nextcloud.example.com and meet.example.com). And with this setup Jitsi Meet simply works. It doesn't need a TURN server.
But Talk only works when both (all) participants are on the local network. As soon as one participant is outside the local network, the call can't get connected. So I installed my own TURN server which seems to be working as it should because some Trickle Ice test page is able to gather a "relay" candidate. The TURN server is listening on port 3478 which is forwarded through my pfSense directly to the TURN server VM (running eturnal).
I have put the public (static) IP in Talk settings and it shows a "heartbeat" icon (rather than the red exclamation mark), so I'm guessing Talk is happy with my TURN server.
But alas, it does not work. Same as before, when a participant is outside my local network, the call can't get connected.
So I have put in the details of some public test TURN server (I could have easily made a mistake setting up mine despite Talk seeming to accept it). It works both on ports 80 and 443. Talk shows the "heartbeat" icon behind both entries (80 and 443). So Talk seems to be fine with that other TURN server.
But alas, it does not work. Same as before, when a participant...
What am I missing?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Nextcloud Talk settings alongside the pfSense/HAProxy forwarding setup and the eturnal TURN configuration. Reproduce a call with one participant outside the local network, then inspect the TURN and firewall behavior; done means external participants can connect reliably.
Written by the indexing model from the issue text.
Assessment
- Domain
- audio-video-rtc, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100