Search for the issuing certificate authority (in this case, Comodo). The linked article hinted at the right thing to do, but here's what worked for me: I even tried using open_ssl at the command line, but also it failed: echo ^d | openssl s_client -connect :443 | tee cert.logĦ480:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure:/SourceCache/OpenSSL098/OpenSSL098-52.40.1/src/ssl/s23_lib.c:185:įinally, I was able to open the website on an old machine with Internet Explorer version 9, and found the name of the certificate authority: Comodo Certification Authority. I got no love here, since every browser refused to negotiate a connection far enough to get the name of the certificate issuer. I tried to follow the advice here, which involved getting information about the root certificate used by the offending website via the web browser: How to fix: Safari can’t open the page because Safari can’t establish a secure connection It also affected all of the browsers I commonly use (Firefox, Chrome, Chrome Canary). 
This just reared its ugly head again, this time with Yosemite. I'm not even sure where to look for those - maybe ~/Library/? If I had to guess, I would think that wherever Safari is checking for "certificates" is somehow corrupted, but I could be wrong. Google Chrome has no problems connecting to HTTPS sites.Īll of the google results I saw suggested either repairing the Keychain (which I tried and which did not help) or were only applicable if there were "Parental Controls" involved, which doesn't apply here. This is on an administrator account, not a managed account.Ī different administrator account is able to use Safari with HTTPS, so must be something specific to my account, but I have no idea what. Safari suddenly can't connect to any HTTPS site because it "can't establish a secure connection".
0 kommentar(er)
