Join the Mozilla’s Test Days event from Dec 2–8 to test the new Firefox address bar on Firefox Beta 134 and get a chance to win Mozilla swag vouchers! 🎁

Avatar for Username

Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Saber mais

Esta discussão foi arquivada. Se precisar de ajuda, por favor, coloque uma nova questão.

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

  • 1 resposta
  • 65 têm este problema
  • 1 visualização
  • Última resposta por guigs

frubio
frubio
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?

Todas as respostas (1)

guigs
guigs
more options

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

Modificado por guigs a