Safari can’t establish a secure connection to the server












5















I realize there is another question with the same title, but my situation is very different.




  • The problem started on three of my computers after upgrading from Leopard to Snow Leopard.


  • I can login to gmail and facebook using https with no problem.


  • I can not login to https://identi.ca/main/login or https://seminars.wolfram.com/ or https://panopticlick.eff.org with Safari, works fine with Firefox.


  • Already tried "Safari Reset..."



Any ideas?










share|improve this question

























  • Using Firefox, I have just discovered that both problematic sites use certificates issued by Comodo

    – gdelfino
    Jan 25 '10 at 14:22











  • Related: Why won't OS X trust GitHub's SSL certificate? and HTTPS certificates invalid on Safari, Chrome on specific user account.

    – Arjan
    Aug 17 '14 at 21:36
















5















I realize there is another question with the same title, but my situation is very different.




  • The problem started on three of my computers after upgrading from Leopard to Snow Leopard.


  • I can login to gmail and facebook using https with no problem.


  • I can not login to https://identi.ca/main/login or https://seminars.wolfram.com/ or https://panopticlick.eff.org with Safari, works fine with Firefox.


  • Already tried "Safari Reset..."



Any ideas?










share|improve this question

























  • Using Firefox, I have just discovered that both problematic sites use certificates issued by Comodo

    – gdelfino
    Jan 25 '10 at 14:22











  • Related: Why won't OS X trust GitHub's SSL certificate? and HTTPS certificates invalid on Safari, Chrome on specific user account.

    – Arjan
    Aug 17 '14 at 21:36














5












5








5


1






I realize there is another question with the same title, but my situation is very different.




  • The problem started on three of my computers after upgrading from Leopard to Snow Leopard.


  • I can login to gmail and facebook using https with no problem.


  • I can not login to https://identi.ca/main/login or https://seminars.wolfram.com/ or https://panopticlick.eff.org with Safari, works fine with Firefox.


  • Already tried "Safari Reset..."



Any ideas?










share|improve this question
















I realize there is another question with the same title, but my situation is very different.




  • The problem started on three of my computers after upgrading from Leopard to Snow Leopard.


  • I can login to gmail and facebook using https with no problem.


  • I can not login to https://identi.ca/main/login or https://seminars.wolfram.com/ or https://panopticlick.eff.org with Safari, works fine with Firefox.


  • Already tried "Safari Reset..."



Any ideas?







mac osx-snow-leopard safari https ident.ca






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 30 '10 at 15:25









MJeffryes

1,191614




1,191614










asked Nov 27 '09 at 13:19









gdelfinogdelfino

1221114




1221114













  • Using Firefox, I have just discovered that both problematic sites use certificates issued by Comodo

    – gdelfino
    Jan 25 '10 at 14:22











  • Related: Why won't OS X trust GitHub's SSL certificate? and HTTPS certificates invalid on Safari, Chrome on specific user account.

    – Arjan
    Aug 17 '14 at 21:36



















  • Using Firefox, I have just discovered that both problematic sites use certificates issued by Comodo

    – gdelfino
    Jan 25 '10 at 14:22











  • Related: Why won't OS X trust GitHub's SSL certificate? and HTTPS certificates invalid on Safari, Chrome on specific user account.

    – Arjan
    Aug 17 '14 at 21:36

















Using Firefox, I have just discovered that both problematic sites use certificates issued by Comodo

– gdelfino
Jan 25 '10 at 14:22





Using Firefox, I have just discovered that both problematic sites use certificates issued by Comodo

– gdelfino
Jan 25 '10 at 14:22













Related: Why won't OS X trust GitHub's SSL certificate? and HTTPS certificates invalid on Safari, Chrome on specific user account.

– Arjan
Aug 17 '14 at 21:36





Related: Why won't OS X trust GitHub's SSL certificate? and HTTPS certificates invalid on Safari, Chrome on specific user account.

– Arjan
Aug 17 '14 at 21:36










2 Answers
2






active

oldest

votes


















3














I had this problem as well. Adding new root authority certificates from Thawte fixed the problem. Apple has documentation on how to do this here http://docs.info.apple.com/article.h...en/mh2046.html



I added the root and server certificates that I downloaded from here
http://www.thawte.com/roots






share|improve this answer
























  • Thanks. Did you have to go through all the 8 directories and 14 subrectories double clicking on every .cer and .pem file? Did you add them to your login keychain or to the system keychain?

    – gdelfino
    Nov 27 '09 at 18:27






  • 1





    There are dozens of certificates in that download. Which one do I need?

    – gdelfino
    Jan 25 '10 at 14:02



















1














