On Aug 14th 11 PM ET/Aug 15th 03:00 UTC, due to scheduled Firefox Account server maintenance, users may not be able to sign in or create a new subscription. This is expected to last approximately 30 minutes. Status updates can be found at https://status.vpn.mozilla.org or https://status.relay.firefox.com.

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

Learn More

Can't fix SEC_ERROR_REUSED_ISSUER_AND_SERIAL as described

  • 1 回覆
  • 1 有這個問題
  • 59 次檢視
  • 最近回覆由 FredMcD

more options

Hi all,

while playing (or better "fighting"...) with a linux docker container on Win10/WSL2/Ubuntu for using the MS spfx tool chain, I generated a SEC_ERROR_REUSED_ISSUER_AND_SERIAL in FF85.0/Win10 by first setting up a certificate exception for a dev-cert (https://localhost:4321) and then have the certificate re-created.

As described the support article [https://support.mozilla.org/en-US/kb/Certificate-contains-the-same-serial...], I removed all certificate exceptions for localhost:* and deleted the "gulp" authority in options/security/certificates.

Unfortunately, the SEC_ERROR_REUSED_ISSUER_AND_SERIAL persists even after a restart of firefox.

Any help is very much appreciated...

Thanks & greetings Markus Fehn

Hi all, while playing (or better "fighting"...) with a linux docker container on Win10/WSL2/Ubuntu for using the MS spfx tool chain, I generated a SEC_ERROR_REUSED_ISSUER_AND_SERIAL in FF85.0/Win10 by first setting up a certificate exception for a dev-cert (https://localhost:4321) and then have the certificate re-created. As described the support article [[https://support.mozilla.org/en-US/kb/Certificate-contains-the-same-serial-number-as-another-certificate]], I removed all certificate exceptions for localhost:* and deleted the "gulp" authority in options/security/certificates. Unfortunately, the SEC_ERROR_REUSED_ISSUER_AND_SERIAL persists even after a restart of firefox. Any help is very much appreciated... Thanks & greetings Markus Fehn

所有回覆 (1)

more options