Firefox Community Forum

For the last ~6 months, my Firefox Windows build has been stuck connecting to numerous websites. Whether I enable auto-detect proxy settings or no proxy settings at all, the same result happens. The websites hang and do not resolve. Occasionally, some of the new Firefox releases have improved this, but then they revert to not working. I'm about to give up on this platform and switch entirely to Chrome which never has this problem.

Has anyone else experienced this? How if at all have you been able to fix it?

I installed firefox a week ago, now in the middle of creating a x account I no longer can reach the internet on this browser, edge works, chrome works. IT SAYS AT THE TOP YOU MUST LOG IN T THIS NETWORK BEFORE YOU CAN AS THE INTERNET. IT LET ME CREATE 1/2 OF A X ACCOUNT.

Is this the reason millions of people are leaving firefox as AI has indicated? The fix is apparently try this for 2 pages. Please create a trouble shooting tool within firefox to fix this junk and I am deleting firefox, don't worry I will reload it 1 - 5 years and try again as I did 1 -5 years in the past.

As of recent I increasingly have issues with accessing websites, those websites previously (yesterday) worked fine on Firefox. Version is 148.0 on Mac 26.3 (Apple M3 Silicon).

Now it has completely stopped working. Only websites using direct IP-address still work, all others fail with "Hmm. We’re having trouble finding that site.". Safari still opens the websites flawlessly.

Nothing has changed on the OS level or application level as no updates have been installed (no need, as everything is up to date). Antivirus is BitDefender with extension for Firefox enabled for already an extended time (year or so).

I tried disabling several dns.resolver settings as mentioned in https://support.mozilla.org/en-US/kb/firefox-cant-load-websites-other-browsers-can. No improvement whatsoever.

I quit firefox, removed the cache manually and restarted while starting a new test profile, so completely blank. Issue is still there.

DNS Servers on OS-level are correct.

Version 148 was installed last night evening and as such could be the reason for the failure since it is basically the only thing that changed.

I get a message that says I must log into this network before I can access the internet then I get another message that says the page isn't direct redirecting properly Firefox has detected that the server is redirecting the request for this address in a way that will never be complete the problem can sometimes be solved back calls by disabling or refusing to accept cookies. I have done neither. don't understand what happened I was browsing and all of the sudden I'm not I guess I may have to switch my browser?

seit einigen Updatesversucht das System verschiedene Webseiten ohne Erfolg zu öffnen. Es erscheint keine Fehlermeldung, auch kein Abbruch wegen Zeitüberschreitung oder der Hinweis, dass der Server nicht erreichbar ist.

My home desktop computer is asking for a network login to access the internet today, after FireFox crashed. I do not see anywhere to login. Please help. I have a Mini Mac. I am at a library as my internet is not working.

After i installed firefox net jitter somehow appeared in my cs2. every time i play jitter is jumping randomly. Can yall somehow fix this i really enjoy using this browser but i just cant play with it running in the background((((

On a dual-stack network, with Windows tcpip6 ‘disabledcomponents’ parameter set to prefer IPv6, Firefox ignores this setting whenever an endpoint resolves both an IPv4 and a NAT64 address.

While monitoring traffic captured while connecting to sites in Firefox, if the initial DNS request for the site comes back with an IPv6 address only, the connection attempts from client’s IPv6 address to destination IPv6. If DNS answers come back with IPv4 and IPv6, the connection attempts IPv6 to IPv6. If DNS answers come back with IPv4 and a NAT64 address, Firefox doesn’t even attempt to connect to the NAT64 address, it immediately defaults to IPv4. I’ve tried disabling the IPv4 fallback setting which doesn’t change the behavior.

We’re running version 140.8.0esr. Is this behavior intended for Firefox? Is there a way to configure Firefox so it doesn’t ignore NAT64 addresses in dual-stack environments? The only way I found to force this was to completely disable the IPv4 stack on the client system’s NIC.

There are times when i am using Firefox that my PC will randomly disconnect from the internet. Sometimes it will reconnect on its own after I close Firefox. Other times I either have to restart my PC or go into Network & Internet settings and connect to my network. I am still running Window 10, free updates. Does anyone know what is causing this? It does not happen with any other browsers.