Audio/ microphone not working on Firefox

[leonidas-o]

I had some issues after updating BBB, so I simply deleted the /data and /conf dir, made sure I got a fresh git pull, executed ./scripts/setup, adapted the .env file generated ./scripts/generate-compose and started everything. I created the admin account, setup openid connect, here I had issues to login with the default admin credentials (was on bbb.mydomain.com/signin), only after I commented out the openid lines in .env I could login with the admin account and give my former logged in openid user admin role.
Don't know if this is a new feature or a bug that you can't login with the default admin user while openid is setup.

Nevertheless, the real issue now is, I can't connect with audio. When I enter the room, click on microphone, I see the dropdown, Audio volume is moving when I say something, but I can't hear the audio feedback.

There was an issue with your audio devices
We couldn't enable your microphone
Review your browser and system settings. Restart your browser and try again.
Error code: 0 - ICE negotiation timeout after 15s

Even audio only is not working, it take forever, saw some ICE error 1010 and that's it.

I can remember, that I had issues in the past because of NAT. I could solve that, everything was working. Haven't changed my setup, so the question is, am I running in the mentioned NAT issue of this version, or is there something I can do to fix that?

When listing the containers, it shows graphql-server-1 as unhealthy.

alangecker/bbb-docker-graphql-server:v3.0.4              "/entrypoint.sh /app…"   52 minutes ago   Up 52 minutes (unhealthy)              bbb-docker-bbb-graphql-server-1

with the following logs:

Restarting database bbb_graphql
DROP DATABASE
CREATE DATABASE
ALTER DATABASE
Creating tables in bbb_graphql
Starting hasura-graphql-engine
Waiting for Hasura's port (8085) to be ready...
{"detail":{"info":"EE client credentials not present in the metadata database. Hasura EE features are disabled.","kind":"license_info"},"level":"warn","timestamp":"2025-05-08T17:23:02.431+0000","type":"startup"}
Waiting for Hasura's port (8085) to be ready...
Applying new metadata to Hasura
{"level":"info","msg":"Help us improve Hasura! The cli collects anonymized usage stats which\nallow us to keep improving Hasura at warp speed. To opt-out or read more,\nvisit https://hasura.io/docs/latest/graphql/core/guides/telemetry.html\n","time":"2025-05-08T17:23:04Z"}
{"level":"info","msg":"Applying metadata...","time":"2025-05-08T17:23:04Z"}
{"level":"info","msg":"Metadata applied","time":"2025-05-08T17:23:07Z"}

Before the update I had the following image versions:

Redis 7.2 alpine
postgres 12-alpine
mongo 4.4
alangecker/bbb-docker-nginx 1.23-v5.0.2-v2.7.3
alangecker/bbb-docker-html5 v2.7.3
alangecker/bbb-docker-webrtc-sfu v2.12.0
alangecker/bbb-docker-recordings v2.7.3
alangecker/bbb-docker-pads v1.5.2
alangecker/bbb-docker-freeswitch v.1.10.10-v2.7.3
...
bigbluebutton/greenlight v3.0.6.1

[leonidas-o]

I just tested it on iPhone Safari and the Mac OS Safari, and on both Audio and Mic is working. So my setup is still good. It somehow has some issues with Firefox 138.0.1 (aarch64) on Mac OS.

[jdepi]

Dear leonidas, I had a similar issue in a non docker environment.
I could solve the issue by commenting two lines in /etc/turnserver.conf:
#denied-peer-ip=0.0.0.0-255.255.255.255
#denied-peer-ip=::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
Hope, it helps.

[leonidas-o]

Thanks but I think if everything works in other browsers but not in one particular, it's more likely a bug.
Nevertheless, I tried your approach, but it wasn't working here, the behavior was the same - on Firefox no audio with the same errors like above.

[jdepi]

It is mysterious. With this turnserver.conf configuration it works fine on my firefox v142.0.1 on LinuxMint.

[jdepi]

Leonidas, I just checked turserver.conf in the docker environment.
Please add the line allowed-peer-ip=xx.xx.xx.xx and change xx.xx.xx.xx with your server's ip address, then:
docker compose down
docker compose up -d

[leonidas-o]

Thanks for still trying, but nope, not working for me either, firefox still same error.

[ben-ba]

for your issue with graphql server
#367

[leonidas-o]

@ben-ba nice, that fixed the graphql issue, thanks for that. One issue less

[ben-ba]

firefox handles webrtc connections in another way than chrome based browsers.

u can try to force turn server use for firefox, see more details about that and the issues with firefox here:

https://docs.bigbluebutton.org/support/troubleshooting/#im-having-troubles-seeing-webcams-or-screen-sharing-in-firefox

the article describe this for the removed kurento, on serverside, here is a method to force this on client side, but user based (for testing only)

https://docs.bigbluebutton.org/administration/turn-server/#test-your-turn-server

here is the direct link to the mentioned issue bigbluebutton/bigbluebutton#13746