搜尋 Mozilla 技術支援網站

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

Learn More

Problem with COMODO ca certificate

  • 3 回覆
  • 6 有這個問題
  • 10063 次檢視
  • 最近回覆由 helper2424

more options

Hi, i have problem with ca comodo certificate. I bought the ssl wildcard certificate in COMODO, it's fine work in all browsers except some versions of firefox. I game developer, create game, it's game load xml from url https://fwassets.voltapps.ru/assetsSources/lobby/lobbyDescription.xml

and show security error (image attached). In error

wassets.voltapps.ru использует недействительный сертификат безопасности. К сертификату нет доверия, так как отсутствует цепочка сертификатов издателя. (Код ошибки: sec_error_unknown_issuer) {text in russian}

Exception reason is undefined ca comodo certificate. Undefined certificate you can see here http://fwassets.voltapps.ru/comododomain.cer .

Technical details: Mac os x yosemite firefox 35.0

Sorry for my english. Thanks for help

被選擇的解決方法

Thanks for help. Problem was at cdn provider, they delete intermediate certificates from ca-bundle file (In my web server all fine).

從原來的回覆中察看解決方案 👍 0

所有回覆 (3)

more options

This cert was already installed was the message I received when I tried. It might be that there is a default list of certs that are added when Firefox is installed.

This will tell you what version that it was added by default: https://www.mozilla.org/en-US/about/g.../included/ via https://docs.google.com/a/mozilla.com.../pub?key=0Ah-tHXMAwqU3dGx0cGFObG9QM192NFM4UWNBMlBaekE&single=true&gid=1&output=html

more options

Note that Firefox automatically stores intermediate certificates that servers send in the Certificate Manager for future usage. If a server doesn't send a full certificate chain then you won't get an untrusted error when Firefox has stored missing intermediate certificates from visiting a server in the past that has send it, but you do get an untrusted error if this intermediate certificate isn't stored yet.

You always need to test for possible server issues with a clean profile or temporarily rename the existing cert8.db.

You can inspect the certificate chain via a site like this:

more options

選擇的解決方法

Thanks for help. Problem was at cdn provider, they delete intermediate certificates from ca-bundle file (In my web server all fine).