Avatar for Username

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信，及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

话题已存档。 如果需要帮助请提出新问题。

SEC_ERROR_UNKNOWN_ISSUER on https://discordapp.com

  • 1 个回答
  • 2 人有此问题
  • 1 次查看
  • 最后回复者为 were.weasel

were.weasel
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)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
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.

were.weasel
were.weasel 提问者
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.