search

strukturag / spreed-webrtc

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

Failed to Create PeerConnection Maximum call Stack Size Exceeded #440

Open aliasger52mail opened 7 years ago

aliasger52mail commented 7 years ago

I am getting this error in spreed.me with next cloud 2017-09-07_1415

2017-09-07_1416

Please do some help

aliasger52mail commented 7 years ago

Please give some solution for the above errors

leonklingele-work commented 7 years ago

Are you using a STUN / TURN server in your setup? See this comment: https://github.com/strukturag/nextcloud-spreedme/issues/57#issuecomment-257885080

johnfelipe commented 7 years ago

Is not working with TURN server, pls give me more option for resolve this issue stay alert

madmath03 commented 6 years ago

Same issue here, but for some reason, it seems to depend on the browser.

Using Chrome "normally" I get the issue, but when I switch to private navigation with Chrome or even a Firefox, it works fine. I have cleaned the Chrome cache and cookies, installed a coturn server but I still get the issue through Chrome.

I have no clue to what's causing this issue... Anyone figured this out ?

johnfelipe commented 6 years ago

do u have Adblock in chrome? Show your turnserver config file

madmath03 commented 6 years ago

I do have Adblock enabled. Tried turning it down globally but I still get the "Maximum call stack size exceeded" error.

Here is the extract of my turn server config :

LISTENING_PORT=3478
TLS_LISTENING_PORT=5349
ALT_LISTENING_PORT=3479
ALT_TLS_LISTENING_PORT=5350

LISTEN_IPS="SERVER_IP"

RELAY_IP=SERVER_IP

STATIC_AUTH_SECRET=2c30...

REALM=my_turn_server_fqdn

VERBOSE=1
LOG_FILE=/srv/turnserver.log
johnfelipe commented 6 years ago

how u install spreedme? do u install for NC instance?

madmath03 commented 6 years ago

I set up a docker-compose containing, among other things, a Nextcloud instance, this spreed docker image and this strukturag/docker-webrtc-turnserver docker image.

My NextCloud and Spreed are accessed through a Nginx reverse proxy.

The initial spreed configuration was generated through NC admin interface. I then generated and added the turnSecret and setup the turnURIs like this : 

turnSecret = 2c30...
turnURIs = turn:my_turn_server_fqdn:3478?transport=udp turn:my_turn_server_fqdn:3478?transport=tcp

I also tried commenting the stunURIs in the spreed config, to force the use of the turn server, but it did not change anything.

johnfelipe commented 6 years ago

stunURIs, put stunURIs = void, and remember restart coturn and spreedme

madmath03 commented 6 years ago

We did some more tests on our side and turns out it is AdBlock which is causing the issue. SImply pausing AdBlock is not enough, you need to completely disable it in Chrome extensions...

What I wonder though is why does AdBlock prevent P2P connections. Does anyone know if it is a bug on the NextCloud Spreed.me app, the Spreed.me server or simply Chrome's AdBlock extension ?