Live data from Hacker News

Ask HN: Firefox connection problems after enabling DoH?

news.ycombinator.com

131–140 of 410 posts

Re: Ask HN: Firefox connection problems after enabling DoH?

#132
post #73

It is time for Mozilla to stop messing around. They are losing user trust extremely fast. A silent FireFox update that cripples the browser? No active update was done since yesterday and this morning: a broken browser. Please stop non-browser development and let me pay a monthly fee for a decent browser! I don’t want a VPN service, bookmark readers or other crap. I want Mozilla to defend the open web and create an op…

I don't understand the anger about the VPN. I think it's a good idea. Reader mode is useful, especially if you block a lot of CSS and JavaScript by default with uMatrix. I don't know why people use DOH anyway. It bypasses your hosts file, so you can't block things as easily.

>It bypasses your hosts file

It doesn't bypass my hosts file... I have a couple of locally hosted websites that I have rules in /etc/hosts for, and Firefox resolves them correctly even with DOH enabled.

Re: Ask HN: Firefox connection problems after enabling DoH?

#133
post #35
post #31

I feel a symptom I've been having for a couple of days could be related, but I can't be sure: There's a site I can only access via a personal VPN connection. If I try to access it while on the VPN, it works immediately. If I try to access it off the VPN, realise it's not accessible because I'm not on the VPN, connect to the VPN and try again, it takes a good 30s to a minute to get to. Feels like Firefox waits some am…

Did you try the more aggressive shortcut ctrl + shift + R / F5? (Not sure if it was this hotkey exactly)

Yeep.

Re: Ask HN: Firefox connection problems after enabling DoH?

#134
post #104
post #6

What worked for me was disabling HTTP3 support with the 'network.http.http3.enabled' key in about:config and then restarting Firefox. Seems like it's stuck in the 'SocketThread', repeatedly doing this: 2022-01-13 08:20:53.075936 UTC - [Parent 4106991: Socket Thread]: V/nsHttp Http3Stream::OnReadSegment count=333 state=4 [this=7f6e295623a0]

Yep, works. However, you need to magically restart the browser. Apperently, it runs some background processes whose names contain neither the character sequence "firefox", nor "mozilla", according to pgrep.

GeckoMain

Re: Ask HN: Firefox connection problems after enabling DoH?

#135

I generally use Firefox ESR and don't have any problems. (Note: if you use Slack things are a bit broken sometimes in Firefox ESR. In fact, there's a notice that they'll stop supporting this browser on March 1. I haven't noticed any other broken sites though.) Last time Firefox wouldn't connect to stuff (Google sites) even though every other browser would (March 21~22, 2017, but I think that was a problem that didn't…

ESR versions were reportedly affected as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1749908#c2

Re: Ask HN: Firefox connection problems after enabling DoH?

#136
What is going on at Mozilla? It's getting harder to stay faithful to the organization supposedly representing the open web. They are acting more like the profit-first companies that are strangling our use of the internet. Starting a browser to a blank page should not make any outbound connection until the user requests something. Apparently their HTTP3 support is choking while trying to connect to some centralized service. This is an unacceptably poor engineering design.

Re: Ask HN: Firefox connection problems after enabling DoH?

#137
post #6

What worked for me was disabling HTTP3 support with the 'network.http.http3.enabled' key in about:config and then restarting Firefox. Seems like it's stuck in the 'SocketThread', repeatedly doing this: 2022-01-13 08:20:53.075936 UTC - [Parent 4106991: Socket Thread]: V/nsHttp Http3Stream::OnReadSegment count=333 state=4 [this=7f6e295623a0]

Thank you very much, this fixed it for me as well! :)

Re: Ask HN: Firefox connection problems after enabling DoH?

#139

Other workaround: Go to preferences -> Firefox Data Collection and uncheck everything. Then restart Firefox[0] This might be better then disabling http3 as Firefox would stop working in the future when http2 is depreciated. [0] https://bugzilla.mozilla.org/show_bug.cgi?id=1749908#c6

If the Mozilla telemetry service can trigger a HTTP/3 DoS bug, then I would assume that any server can trigger the same HTTP/3 DoS bug. I think I'll keep http3 disabled for now, until this is figured out and fixed.

EDIT: https://bugzilla.mozilla.org/show_bug.cgi?id=1749908#c21 yes, it's not just telemetry

Post reply on HN