search

bigbluebutton / bigbluebutton

Complete open source web conferencing system.
https://bigbluebutton.org
GNU Lesser General Public License v3.0
8.54k stars 5.95k forks source link

Time out error - ICE 1010 only in Firefox #19357

Open alyfilipe opened 10 months ago

alyfilipe commented 10 months ago

Hello,

We have a fully functional BBB 2.5 installation. To update to version 2.7, we created a new server and applied the installation from scratch, which is finished and without errors. However, we were unable to get it to work in Firefox. Does not enable audio when entering the room, giving ICE 1010 error. In other browsers, everything works normally.

To Reproduce Steps to reproduce the behavior:

  1. Go to a room
  2. Click on start or participate
  3. Enable Audio
  4. See error

Expected behavior Audio connected

Actual behavior Error ICE 1010

BigBlueButton Server 2.7.3 (492) Kernel version: 5.4.0-164-generic Distribution: Ubuntu 20.04.6 LTS (64-bit)

Captura de tela de 2023-12-22 18-45-41 Captura de tela de 2023-12-22 18-45-06

jezekus commented 8 months ago

Having same error on fresh new installation with Firefox

Kaor commented 8 months ago

Same error on fresh installation with Firefox

rschoene commented 8 months ago

Same error on Firefox under Windows 10, more Info:

[19:38:15:0202] DEBUG: clientLogger: SFU audio offer generated https://bbb.<...>.de/bbb-008/html5client/<...>.js?meteor_js_resource=true:649:1507869 [<...>.js:132:101324](https://bbb.<...>.de/bbb-008/html5client/<...>.js?meteor_js_resource=true)
[19:38:15:0330] DEBUG: clientLogger: Start request accepted for audio https://bbb.<...>.de/bbb-008/html5client/<...>.js?meteor_js_resource=true:649:1517886 [<...>.js:132:101324](https://bbb.<...>.de/bbb-008/html5client/<...>.js?meteor_js_resource=true)
[19:38:29:0551] ERROR: clientLogger: SFU audio failed https://bbb.<...>.de/bbb-008/html5client/<...>.js?meteor_js_resource=true:649:1592932 [<...>.js:132:101324](https://bbb.tu-dresden.de/bbb-008/html5client/<...>.js?meteor_js_resource=true)
[19:38:29:0557] DEBUG: clientLogger: Stopped broker session for audio https://bbb.<...>.de/bbb-008/html5client/<...>.js?meteor_js_resource=true:649:1520339 [<...>.js:132:101324](https://bbb.<...>.de/bbb-008/html5client/<...>.js?meteor_js_resource=true)
[19:38:29:0560]  INFO: clientLogger: Audio ended without issue https://bbb.<...>.de/bbb-008/html5client/<...>.js?meteor_js_resource=true:649:1492719 [<...>.js:132:101324](https://bbb.<...>.de/bbb-008/html5client/<...>.js?meteor_js_resource=true)
[19:38:29:0568] ERROR: clientLogger: Audio error - errorCode=1010, cause=ICE negotiation timeout after 15s [https://bbb.<...>.de/bbb-008/html5client/<...>](https://bbb.<...>.de/bbb-008/html5client/<...>.js?meteor_js_resource=true:649:1493034)
IT-Bob commented 7 months ago

I have the same issue with BigBlueButton server version 2.7.5 on Ubuntu 20.04.6, with Firefox 123 and Ungoogled Chromium 122.0.6261.111 on Linux. No issue with Chromium 111.0.5563.64.

Audio and webcam feedback works, but when I click on Join audio or start sharing I get the ICE 1010 error, or the video doesn't work without error.

I've no error nor warning with the bbb-conf --check command.

alyfilipe commented 7 months ago

BBB is not usable with these errors. Maintaining an old version is not an option. It's always very difficult to make it work behind a NAT. Many errors and few answers. We are looking at other webconference options

Thanks

ccoenen commented 6 months ago

I have recently also developed these problems. This used to work fine before and for ~2 weeks now, I can't use Firefox or Ungoogled-Chromium with BBB 2.7.6 any more. Sadly I don't have knowledge which versions we ran at which point in time, so I don't know if a Firefox Update or a BBB update broke it, or if something else about our setup has shifted around.

prlanzarin commented 6 months ago

No significant changes in the audio area for BBB version timespan outlined in the comments here.

If nothing changes, please attach relevant information - full, uncropped server logs from /var/log/bbb-webrtc-sfu/bbb-webrtc-sfu.log, and full console logs.

ccoenen commented 6 months ago

On our servers I get an easily reproducible 1010 error in firefox and ungoogled chromium. test27.bigbluebutton.org works fine. demo.bigbluebutton.org, which connected me to demo6.bigbluebutton.org is also working fine. I will try your suggestion in my defunct setup next and update this post accordingly.

Sorry, I don't have control over the server administration, so I can't change and test this myself. I will forward this info to our admins though. Thank you very much!

prlanzarin commented 6 months ago

On our servers I get an easily reproducible 1010 error in firefox and ungoogled chromium. test27.bigbluebutton.org works fine. demo.bigbluebutton.org, which connected me to demo6.bigbluebutton.org is also working fine. ~I will try your suggestion in my defunct setup next and update this post accordingly.~

Sorry, I don't have control over the server administration, so I can't change and test this myself. I will forward this info to our admins though. Thank you very much!

Ok. Ask them to review their TURN servers as well. The problem is usually there.

ccoenen commented 6 months ago

My IT department was able to fix our setup thanks to your help @prlanzarin, thank you very much. From what I hear, I believe it was the forceRelayOnFirefox setting. Of course, I can't know if the original poster has the exact same problem and solution.

prlanzarin commented 6 months ago

My IT department was able to fix our setup thanks to your help @prlanzarin, thank you very much. From what I hear, I believe it was the forceRelayOnFirefox setting. Of course, I can't know if the original poster has the exact same problem and solution.

@ccoenen Good, but be aware that my suggestion to disable that flag was merely to try and pinpoint the underlying issue. The fact that turning it off "solved" the issue means that the TURN instances being used by your BBB installation are malfunctioning.

I recommend relaying this info to your IT department. The TURN instances should be checked upon - if they're using the built-in ones, make sure to restart the coturn service and try again with the forceRelayOnFirefox flag enabled. The coturn service is known to misbehave after a long enough uptime, so a periodic restart on idle times (eg via a cron job) is advised.

For added context: the forceRelayOnFirefox flag is important to circle around a Firefox implementation issue. It's an edge case, most Firefox scenarios work fine without it - but some specific users may be affected by that flag being inactive.

ccoenen commented 6 months ago

thank you for clarifying, I will forward this to my IT department!