Hi there,
Thank you for making demo server happen!
We just tested it internally, my PopOS/Ubuntu worked like a charm on Firefox.
However Hannah, the other Animorph, encountered to issues on Mac+Firefox:
Could not enable their microphone (they could not hear me either), we could do only text chat.
The error was connection failure ICE error 1007, please find screenshot below.
After the error system would still try to connect to the echo test to no avail. When Hannah used Chrome it worked at first attempt though 1007 would pop up again next time round, but was fine after refreshing.
Hannah encountered another error when trying to launch video on Firefox Media could not reach the server [error 1020] Did work on Chrome, will spare you the screenshot.
Hope this is somewhat relevant, thank you for all your work on this!
Thanks for testing @szczepan_animorph! Searching up a bit on those errors leads me to think that it is connection problems which can be helped with better supporting the TURN server. We’re tracking that via this ticket.
I updated some packages last night and then applied our Ansible role to 2 of the 3 servers we had at the time but it was late and I forgot to apply it to demo.meet.coop, it is running now, can you try again in 5 minutes or so?
Encountered same error before on our own instance, think it was because we misconfigured the TURN and once that was fixed it never happened again for months.
Looking back at our chat logs, I think Elon upgraded BBB and the upgrade process overwrote the config file, so these reverted to default it looks like:
stunServerAddress
stunServerPort
I believe pointing to the correct address and port fixed it.
chrome://webrtc-internals (chrome) and about:webrtc (firefox) can be used to debug these issues.
Usually it happens when there is a Nat in the way. In our case it was because BBB was behind a Nat, but not exclusively.
And yes we found that upgrading causes configs to get overwritten.
I should point out that STUN and TURN are important to establish a good connection with correct ip addresses so its a good place to check.
ICE tries to find the best path to connect peers. It tries all possibilities in parallel and chooses the most efficient option that works. ICE first tries to make a connection using the host address obtained from a device’s operating system and network card; if that fails (which it will for devices behind NATs) ICE obtains an external address using a STUN server, and if that fails, traffic is routed via a TURN relay server.
Do you know which config file? The /etc/turnserver.conf file is on the TURN/STUN server itself and the config on the BigBlueButton server with the TURN/STUN server settings is /usr/share/bbb-web/WEB-INF/classes/spring/turn-stun-servers.xml and those variables don’t appear in that file:
We are putting server specific variables in the hosts.yml file in the servers repo, see for example the current variables for the BBB servers, at the moment the only variables not in this file are the ones for creating users accounts, see the host_vars files for these. This means that there is basically one file with all the settings in it, hosts.yml, we are also setting variables that apply to groups of servers in that file, for example see the list of variables for the TURN/STUN servers. At some point it might make sense to split this into separate files but at the moment just having one file with everything in keeps it simple.
Quite a few more than 5 minutes, but have just tested on Firefox, Chrome and Safari on Mac and no errors. Thank you Chris! Enjoy the other aspects of the bug hunt!
Video mirroring in video chats = seeing ourselves as if in a mirror, rather than as another person sees us . . the usual default for Zoom, Skype etc. But seems not to be an option in BBB.
Pardon me, I forgot ‘mirroring’ has other meanings in the world of servers.
