I am not able to load any websites with Firefox on my PC despite having an internet connection. I went on Reddit and found other people complaining of the exact same issue, so it appears to be a problem with firefox: https://www.reddit.com/r/firefox/comments/s2u7eg/is_firefox_down/

My phone’s firefox browser works fine.

What can cause a browser to fail this way?

  • Danacus
    9·
    3 years ago

    Apparently auto-updates enabled HTTP3 which somehow broke everything.

  • m-p{3}
    8·
    3 years ago

    https://www.reddit.com/r/firefox/comments/s2utvv/comment/hsgrt6v/?utm_source=share&utm_medium=web2x&context=3

    Stickied your post for visibility.
    Edit: It’s been fixed already.

    Firefox has witnessed outages and we are sorry for that. We believe it’s fixed and a restart of Firefox should restore normal behaviour. We will provide more information shortly.

    Also, disabling telemetry doesn’t fix this issue anymore, the telemetry servers weren’t the root cause and have been adjusted already.

    Our current suspicion is that Google Cloud Load Balancer (or a similar CloudFlare service) that fronts one of our own servers got an update that triggers an existing HTTP3 bug. Telemetry was first implicated because it’s one of the first services a normal Firefox configuration will connect first, but presumably the bug will trigger with any other connection to such a server. Our current plan is to disable HTTP3 to mitigate until we can locate the exact bug in the networking stack.

  • const_void
    7·
    3 years ago

    They claim a ‘cloud provider’ they use went down and that’s what caused all of this. The real question is why is there an always-on cloud connection in Firefox and why is it so important that the browser stops working if that server can’t be reached. Super fishy…

    https://twitter.com/firefox/status/1481657624651313155

    edit: fix link

    • Salamander@mander.xyzOP
      6·
      3 years ago

      The URL is missing a few numbers: https://twitter.com/firefox/status/1481657624651313155

      The tweet says:

      “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.”

      To be honest, I don’t understand what “a change in defaults by a cloud provider” even means. But it smells fishy indeed.