FireFox is suddenly having a google certificate problem
Starting only today, I suddenly can't access https google. I get the message "The page you are trying to view cannot be shown because the authenticity of the received data could not be verified." Things I've already tried: 1. Updated to FF 50.1.0 2. Safe Mode 3. Deleted cert8.db file 4. Tried to add exception but when typing the google url FF comes up empty (no certificate provided)
I'm on an iMac running El Capitain and I have no AnitVirus software what so ever. This is driving me nuts. Any ideas would be appreciated.
Chosen solution
If your service provider is TEdata or Etisalat, power cycling your router (unplugging it and then plugging it back in) might help temporarily.
See also:
- Cannot open https://www.google.com/ or search through firefox searchbar or address bar, always get Secure Connection Failed
- "secure connection failed" for google .com
All Replies (4)
Does your system have the correct date?
Please try what is detailed at Secure connection failed and Firefox did not connect.
Kindly let us know if this solves your question.
Thanks for the reply Alex. I forgot to mention that yes I did check the date and time. It was part of the many solution suggestions I read about extensively before I posted my problem. It is also worth noting that when I just type "google.com" it takes me to google.com.eg successfully, but when I use the search bar (which by default refers me to https://www.google.com) that's when I get the certificate problem error. Very strange. And like I said, this only started yesterday with not a single change made to my FF setup in ages!
Chosen Solution
If your service provider is TEdata or Etisalat, power cycling your router (unplugging it and then plugging it back in) might help temporarily.
See also:
Thanks a bunch jscher200. I'm actually on TEdata, and strangely enough a router power cycling did resolve the issue immediately. Of all the things I tried this never crossed my mind. From the looks of it, this might be a recurring problem, but at least now I have a quick fix. Thanks