I have had this issue for 3 days now. I am unable to access yahoo mail or yahoo in general because I get warning potential risk ahead message. I had to make twitter… (閱讀更多)
I have had this issue for 3 days now. I am unable to access yahoo mail or yahoo in general because I get warning potential risk ahead message. I had to make twitter account to be able to get in touch with yahoo support but they just offered a yahoo link which, of course, I am unable to open because of "potential risk ahead". I tried solutions suggested by people here at mozilla support, like clearing history, cache etc but it didn't work. I also tired accessing yahoo via internet explorer and chrome (installed on my father's laptop, windows 10) Of course same message appears. I am using windows 7 64 bit. I also tried Edge and of course it says yahoo site is not secure. I have never had these kind of problems before. I was always able to access yahoo via FIrefox and other browsers. It's really damn annoying because i see no solution to this damn crap. Also I am unable to upload a 170kb screenshot to show you the issue. Just keeps loading and loading and it doesn't stop. So I guess I will just have to describe it:
Firefox detected a potential security threat and did not continue to guce.yahoo.com. If you visit this site, attackers could try to steal information like your passwords, emails, or credit card details.
What can you do about it?
The issue is most likely with the website, and there is nothing you can do to resolve it. You can notify the website’s administrator about the problem.
Websites prove their identity via certificates. Firefox does not trust this site because it uses a certificate that is not valid for guce.yahoo.com. The certificate is only valid for *.amz-aws.jp. Error code: SSL_ERROR_BAD_CERT_DOMAIN
https://guce.yahoo.com/consent?gcrumb=gscOGxw&trapType=login&done=https%3A%2F%2Fwww.yahoo.com%2F&src= Unable to communicate securely with peer: requested domain name does not match the server’s certificate. HTTP Strict Transport Security: false HTTP Public Key Pinning: false