Hotmail untrusted connection,why?
All these while i have been using Hotmail and it's fine.Until recently,after i log in Hotmail it will say
"We can't connect to Outlook.com right now. Please try again later."
then after i refresh it said
"This Connection is Untrusted
You have asked Firefox to connect securely to bay174.mail.live.com, but we can't confirm that your connection is secure.
Normally, when you try to connect securely, sites will present trusted identification to prove that you are going to the right place. However, this site's identity can't be verified. What Should I Do?
If you usually connect to this site without problems, this error could mean that someone is trying to impersonate the site, and you shouldn't continue. " i had seen Hotmail asking others to contact Mozilla to solve this problem instead.
Изабрано решење
Hi Conson, the idea behind renaming cert8.db to oldcert8.db is to cause Firefox to ignore the old file and start a new one. I don't think there is an add-on that would work better for that purpose.
As for how to interpret "data base file" that is exactly the problem: we have no idea what your system means by "data base file" since that definition for the file extension depends on what is stored in your Windows registry and can be changed by applications.
That said, there's normally no other cert8 file in Firefox's profile folder, so that's probably the right one. And if chaos ensues, you can rename it back.
By the way, please make sure Firefox is fully closed before renaming any settings files.
Прочитајте овај одговор са објашњењем 👍 0Сви одговори (2)
Hi Conson, I think there might be an error in the SSL test page. If you check the SAN list (just below what I can see on your screen shot, do you see your server there? If so, try adding the exception again.
By the way, if you go directly to the following URL, do you also get an error page and, if so, does it also lack the ability to add an exception?
Not sure if it's relevant to you, but another user who had a problem with bay174.mail.live.com discovered that it was caused by Replay Media Catcher changing some proxy settings. This post has more info on how to fix those settings:
https://support.mozilla.org/questions/1033421?page=1#answer-694823