A phenomenon that suddenly cannot open the website in "Firefox" [Updated January 14]

It seems that the performance has suddenly decreased in the "Firefox" in the Windows environment, and there is a problem that the website cannot be opened.

The conditions for which this phenomenon occurred is not yet known, but when the information reported on "Twitter", etc., "Firefox 96, which was just released the other day.0 "and the combination of the Windows Security Update Program in January 2022 are suspected.However, there are reports that it will occur outside of Windows environment, and future surveys will be waiting.

[Added at 19:30 on January 13] Subsequent surveys revealed that it would occur regardless of the "Firefox" platform version."Windows Update" seems to be irrelevant, and is now considered to be a problem with HTTP3 connection.

「Firefox」で突如Webサイトが開けなくなる現象が発生中【1月14日更新】

As a countermeasure, there is a method of temporarily disabling the HTTP3 connection.First, enter "about: config" to the address bar and access the [Advanced] screen.

アドレスバーに「about:config」と入力して、[高度な設定]画面にアクセス

Next, "Network.http.http3.Switch the flag "Enabeld" (False).Enter "http3" in the search box and filter.The settings are now complete, but you should restart "Firefox" just in case.

[高度な設定]画面「network.http.http3.enabeld」というフラグを無効(false)に切り替える

If you are not sure, we recommend using a web browser other than "Firefox".

In addition, there is a view that disabling the telemetry function of "Firefox" can be avoided, but the root cause is the HTTP3 connection.Considering the possibility that other web services may cause problems, you should choose to disable HTTP3 connection.

[Added at 10:30 on January 14] According to Mozilla, the setting change of the cloud provider, which triggered the defect, was disabled, and the problem was successfully resolved.If it does not normalize yet, he wants to restart "Firefox".

Earlier toDay, Firefox Became Unresponsive Due To a Change in Defaults by a Cloud Provider Which Triggered A Firefox HTTP/3 BUG.We Disabled the Configuration Change and Confirmed THIS FIXED THE IsSUE.