Google Meet audio and video streams not starting, console shows "WebRTC: ICE failed, add a STUN server"
Categories
(Core :: WebRTC, defect)
Tracking
()
People
(Reporter: hmitsch, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
84.43 KB,
text/html
|
Details |
Bug Scope
I am observing this on Firefox Release (104.0b9) and Nightly (105.0a1 (2022-08-11)) on macOS.
Test Condition
- Open Google Meet https://meet.google.com/
- Join a session with 5+ participants
Expected Result
- Video conferencing works
Actual Result
- Google shows the participants video streams
- All video streams are "empty," i.e., no content.
- There is no sound from the speaker(s).
Artifacts
Browser Console
The console shows this error:
WebRTC: ICE failed, add a STUN server and see about:webrtc for more details
about:webrtc Trace
See attached file aboutWebrtc_20220812_0919.html.
|
Reporter | |
Comment 1•3 years ago
|
||
Update: The issue also exists for video sessions with only 1 other participant.
|
||
Updated•3 years ago
|
|
||
Comment 2•3 years ago
|
||
So, meet is definitely not supplying any ICE servers. I wonder if they're hitting some bug in setConfiguration?
|
|
||
Comment 3•3 years ago
|
||
I have had no luck reproducing this; could you try reproducing with a new profile?
|
|
Reporter | |
Comment 4•3 years ago
|
||
Hi bwc,
I just reproduced on Firefox Release 104.0b9 with a clean, new profile.
Can I ask you for your test setup? What else could I do to help you analyze the issue?
Best regards,
Henrik
|
|
||
Comment 5•3 years ago
|
||
Is there any chance you're using a web proxy? Or maybe a VPN?
It is possible that a wireshark trace could shed some light on what is happening here.
|
|
Reporter | |
Comment 6•3 years ago
|
||
I am not using a web proxy or VPN. I will see if I can produce a wireshark trace.
|
|
Reporter | |
Comment 7•3 years ago
|
||
Ok, this is embarrassing ... I was working from a different location for the past 10 days. Today I returned home and ... Google Meet in Firefox Release and Nightly is again working like a charm.
I assume there was some weird IP/network setup in the remote location. It is strange that Safari was working, though.
As I no longer have access to the remote location, I will close this bug.
Thanks for helping me and sorry for creating the noise. Please accept my sincere apologies.
Best regards,
Henrik
Description
•