This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

Firefox says "No internet connection" after 10/11/2023 update to 118.0.2(64 bit)

  • 1 antwoord
  • 1 het hierdie probleem
  • 8 views
  • Laaste antwoord deur Old1912

jean.powell
jean.powell
more options

Since Firefox updated to 118.0.2 yesterday evening, it will work fine for a few minutes and then, usually when I am trying to open an email, a pop up appears that says "No internet connection" and no other websites will load. The problem does not occur on other browsers. I made no other changes to my Firefox settings or add-ons nor did I change any security settings. Help!

Since Firefox updated to 118.0.2 yesterday evening, it will work fine for a few minutes and then, usually when I am trying to open an email, a pop up appears that says "No internet connection" and no other websites will load. The problem does not occur on other browsers. I made no other changes to my Firefox settings or add-ons nor did I change any security settings. Help!

All Replies (1)

Old1912
Old1912
more options

I got similar error messages since 117.x.x. It would happen on tabs with email services open (both Yahoo and Gmail), but other tabs were not affected. My windows 10 system said there was network connectivity. My network provider is T-Mobile Home Internet which uses cellular. After installing a VPN product, all upload/download speeds increased and I no longer am affected by this situation. Not sure if this applies to your case, but in my case it appeared to be a timing issue with FF not waiting long enough for a response.

Gewysig op deur Old1912