Firefox Not Connecting to Internet
I've used Firefox on this same Mac for several years without a problem. Suddenly, this morning, the browser stopped working. Since then, I've cleared cookies and cache, and uninstalled and reinstalled Firefox. Still, no matter the website I try to connect with, I get the same message, "Hmm. We're having trouble finding that site." According to Mozilla, my Mac OS, 10.14.6, is still supported. Help!
被選擇的解決方法
Some problems occur when your Internet security program was set to trust the previous version of Firefox, but no longer recognizes your updated version as trusted. Now how to fix the problem: To allow Firefox to connect to the Internet again;
- Make sure your Internet security software is up-to-date (i.e. you are running the latest version).
- Remove Firefox from your program's list of trusted or recognized programs. For detailed instructions, see
Configure firewalls so that Firefox can access the Internet. {web link}
從原來的回覆中察看解決方案 👍 0所有回覆 (4)
I should also note that Chrome seems to be connecting to internet, but Safari is not. My version of Firefox is 94.0.1.
選擇的解決方法
Some problems occur when your Internet security program was set to trust the previous version of Firefox, but no longer recognizes your updated version as trusted. Now how to fix the problem: To allow Firefox to connect to the Internet again;
- Make sure your Internet security software is up-to-date (i.e. you are running the latest version).
- Remove Firefox from your program's list of trusted or recognized programs. For detailed instructions, see
Configure firewalls so that Firefox can access the Internet. {web link}
Thanks, Fred. As with so many of these issues, I'm not sure what solved the problem. I just kept throwing ideas, including yours at it, then turned off the computer, let it rest, and -- amazingly -- I'm back in business. I think you were on to something about security protocols, however, since Safari and Messages both went offline, as well as Firefox. Thanks for your help, R
Glad to help. Safe Surfing.
It might have been a corrupted or locked file.