Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

WebRTC seems broken

  • 2 replies
  • 1 has this problem
  • 1 view
  • Last reply by Søren

more options

After upgrading to Firefox 76 WebRTC is broken. Trying on other machines shows the same. Even an older one with Firefox 75 was broken.

https://test.webrtc.org/ shows the problem. Zero video bandwith, although camera, sound and network is fine:

Video bandwidth

[ FAILED ] Frame rate mean is 0, cannot test bandwidth without a working camera. [ INFO ] Send bitrate mean: NaN kbps [ INFO ] Send bitrate standard deviation: NaN kbps [ INFO ] RTT average: 0 ms [ INFO ] RTT max: 0 ms [ INFO ] Packets lost: -1

Chrome works fine

After upgrading to Firefox 76 WebRTC is broken. Trying on other machines shows the same. Even an older one with Firefox 75 was broken. https://test.webrtc.org/ shows the problem. Zero video bandwith, although camera, sound and network is fine: Video bandwidth [ FAILED ] Frame rate mean is 0, cannot test bandwidth without a working camera. [ INFO ] Send bitrate mean: NaN kbps [ INFO ] Send bitrate standard deviation: NaN kbps [ INFO ] RTT average: 0 ms [ INFO ] RTT max: 0 ms [ INFO ] Packets lost: -1 Chrome works fine

Chosen solution

It seems fixed in 76.0.1

Read this answer in context 👍 0

All Replies (2)

more options

Meaning Google meet and meet.jit.si is no longer working. Bit of a pain when working remotely...

more options

Chosen Solution

It seems fixed in 76.0.1