I-Firefox Community Forum

Hello. For years I've been successfully using your browser. Now it keeps giving messages that say "Try Again" .

We can’t connect to the server at links... bla blah

Server Not Found

...PLEASE ADVISE

The connection has timed out

The server at eofficepwd.kerala.gov.in is taking too long to respond.

   * itemThe site could be temporarily unavailable or too busy. Try again in a few moments.
   * If you are unable to load any pages, check your computer’s network connection.
   If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the web.

Within a minute of starting Firefox up, it loses internet connection and prevents the computer from connecting to anything else. Using Ethernet or Wifi doesn't work. The only thing that corrects it is restarting the computer. List of things we have tried: Troubleshooting Mode in Firefox Removing all addons Uninstalling and Reinstalling Firefox with the latest update Disabling DNS over HTTPS Clearing Firefox's DNS cache Clearing the computer's DNS cache Adding IPv6 to our standard IPv4 connection Rebooting the router Used a new Firefox profile Run a virus scan

This is on Windows 11. There are multiple other computers on the network, with W10 and W11, and none of them are having this issue. I've tried everything I can think of. After losing connection, it still pings 8.8.8.8.. Is there anything else we can try?

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.

i want to access www.fintreeindia.com i pursue professional courses that's my class website and also i could not access youtube also my exam are nearly

For so, me reason i have lost my connection to FireFox. It was in the last week. I was surprised because i have been using it for a few years. Can you help me to be able to use it again please?

BARRY HATHAWAY 14 SPINNERS COTTAGES LONGFORDS MILL MINCHINHAMPTON STROUD, GLOUCESTERSHIRE GL69LP. UK