I have just solved this problem by following this procedure published by phurd99 in the Apple Support Forums:




  1. Open applications

  2. Utiliities

  3. Open Keychain

  4. Click Keychain Access and select Preferences.

  5. Click the "Reset My Default Keychain"


(...)



http://discussions.apple.com/thread.jspa?threadID=2138178&start=15&tstart=0



This solves the problem but you are left without you precious keychain (a backup is saved).



Then, using the backup and trial and error I discovered that by deleting one specific certificate, the problem is solved:



UNT-USERFirst-Hardware

Intermediate certificate authority

Note: This certificate is signed by an untrusted issuer






share|improve this answer





















  • 1





    [+1] Searching for UNT-USERFirst-Hardware revealed 2 such certificates on my machine. One indeed was noted as signed by an untrusted issuer. So I just deleted this certificate and my HTTPS problems with Safari were gone! I couldn't use MobileMe on my MBA because of this. Thank you very much!

    – Marc
    Dec 12 '10 at 21:12











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f75960%2fsafari-can-t-establish-a-secure-connection-to-the-server%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes









3














I had this problem as well. Adding new root authority certificates from Thawte fixed the problem. Apple has documentation on how to do this here http://docs.info.apple.com/article.h...en/mh2046.html



I added the root and server certificates that I downloaded from here
http://www.thawte.com/roots






share|improve this answer
























  • Thanks. Did you have to go through all the 8 directories and 14 subrectories double clicking on every .cer and .pem file? Did you add them to your login keychain or to the system keychain?

    – gdelfino
    Nov 27 '09 at 18:27






  • 1





    There are dozens of certificates in that download. Which one do I need?

    – gdelfino
    Jan 25 '10 at 14:02
















3














I had this problem as well. Adding new root authority certificates from Thawte fixed the problem. Apple has documentation on how to do this here http://docs.info.apple.com/article.h...en/mh2046.html



I added the root and server certificates that I downloaded from here
http://www.thawte.com/roots






share|improve this answer
























  • Thanks. Did you have to go through all the 8 directories and 14 subrectories double clicking on every .cer and .pem file? Did you add them to your login keychain or to the system keychain?

    – gdelfino
    Nov 27 '09 at 18:27






  • 1





    There are dozens of certificates in that download. Which one do I need?

    – gdelfino
    Jan 25 '10 at 14:02














3












3








3







I had this problem as well. Adding new root authority certificates from Thawte fixed the problem. Apple has documentation on how to do this here http://docs.info.apple.com/article.h...en/mh2046.html



I added the root and server certificates that I downloaded from here
http://www.thawte.com/roots






share|improve this answer













I had this problem as well. Adding new root authority certificates from Thawte fixed the problem. Apple has documentation on how to do this here http://docs.info.apple.com/article.h...en/mh2046.html



I added the root and server certificates that I downloaded from here
http://www.thawte.com/roots







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 27 '09 at 13:51









admintechadmintech

6,72812241




6,72812241













  • Thanks. Did you have to go through all the 8 directories and 14 subrectories double clicking on every .cer and .pem file? Did you add them to your login keychain or to the system keychain?

    – gdelfino
    Nov 27 '09 at 18:27






  • 1





    There are dozens of certificates in that download. Which one do I need?

    – gdelfino
    Jan 25 '10 at 14:02



















  • Thanks. Did you have to go through all the 8 directories and 14 subrectories double clicking on every .cer and .pem file? Did you add them to your login keychain or to the system keychain?

    – gdelfino
    Nov 27 '09 at 18:27






  • 1





    There are dozens of certificates in that download. Which one do I need?

    – gdelfino
    Jan 25 '10 at 14:02

















Thanks. Did you have to go through all the 8 directories and 14 subrectories double clicking on every .cer and .pem file? Did you add them to your login keychain or to the system keychain?

– gdelfino
Nov 27 '09 at 18:27





Thanks. Did you have to go through all the 8 directories and 14 subrectories double clicking on every .cer and .pem file? Did you add them to your login keychain or to the system keychain?

– gdelfino
Nov 27 '09 at 18:27




1




1





There are dozens of certificates in that download. Which one do I need?

– gdelfino
Jan 25 '10 at 14:02





There are dozens of certificates in that download. Which one do I need?

– gdelfino
Jan 25 '10 at 14:02













1














I have just solved this problem by following this procedure published by phurd99 in the Apple Support Forums:




  1. Open applications

  2. Utiliities

  3. Open Keychain

  4. Click Keychain Access and select Preferences.

  5. Click the "Reset My Default Keychain"


(...)



http://discussions.apple.com/thread.jspa?threadID=2138178&start=15&tstart=0



