doxy.me incident

Audio and Video Problems with Firefox 80.0

Minor Resolved View vendor source →

doxy.me experienced a minor incident on August 25, 2020 affecting Doxy.me webpages, lasting 71d 14h. The incident has been resolved; the full update timeline is below.

Started
Aug 25, 2020, 10:22 PM UTC
Resolved
Nov 05, 2020, 01:11 PM UTC
Duration
71d 14h
Detected by Pingoru
Aug 25, 2020, 10:22 PM UTC

Affected components

Doxy.me webpages

Update timeline

  1. investigating Aug 25, 2020, 10:22 PM UTC

    We have identified an issue with audio and video not working when using Firefox 80.0. Please use Google Chrome while this is being resolved.

  2. investigating Aug 26, 2020, 01:54 PM UTC

    We are continuing to investigate this issue caused by some of the changes introduced with the Firefox 80.0 update. There has been a temporary workaround identified: 1) You can open your Firefox browser and search "about:config" in the url. Then Select Accept the Risk and Continue button on page 2) From there you can find and update by typing in "media.peerconnection.video.use_rtx" then click the arrow toggle to switch the setting to false to resolve this issue. We are continuing to look into a permanent fix. Google Chrome and Microsoft Edge are also viable options if you are unable to change these settings on your browser.

  3. investigating Aug 26, 2020, 02:14 PM UTC

    We are continuing to investigate this issue.

  4. identified Aug 27, 2020, 03:02 PM UTC

    We have identified the underlying cause for these issues, which are related to the browser update released on 8/25. Our third-party provider has acknowledged the issue and is working on a resolution.

  5. identified Sep 17, 2020, 03:04 PM UTC

    Our real time communications vendor is testing a fix that would resolve the audio and video issues when using new versions of Firefox.

  6. monitoring Oct 29, 2020, 07:21 PM UTC

    A fix for the Firefox Audio and Video issue has been deployed. We are continuing to monitor the results.

  7. resolved Nov 05, 2020, 01:11 PM UTC

    This incident has been resolved.