Все продукты: форум сообщества

Hello :D

I seem to e having a problem with Firefox in that whenever I use it, my entire internet slows down to barely a crawl. I have tried several things, including turning off efficiency mode in the config.

I have tried various DNS and Proxy fixes I've seen on reddit and these forums, including turning of proxy and dns over https as well as reinstall the browser. It is only firefox that does this to my network.

I got Windows 11 Home edition and my network is a fiber network

Any help would be appreciated.

The server at biz209.vodien.com:2096 is taking too long to respond.

Moderator note: This question has been edited to correct the link formatting.

I’ve been troubleshooting a strange networking issue in Firefox that I haven’t been able to pin down, and it seems to be specific to Firefox’s network stack rather than my system or connection.

On several high-traffic sites that sit behind Cloudflare (Discord, Shopify storefronts, some SaaS dashboards), Firefox occasionally stalls during page load. The request shows up in the Network panel as pending for several seconds before finally completing. Sometimes the page partially renders and then hangs until the stalled requests finish.

A few things that make this confusing:

• The same sites load instantly in Chromium-based browsers on the same machine and network • The issue persists even in Firefox Troubleshoot Mode with extensions disabled • DNS over HTTPS on/off does not appear to change behavior • Packet captures show the TCP connection is established quickly, but some HTTP/2 streams appear to wait before data begins flowing • If I force HTTP/1.1 using a proxy for testing, the issue disappears

System details:

OS: Windows 11 Firefox: latest stable release Connection: fiber, low latency, no packet loss locally No system proxy configured

Things I’ve already tried:

• Clearing cache and site data • New Firefox profile • Disabling hardware acceleration • Testing with network.http.http2.enabled toggled • Comparing HAR logs with Chromium

One thing I noticed in the Firefox networking logs is that multiplexed streams sometimes wait behind earlier streams longer than expected, almost like there’s some internal prioritization or queue behavior happening. I’m wondering whether this could be related to HTTP/2 prioritization logic, connection coalescing, or how Firefox handles Cloudflare edge endpoints.

Has anyone seen similar behavior or knows whether there are any advanced networking prefs in about:config worth experimenting with (connection limits, HTTP/2 concurrency, etc.)?

Curious if this might be a known quirk with certain CDNs or just something unique to my environment.

So basically, I'm trying to add a 2FA code, homever when I scanned the code using google authenticator, everything went normal. Homever, when I try to put in the code, firefox only lets me put 5 digits but not 6. Any solutions?

I got a Firefox update recently and have not been able to access Flickr since then. I am getting a message that the page is not redirecting correctly. I am attaching the error message. I am running with standard firefox protection. I have cleared cache and cookies. I have also added Flickr as an exception to Firefox enhanced privacy tracking. Firefox is up to date (version 134.0.1 (64 bit)). Anyone else having this issue or know the solution?

I am a Cacti developer and we are considering switching from FontAwesome Web Fonts to Tabler Web Fonts. However, on Firefox for Windows only, we are having a major slowdown when using the Tabler SVG based webfonts. The page load is first stalled by Firefox apparently loading all the Web Fonts, which would appear normal with any browser (though exceedingly slow on Firefox for some reason).

However, once the page is loaded, when going off tab to another browser tab, and then back to the Firefox tab that includes the Tabler webfonts, there is a 3 second delay before the tab switches. When we enable the performance analyzer, we find that the delay is almost 100% Reflow of the page, even though the page is static as this point (no changes) from the last time it was activated.

We do not have this issue on Firefox for Linux, MS Edge or any other Chromium browser, only Firefox on Windows. I'm using the latest version 134. Should I be opening a bug?