Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

SEC_ERROR_UNKNOWN_ISSUER on https://discordapp.com

  • 1 답장
  • 2 이 문제를 만남
  • 108 보기
  • 최종 답변자: were.weasel

more options

Firefox refuses to visit https://discordapp.com, complaining about SEC_ERROR_UNKNOWN_ISSUER. Upon inspection of the certificates, the root CA is "COMODO ECC Certification Authority" - Serial Number 16:E5:86:78:E0:70:94:39:4B:DF:DB:4E:FC:A6:3B:DF.

The Firefox certificate manager contains a trusted entry for "COMODO ECC Certification Authority", however it is a different cert with serial number 1F:47:AF:AA:62:00:70:50:54:4C:01:9E:9B:63:99:2A.

I'm wondering what's the cause of this situation? Did Comodo recently change certificates? Can somebody else check which version of the "COMODO ECC Certification Authority" is shipped with their FF?

Firefox refuses to visit https://discordapp.com, complaining about SEC_ERROR_UNKNOWN_ISSUER. Upon inspection of the certificates, the root CA is "COMODO ECC Certification Authority" - Serial Number 16:E5:86:78:E0:70:94:39:4B:DF:DB:4E:FC:A6:3B:DF. The Firefox certificate manager contains a trusted entry for "COMODO ECC Certification Authority", however it is a different cert with serial number 1F:47:AF:AA:62:00:70:50:54:4C:01:9E:9B:63:99:2A. I'm wondering what's the cause of this situation? Did Comodo recently change certificates? Can somebody else check which version of the "COMODO ECC Certification Authority" is shipped with their FF?

선택된 해결법

I have the same Comodo root certificate as you. If there are certificate issue then this is more likely an issue with the intermediate certificate, in this case "COMODO ECC Domain Validation Secure Server CA 2".

You can try to rename the cert9.db file (cert9OLD.db) and remove the previously used cert8.db file in the Firefox profile folder with Firefox closed to remove intermediate certificates and exceptions that Firefox has cached.

If this has helped to solve the problem then you can remove the renamed cert9OLD.db file. Otherwise you can undo the rename and restore cert9.db.

You can use the button on the "Help -> Troubleshooting Information" (about:support) page to go to the current Firefox profile folder or use the about:profiles page.

문맥에 따라 이 답변을 읽어주세요 👍 1

모든 댓글 (2)

more options

선택된 해결법

I have the same Comodo root certificate as you. If there are certificate issue then this is more likely an issue with the intermediate certificate, in this case "COMODO ECC Domain Validation Secure Server CA 2".

You can try to rename the cert9.db file (cert9OLD.db) and remove the previously used cert8.db file in the Firefox profile folder with Firefox closed to remove intermediate certificates and exceptions that Firefox has cached.

If this has helped to solve the problem then you can remove the renamed cert9OLD.db file. Otherwise you can undo the rename and restore cert9.db.

You can use the button on the "Help -> Troubleshooting Information" (about:support) page to go to the current Firefox profile folder or use the about:profiles page.

more options

cor-el said

If there are certificate issue then this is more likely an issue with the intermediate certificate, in this case "COMODO ECC Domain Validation Secure Server CA 2". You can try to rename the cert9.db file (cert9OLD.db) and remove the previously used cert8.db file in the Firefox profile folder with Firefox closed to remove intermediate certificates and exceptions that Firefox has cached.

Deleting cert9.db has indeed resolved the problem. Now FF displays 1F:47:AF:... as root signatory of the discordapp.com certificate. Interestingly, only deleting the cached intermediate certificate (COMODO ECC Domain Validation Secure Server CA 2) in the certificate manager was not enough. So I'm still quite clueless how exactly this issue was caused. Anyway, thanks for your help.