strukturag / spreed-webrtc

WebRTC audio/video call and conferencing server.
GNU Affero General Public License v3.0
1.09k stars 259 forks source link

can't use TURN server with chrome #433

Open krodelabestiole opened 7 years ago

krodelabestiole commented 7 years ago

I've just setup a coturn server using both TLS (with signed csr) or not. I've configured spreed to use it (I use spreed with nextcloud) but I can't start a video call with chrome :

Oops Failed to create peer connection. See log for details.

I can't find much info in spreed's log. It works fine with Firefox though.

I have configured my TURN server in verbose mode and I can see a bunch of data when using firefox, but absolutely nothing when trying with chrome. no connexion attempt e.g.

this is what the config looks like for spreed : turnSecret = xxxxxxxxxxxxxxxxxxxx turnURIs = turns:turn.mydomain.com:555?transport=udp turns:turn.mydomain.com:555?transport=tcp turn:turn.mydomain.com:544?transport=udp turn:turn.mydomain.com:544?transport=tcp

I don't know where to look for a solution, it might be a bug with chrome or something ?

mabe-at commented 7 years ago

Hello!

Same here. We have used spreed and the spreed.me app (nextcloud) for a couple of months without any issues. But suddenly Chrome brings up the same error. 'Ooops Failed to create peer connection. See log for details.'.

We have used rfc5766-turn-server and now the latest coturn without any success.

It does work with Firefox without any problems.

Any hints to solve this are appreciated!

Kind regards, Matthias

krodelabestiole commented 6 years ago

when I append ?debug to the url I can get an error message with chrome : app.js:219 // Failed to create PeerConnection, exception: Maximum call stack size exceeded that might be of any help ?

without debugging I don't have any error message though, so I guess it might be due to the debugging functionnality itself...

no issue nor error message with firefox, with our without debugging.

johnfelipe commented 6 years ago

@mabe-at and @krodelabestiole how do u install coturn for be use with spreed?

krodelabestiole commented 6 years ago

debian package.

Package: coturn
Version: 4.5.0.5-1+b1

i'm not sure the issue is related to turn server though. i think latest docker image of spreed.me simply doesn't work with chrome. i will run more tests asap (unfortunately i'm very busy at the moment).

mabe-at commented 6 years ago

Finally, it looks like this issue is related with the nextcloud-app.

Chrome throws a Javascript error: 'Maximum call stack size exceeded'.

Which probably is not an issue of spreed-webrtc itself.

johnfelipe commented 6 years ago

@mabe-at then this https://github.com/strukturag/spreed-webrtc/issues/442 is not in this repo?

johnfelipe commented 6 years ago

@krodelabestiole my version is

root@cloud:/home/felipe# turnserver -v
0: log file opened: /var/log/turn_31579_2017-09-12.log
0:
RFC 3489/5389/5766/5780/6062/6156 STUN/TURN Server
Version Coturn-4.5.0.3 'dan Eider'
0:
Max number of open files/sockets allowed for this process: 1048576
0:
Due to the open files/sockets limitation,
max supported number of TURN Sessions possible is: 524000 (approximately)
0:

Need update to 4.5.0.5-1+b1?

mabe-at commented 6 years ago

@johnfelipe no idea. As it works with current Firefox and Opera, it looks like it's an issue with Chrome and the Nextcloud-App.

johnfelipe commented 6 years ago

@mabe-at do u review my steps https://github.com/strukturag/spreed-webrtc/issues/442, may be something is missing

mabe-at commented 6 years ago

@johnfelipe as i don't use snap, i cannot follow your steps. however restarting spreed-webrtc-server in my environment does not help.

mabe-at commented 6 years ago

Okay ... i have investigated the issue a little bit. The problem is the webrtc adapter. spreed-webrtc uses a pretty old version of https://github.com/webrtc/adapter

So probably it's not an issue with the Nextcloud app.

johnfelipe commented 6 years ago

@mabe-at do u run test and good? Pls share steps for nextcloud

mabe-at commented 6 years ago

@johnfelipe i have no solution. looks like we are switching to nextcloud 12 and get rid of spreed.me.

rferreiroa commented 6 years ago

@leonklingele this exactly the issue that i have now with chrome. Only say that Chrome with incognito session works too like with Firefox or Chromium.

rferreiroa commented 6 years ago

Perhaps we need to try to update the library that @mabe-at suggested before.

longsleep commented 6 years ago

The reason for the Maximum call stack size exceeded is the AdBlock Plus Extension. It breaks WebRTC in iframes. Solution is quite simple, just get rid of the extension. That's also the reason why it works in porn mode as there extensions are disabled by default.

johnfelipe commented 6 years ago

That is sweet, is working for me with snap, even i dont need restart service if deactive AdBlock:

pantallazo-0330

I will do more test, but working better

ghost commented 6 years ago

Deactivating Adblock Plus solves the problem here too. @longsleep are you considering having a workaround builtin spreed.me? I think a lot of people using adblock plus and are not aware that adblock plus is the reason for their problems.

thanks and cheers t.

rferreiroa commented 6 years ago

Ok, i´ll ty it. It would be nice to change this Warning for other saying this kind of things for example. Where is this warning located?

steel4me commented 6 years ago

I came across same problem. Chrome with activated Adblock Plus -> Failed to create peer connection. Firefox with actived Adblock Plus -> Working. Wow!

Other Adblocker in chrome -> Failed to create peer connection. Whitelisting don't work too. More Wow!