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?

m-p{3}
link
76d

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.

@Reaton@lemmy.ml
link
77d

Just saw a toot about it: https://social.tcit.fr/@tcit/107614258789600399

How to fix Firefox if you’re having trouble today :
Kill the running Firefox process (through your favourite task manager, htop, whatever)
Access about:config
Search for network.http.http3.enabled and set it to false
Close Firefox and kill it again
Launch Firefox
Enjoy

Salamander
creator
link
16d

Thanks!

@const_void@lemmy.ml
link
56d

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/1481657624651313

@Nyaa@lemmy.ml
link
04d

Seems like it’s related to the telemetry according to replies

Salamander
creator
link
36d

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.

@Danacus@lemmy.ml
link
67d

Apparently auto-updates enabled HTTP3 which somehow broke everything.

Kromonos
admin
link
47d

HTTP3 was already enabled in last 94 and 95.0 releases.

Salamander
creator
link
26d

Oh, I was under the wrong impression that my Firefox was not auto-updated when using Arch Linux!

@Danacus@lemmy.ml
link
16d

I didn’t have any problems on Arch Linux, weird. I also thought Firefox didn’t auto-update on Linux.

@kevincox@lemmy.ml
link
1
edit-2
6d

Apparently HTTP3 was enabled but an update to Google’s implementation triggered a long-existing bug.

@Nyaa@lemmy.ml
link
4
edit-2
7d

Same here as of a while ago. I’m on Ubuntu 20.04 using the snap. Closing Firefox and trying to reopen it says that an instance is already open and won’t let me open it again for a few seconds.

It let me file a bug report from there so I filled it out and added details

A place to discuss the news and latest developments on the open-source browser Firefox

  • 0 users online
  • 8 users / day
  • 16 users / week
  • 40 users / month
  • 131 users / 6 months
  • 5 subscribers
  • 61 Posts
  • 321 Comments
  • Modlog