5 ms·

I really hope the auto-update component doesn't have the same issue, otherwise Firefox is essentially dead on millions of computers owned by non-techies.

by styeco 5y ago

dantondwa 5y ago
Exactly what I was thinking. I hope they thought about this case and made the updater use a different stack...
- perlwle 5y ago
  Auto-Update doesn't work anymore. It's the first thing I tried when encounter this issue like 20 minutes ago. Can't access any website or making any connection without disable `network.http.http3.enabled` and restart. This impact is huge for million of firefox users!
  - rightbyte 5y ago
    Good. Abusing the users for testing via forced auto updates is short sighted and hopefully enough people change browser that Mozilla change their ways.
kimi 5y ago
I hope i am mistaken, but the auto-updater of my own FF was blocked.
- nottorp 5y ago
  There is something about being unable to check for updates if you open the console on any site...
Santosh83 5y ago
I fear not. With http3 enabled, the auto-updater never returns a result. It keeps saying "checking...". Looks like the auto-updater itself will work only when http3 is disabled through about:config which non-technical people may not be able to do. However I do recall Mozilla having another backdoor channel which they used sometime ago to push an emergency update. I hope that works.
foxfluff 5y ago
I can confirm auto-updater got broken too. When I realized my browser (nightly) was borked, first instinct was to update.. but nope, that didn't work. Then I manually downloaded a new nightly tarball, but that also didn't help. Switched to stable (95.0.2) and that worked once, then it got borked too.
Vinnl 5y ago
Someone just reported that it looks like a load balancer issue. Presumably, if that's the case it can also be fixed without user action: https://bugzilla.mozilla.org/show_bug.cgi?id=1749908#c17 https://bugzilla.mozilla.org/show_bug.cgi?id=1749908#c17
stef25 5y ago
Several non techie friends already contacted me about a broken FF. There will be millions of people with this problem, indeed.
deleted 5y ago
[deleted]
schroeding 5y ago
Was blocked on my machine too, but spontaneously started working again after a complete reboot without the disable http3 fix, so there is hope! :D

I really hope the auto-update component doesn't have the same issue, otherwise Firefox is essentially dead on millions of computers owned by non-techies.

by styeco 5y ago

I really hope the auto-update component doesn't have the same issue, otherwise Firefox is essentially dead on millions of computers owned by non-techies.

dantondwa 5y ago

Exactly what I was thinking. I hope they thought about this case and made the updater use a different stack...

perlwle 5y ago
Auto-Update doesn't work anymore. It's the first thing I tried when encounter this issue like 20 minutes ago. Can't access any website or making any connection without disable `network.http.http3.enabled` and restart. This impact is huge for million of firefox users!
- rightbyte 5y ago
  Good. Abusing the users for testing via forced auto updates is short sighted and hopefully enough people change browser that Mozilla change their ways.

kimi 5y ago

I hope i am mistaken, but the auto-updater of my own FF was blocked.

nottorp 5y ago
There is something about being unable to check for updates if you open the console on any site...

Santosh83 5y ago

I fear not. With http3 enabled, the auto-updater never returns a result. It keeps saying "checking...". Looks like the auto-updater itself will work only when http3 is disabled through about:config which non-technical people may not be able to do. However I do recall Mozilla having another backdoor channel which they used sometime ago to push an emergency update. I hope that works.

foxfluff 5y ago

I can confirm auto-updater got broken too. When I realized my browser (nightly) was borked, first instinct was to update.. but nope, that didn't work. Then I manually downloaded a new nightly tarball, but that also didn't help. Switched to stable (95.0.2) and that worked once, then it got borked too.

Vinnl 5y ago

Someone just reported that it looks like a load balancer issue. Presumably, if that's the case it can also be fixed without user action: https://bugzilla.mozilla.org/show_bug.cgi?id=1749908#c17 https://bugzilla.mozilla.org/show_bug.cgi?id=1749908#c17

stef25 5y ago

Several non techie friends already contacted me about a broken FF. There will be millions of people with this problem, indeed.

deleted 5y ago

[deleted]

schroeding 5y ago

Was blocked on my machine too, but spontaneously started working again after a complete reboot without the disable http3 fix, so there is hope! :D