search

nextcloud / spreed

🗨️ Nextcloud Talk – chat, video & audio calls for Nextcloud
https://nextcloud.com/talk
GNU Affero General Public License v3.0
1.64k stars 437 forks source link

Since upgrade calls won't connect #9277

Closed Luticus closed 12 months ago

Luticus commented 1 year ago

Since I upgraded to the latest version of talk my calls will not connect, even if to and from the same network.

I have apache 2.4 on Debian 11 php 8.1/php-fpm Nextcloud 26 mariadb coturn for stun/turn no high performance backend (yet) no recording backend

I have confirmed that coturn is on and reachable. chat works and calls do ring through but they don't connect

firefox error log shows this: Connection failed. AHJmZN+e6MGqD+3vtC/7u6lObn+u/ZEdCNGu0FhLKAr1tWPtWZkvtBNMICMpz0S25JhD6ZjTeeLeW7214oufmLPom+iKU2EQ0tuXrhGoM0MQLBooqDQ84Qu5J0PsqOQ7aQ0SoNhYlrSrL3i5/d06K6c+G+/qzAtXtpiSinugfGhtj2ftdDFYU842w7eDPlosKsjQ+rV0EXJB2m4FNKS0XWVzeo7yWFLh63ys/DUxhAPruqqTXJdsCtYmfAUj4vj Object { id: Getter & Setter, parent: Getter & Setter, type: Getter & Setter, oneway: Getter & Setter, sharemyscreen: Getter & Setter, stream: Getter & Setter, receiverOnly: Getter & Setter, sendVideoIfAvailable: Getter & Setter, enableDataChannels: Getter & Setter, enableSimulcast: Getter & Setter, … } webrtc.js:864:4

Calls have historically worked fine.

Luticus commented 1 year ago

Narrowed it down, for whatever reason calls do not seem to work in firefox or firefox based web browsers so far. In chromium they seem to work fine.

nickvergessen commented 1 year ago

That could indicate a misconfigured coturn. IIRC there was a difference in usage between Firefox and Chrome

Luticus commented 1 year ago

I can double check my Coturn but historically calls have worked fine. My primary browser is Firefox so if there was an issue with Coturn and Firefox, I'd have seen it by now. My Coturn config hasn't changed in a long time, so I'm rather skeptical. Really I wanted to know if anyone else was experiencing this or if it was just me.

If there's any other info that is required here let me know and I'll add it.

Luticus commented 1 year ago

I don't know, I've tried pretty much everything on my turn server that I can think of. My /etc/turnserver.conf file matching the nextcloud recommended settings to the letter:

llistening-port=#### tls-listening-port=#### listening-ip=###.###.###.### verbose fingerprint use-auth-secret static-auth-secret=########################### realm=example.com total-quota=100 bps-capacity=0 stale-nonce=600 log-file=/var/log/turn.log syslog no-multicast-peers no-tlsv1 no-tlsv1_1

I've tried with stale-nonce, and total-quota set to 0/unlimited Tried with tls completely disabled. Tried with firefox set to a default profile. reset the shared secret. set verbose to watch logs.

Nothing. For the life of me, I can't understand what could possibly be wrong here.

This worked fine like a week ago before I upgraded to Nextcloud 26 and the newer version of talk.

Any configuration ideas, or directions I could be pointed in would be greatly appreciated.

I'm also considering upgrading my Coturn server to Debian 12 bookworm to see if maybe a newer version of Coturn would help, or perhaps even attempting to build the high performance backend again, stable Debian couldn't meet a dependency I think.

Luticus commented 1 year ago

I've tested with multiple configurations from talk as well. image

As you can see, talk thinks turn is reachable. So far all Chrome based clients seem to work, so does Nextcloud talk on Android.

Any firefox based client, such as librewolf or even firefox itself, shows this: image

nickvergessen commented 12 months ago

If this is still an issue for you, please reach out to the forums as this is more a configuration issue on your side and not a bug in talk in general: https://help.nextcloud.com/c/support/talk/52