Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Firefox tells it is unable to get identification status for a given site?

  • 1 reply
  • 65 have this problem
  • 1 view
  • Last reply by guigs

more options

I have a server for which I have created a self-signed CA. Using this CA, I have signed a wildcard server certificate. I have imported both certs to my Firefox, asking Firefox to trust CA.pem for everything.

However, when I try to load the page I get a window saying the connection is untrusted (Error code: sec_error_untrusted_cert) and I can not even add an exception (unable to obtain identification status for the given site), even when konqueror shows the site flawlessly and both certs are shown as trusted.

I have already tried removing cert8.db unsuccessfully. Does anybody know how to fix this problem?

I have a server for which I have created a self-signed CA. Using this CA, I have signed a wildcard server certificate. I have imported both certs to my Firefox, asking Firefox to trust CA.pem for everything. However, when I try to load the page I get a window saying the connection is untrusted (Error code: sec_error_untrusted_cert) and I can not even add an exception (unable to obtain identification status for the given site), even when konqueror shows the site flawlessly and both certs are shown as trusted. I have already tried removing cert8.db unsuccessfully. Does anybody know how to fix this problem?

All Replies (1)

more options

This is one of the known issues for this release. We are working hard on fixing it.Release notes Bug 995801

Modified by guigs