Firefox Community Forum

HTTPS pages are no longer loading. Everything works fine in Microsoft Edge. I've reinstalled Firefox several times – the problem persists. Thank you very much for your help.

After running updates and restarting my computer, I am no longer able to open my common websites used frequently. I don't know how to fix this problem. The search bar runs until it times out.

After the most recent upgrades (both MacOS to 26.4 beta and Firefox 147.0.4), Firefox is giving me this message: Hmm. We’re having trouble finding that site. Any suggestions?

Hello everyone,

We are currently investigating an issue where browsers are sending HTTP requests with Connection: close in the header during integrated Windows authentication (NTLM authentication) via SAML Service Provider (SP), leading to premature termination of the TCP connection.

This behavior occurs in the middle of the authentication process, preventing the NTLM authentication from completing and subsequently prompting for re-authentication.

We have observed the following browser behaviors:

Chrome and Edge: These browsers function without issues, communicating with Connection: keep-alive. Safari (macOS): Older versions of macOS with Safari exhibit the Connection: close behavior, leading to authentication failure. Newer versions of macOS with Safari work correctly with Connection: keep-alive. Firefox (macOS): Even on the latest versions of macOS, Firefox continues to attach Connection: close, resulting in authentication failure. Upon reviewing logs, we've identified that various browsers attach the Connection: close header during the NTLMSSP_NEGOTIATE request in the NTLM authentication sequence. Although this happens in an environment with a load balancer, we have confirmed that the load balancer is not modifying the header; rather, the client (browser) is adding it.

We would appreciate your insights into the conditions under which Firefox attaches Connection: close to HTTP requests, especially considering the differences across macOS versions and other browsers, addressing the following points:

Are there any known conditions or past cases where Firefox outputs Connection: close in an NTLM authentication environment via SAML SP? Given that older Safari versions show similar behavior, we are also considering if there's a common factor depending on NTLM authentication and browser version. What are the general heuristics, logic, or triggers for a browser to decide to "close" a connection or to attach Connection: close? We are particularly interested in cases that occur mid-authentication process. Could specific configurations (e.g., the combination of SAML and NTLM authentication, or the presence of an intermediate proxy/load balancer) potentially influence Firefox's Connection: close behavior? Are there any additional logs or debugging information we should collect from the Firefox client side to further pinpoint this issue? Any guidance or suggestions you could provide to help us resolve this problem would be greatly appreciated.

Thank you.

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.

Hi, all experienced peoples are here I got strange issue with firefox lately. my site sometimes https://avsogirl.net/ not loads at all, just shows “server not found” look at the image.

i first thought maybe server down, but i checked with curl and ping, server responds fine. also tested same site in chrome and edge, loads normal there, no error. i tried clearing cache, disabling addons, even fresh profile. still same. only firefox gives this dns error.

i use dns-over-https in firefox, and i also have proxy config for work. maybe firefox handling dns/proxy different? when i switch off doh, sometimes page loads, sometimes not. so looks like firefox network stack problem, not site issue. anyone else facing same error?

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.

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.

Hi, When I click on a link in ANY email, it says " Hmm. We’re having trouble finding that site. We can’t connect to the server at omxj86ebb.cc.rs6.net. If you entered the right address, you can:

   Try again later
   Check your network connection
   Check that Firefox has permission to access the web (you might be connected but behind a firewall)

I know I did something to make my computer more secure, but don't remember. Please help! THANK YOU!

I have been using Firefox for last couple of years. Two days ago I got a bunch of updates, which reminded be of how AOL used to update, ie days of confusion.

SO NOW I CANT EVEN GET ON INTERNET! So here am a few days before Christmas, and can't access my bank account, or stocks. And I had no idea Firefox was going to institute these changes.

I can't express how stupid these unauthorized changes have been (without notification!) to users. Please remove this crap ASAP, and demote the group that thought a week before Christmas was a good time to make changes.

every time i launch Firefox, I get the banner prompting me to log in to network so i can access to the internet, i don´t understand it , cos I see that I am both logged in and connected to the net ?

Hi I have switched to Mozilla from Chrome as I can’t update latest OS for my Mac. I can only browse internet intermittently and just want to ask if there are any settings I need to change on Firefox? Thanks Aidan