Current issue with microphones on

Hi all!

in this thread we’ll communicate the actions we’re taking regarding the issues some users have been experiencing when connecting to’s service in the last few days.

To summarize, some users are unable to complete the echo test, receiving either a timeout error or a “1006” error from the BigBlueButton HTML5 client. They are then connected to the room, but can’t send audio to the other participants. This is what we have been able to find out so far:

  • The issue can be reproduced on the latest versions of Chrome for Android (96.0.4664.104), Windows (96.0.4664.110) and MacOS (96.0.4664.110). It is unclear whether the issue affects other, slightly older versions of Chrome. Chrome for Linux seems not to be affected.
  • Some users have reported a similar issue on Safari for iOS, but we’ve been unable to reproduce it so far.

This issue has been reported by other users both in BigBlueButton’s [1] and Chrome’s [2] issue trackers. It is apparently related to a the deprecation [3] of the Plan B method that Chrome was using to connect to WebRTC until recently. A similar issue has been reported by users of other videoconferencing platforms that use WebRTC, such as Jitsi [4]. This issue does not affect the most recent BigBlueButton releases.

There are a couple of client-side workarounds for the issue described above:

  • The first one is to use a different browser. Recent versions of Firefox, Edge (for Windows) and Safari (for MacOS) are unaffected as far as we can tell. Several users reported being able to connect normally to the service after switching to one of those alternative browsers.
  • Another workaround is to connect using Chrome, but connect to the audio stream using the dial-in feature instead of enabling the microphone on the browser.

We understand that these workarounds won’t work for all users, for example when having a session with a larger group of new participants, which may not be able to quickly change browsers or switch to a dial-in channel.

Therefore, the is already working on the deployment of a new server running a more recent version (2.3) of BigBlueButton. This will not be a full upgrade of’s infrastructure, which we were planning for January, but a temporary solution to mitigate this issue. In the coming hours we’ll let you know how to access this alternative service.

Again, we want to thank you all for your patience and your feedback.

In solidarity,
the :robot:

[1] Chrome browsers new version microphone issue · Issue #13936 · bigbluebutton/bigbluebutton · GitHub
[2] 1280590 - chromium - An open-source project to help move the web forward. - Monorail
[3] [WebRTC] Deprecate and Remove Plan B - Chrome Platform Status
[4] Jitsi stopped working about a week ago - #8 by jbg - Install & Config - Jitsi Community Forum - developers & users


Hey thanks for working to get us back on track! It makes a difference! :green_heart:

1 Like

Thanks for the detailed explanation @dvdjaco
It seems a bit more complex than just the browser version because I just came off a meeting with a colleague who was using Chrom Version 96.0.4664.110 (Official Build) (x86_64) on a Mac - and it worked fine!

Chrome Version 96.0.4664.110 (Official Build) (64-bit) - didn’t work for someone else on PC

So they Updated to 97.0.4692.71 but it still did not work :frowning:

The short answer is: Use FireFox - and BBB works fine

There have been systematic issues with server/browser communication arising in Chrome and BBB. Many/most of these should be fixed now, after upgrading our severs to BBB2.3. See status report here Some recent problems with my BBB rooms - #16 by Yurko

Thank you, folks! Like in most open source projects, what we lack in funding we make up for in generosity, patience, grit, and improvisation. I love being able to use again for all my meetings, and I am impressed with and grateful for the determination, skill, and perseverance of the ops team in making that happen. Thank you team! The Open Food Network loves you! :smiling_face_with_three_hearts:


Quick note that the issue has now been resolved on all servers.

We made a master thread here Microphone Issues on Big Blue Button 2.2 (Working)

And a further instance of fabulous tech support . . Yesterday a user mailed me to say an mp4 downlaod wasn’t available in Greenlight. Less than 24hr later the Tech detectives (@Yurko and others) have tracked and patched it . .

Looks like the processing script for mp4 was made for BBB 2.0, and its been working ever sicne the pre-compiled ffmpeg as part of that script no longer works with ubuntu 18 and no evidance of it being upgaded since then We are looking into options to fixing this issue. I tried using the stock ffmpeg that comes with ubuntu and although it did go through the motions of making an mp4 file, it did not generate one.
. . . OK mp4 is available, please confirm that it is as expected.

:green_heart: Eternal vigilance, in the face of software rust!


I’m writing to report that every time I connect to meet[dot]coop I have to clear cookies for meet[dot]coop for my microphone to work. @lauriewayne with Open Food Network convenes a group of us on meet[dot]coop once a week and it has happened each week for something like 5 or 6 weeks. I am using firefox 98.0.1 (64-bit) on Mac OS 12.0.1.


P.S. Sorry for having to put a [dot] in meet[dot]coop – there is a setting in which I am not allowed to add links as a first time poster to this discourse forum.

1 Like

That’s a dumb default :frowning:
@dvdjaco @Yurko @3wc is there a way to tell our Discourse instance that is not a link?!

Juliet, I’m not sure why you’d need to clear cookies every time again. As a regular user of Firefox this doesn’t happen to me; after the first time allowing a browser to share mic and webcam with, this is recorded and isn’t normally asked again. Could it be that you have a special cookie policy or plugins to that extent?

Yes that’s a policy on this forum for not allowing new forum users to post links - that’s a key step to reduce spam. Now that you have participated in the forum I think you’ll soon “earn” that right. Thanks for being here :slight_smile: