3 ms·

Genuinely, I cannot reproduce the issue. I ensured that both DoH (set to Cloudflare) and H3 are enabled but didn't hit the snag, so either Cloudflare has a bugg

Genuinely, I cannot reproduce the issue. I ensured that both DoH (set to Cloudflare) and H3 are enabled but didn't hit the snag, so either Cloudflare has a buggy deployment or the hunch (https://bugzilla.mozilla.org/show_bug.cgi?id=1749908#c6 https://bugzilla.mozilla.org/show_bug.cgi?id=1749908#c6) that it's telemetry activating H3. Update: using Google's (the horror) DoH, and I didn't notice problems. Might just be CF having a bad H3 deployment, but I want to know what bug it triggered on FF. Update 2: To clarify, CF did indeed hang FF, but also Google, which is know for at least bothering to monitor complaints (and dns.google is still H2). Trying to disable telemetry now. Update 3: incoming.telemetry.mozilla.org is still H2. Can someone give me the other domains of MozTelemetry? Browser still working as of the moment. Update 4: Telemetry was indeed H3'd: https://bugzilla.mozilla.org/show_bug.cgi?id=1749908#c17 https://bugzilla.mozilla.org/show_bug.cgi?id=1749908#c17, me angery right now.

jack_pp 5y ago
I think it has been fixed, I didn't do any fixing on my own and it just worked after 20-30 minutes again
- jacquesm 5y ago
  It goes up and down as long as that http3 setting is enabled, if you disable it it just works and continues to work. I've had it working intermittently all morning but after that setting got set to false it never failed.
- matsemann 5y ago
  I had the issue earlier today, then after a restart it went away. Not 3 minutes ago it started happening again. A restart then didn't work, but disabling http3 got me up and running.
terom 5y ago
Did you have telemetry disabled? It sounds like users with telemetry disabled were not affected. EDIT: https://bugzilla.mozilla.org/show_bug.cgi?id=1749908#c19 https://bugzilla.mozilla.org/show_bug.cgi?id=1749908#c19 this is seemingly not the case, other HTTP/3 services can also trigger the same bug, telemetry just happens to be the most common / first to be triggered

jack_pp 5y ago

I think it has been fixed, I didn't do any fixing on my own and it just worked after 20-30 minutes again

jacquesm 5y ago
It goes up and down as long as that http3 setting is enabled, if you disable it it just works and continues to work. I've had it working intermittently all morning but after that setting got set to false it never failed.
matsemann 5y ago
I had the issue earlier today, then after a restart it went away. Not 3 minutes ago it started happening again. A restart then didn't work, but disabling http3 got me up and running.

terom 5y ago

Did you have telemetry disabled? It sounds like users with telemetry disabled were not affected. EDIT: https://bugzilla.mozilla.org/show_bug.cgi?id=1749908#c19 https://bugzilla.mozilla.org/show_bug.cgi?id=1749908#c19 this is seemingly not the case, other HTTP/3 services can also trigger the same bug, telemetry just happens to be the most common / first to be triggered