This solves the problem but you are left without you precious keychain (a backup is saved).



Then, using the backup and trial and error I discovered that by deleting one specific certificate, the problem is solved:



UNT-USERFirst-Hardware

Intermediate certificate authority

Note: This certificate is signed by an untrusted issuer






share|improve this answer





















  • 1





    [+1] Searching for UNT-USERFirst-Hardware revealed 2 such certificates on my machine. One indeed was noted as signed by an untrusted issuer. So I just deleted this certificate and my HTTPS problems with Safari were gone! I couldn't use MobileMe on my MBA because of this. Thank you very much!

    – Marc
    Dec 12 '10 at 21:12
















1














I have just solved this problem by following this procedure published by phurd99 in the Apple Support Forums:




  1. Open applications

  2. Utiliities

  3. Open Keychain

  4. Click Keychain Access and select Preferences.

  5. Click the "Reset My Default Keychain"


(...)



http://discussions.apple.com/thread.jspa?threadID=2138178&start=15&tstart=0



This solves the problem but you are left without you precious keychain (a backup is saved).



Then, using the backup and trial and error I discovered that by deleting one specific certificate, the problem is solved:



UNT-USERFirst-Hardware

Intermediate certificate authority

Note: This certificate is signed by an untrusted issuer






share|improve this answer





















  • 1





    [+1] Searching for UNT-USERFirst-Hardware revealed 2 such certificates on my machine. One indeed was noted as signed by an untrusted issuer. So I just deleted this certificate and my HTTPS problems with Safari were gone! I couldn't use MobileMe on my MBA because of this. Thank you very much!

    – Marc
    Dec 12 '10 at 21:12














1












1








1







I have just solved this problem by following this procedure published by phurd99 in the Apple Support Forums:




  1. Open applications

  2. Utiliities

  3. Open Keychain

  4. Click Keychain Access and select Preferences.

  5. Click the "Reset My Default Keychain"


(...)



http://discussions.apple.com/thread.jspa?threadID=2138178&start=15&tstart=0



This solves the problem but you are left without you precious keychain (a backup is saved).



Then, using the backup and trial and error I discovered that by deleting one specific certificate, the problem is solved:



UNT-USERFirst-Hardware

Intermediate certificate authority

Note: This certificate is signed by an untrusted issuer






share|improve this answer















I have just solved this problem by following this procedure published by phurd99 in the Apple Support Forums:




  1. Open applications

  2. Utiliities

  3. Open Keychain

  4. Click Keychain Access and select Preferences.

  5. Click the "Reset My Default Keychain"


(...)



http://discussions.apple.com/thread.jspa?threadID=2138178&start=15&tstart=0



This solves the problem but you are left without you precious keychain (a backup is saved).



Then, using the backup and trial and error I discovered that by deleting one specific certificate, the problem is solved:



UNT-USERFirst-Hardware

Intermediate certificate authority

Note: This certificate is signed by an untrusted issuer







share|improve this answer














share|improve this answer



share|improve this answer








edited Dec 3 '15 at 22:30

























answered Mar 12 '10 at 1:39









gdelfinogdelfino

1221114




1221114








  • 1





    [+1] Searching for UNT-USERFirst-Hardware revealed 2 such certificates on my machine. One indeed was noted as signed by an untrusted issuer. So I just deleted this certificate and my HTTPS problems with Safari were gone! I couldn't use MobileMe on my MBA because of this. Thank you very much!

    – Marc
    Dec 12 '10 at 21:12














  • 1





    [+1] Searching for UNT-USERFirst-Hardware revealed 2 such certificates on my machine. One indeed was noted as signed by an untrusted issuer. So I just deleted this certificate and my HTTPS problems with Safari were gone! I couldn't use MobileMe on my MBA because of this. Thank you very much!

    – Marc
    Dec 12 '10 at 21:12








1




1





[+1] Searching for UNT-USERFirst-Hardware revealed 2 such certificates on my machine. One indeed was noted as signed by an untrusted issuer. So I just deleted this certificate and my HTTPS problems with Safari were gone! I couldn't use MobileMe on my MBA because of this. Thank you very much!

– Marc
Dec 12 '10 at 21:12





[+1] Searching for UNT-USERFirst-Hardware revealed 2 such certificates on my machine. One indeed was noted as signed by an untrusted issuer. So I just deleted this certificate and my HTTPS problems with Safari were gone! I couldn't use MobileMe on my MBA because of this. Thank you very much!

– Marc
Dec 12 '10 at 21:12


















draft saved

draft discarded




















































Thanks for contributing an answer to Super User!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f75960%2fsafari-can-t-establish-a-secure-connection-to-the-server%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

Mangá

 ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