Este site está com funcionalidades limitadas enquanto realizamos manutenção para melhorar sua experiência de uso. Se nenhum artigo resolver seu problema e você quiser fazer uma pergunta, nossa comunidade de suporte pode te ajudar em @FirefoxSupport no Twitter e /r/firefox no Reddit.

Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Saiba mais

Esta discussão foi arquivada. Faça uma nova pergunta se precisa de ajuda.

SSL certificate error - when the site is correct and works fine for other users using the same version - seems to be a random issue with latest build.

  • 3 respostas
  • 29 têm este problema
  • 2 visualizações
  • Última resposta de ktroutman

more options

Gets SSL invalid *This connection is untrusted.

Valid certificate - is a wildcard certificate, name match's destination. Worked without any issues in the older version of FireFox.

Gets SSL invalid *This connection is untrusted. Valid certificate - is a wildcard certificate, name match's destination. Worked without any issues in the older version of FireFox.

Todas as respostas (3)

more options

That certificate was just issued on July 16th. I wonder whether there was an old version cached on the problem PC or some other issue with the chain of trust up to the trusted root certificate?

more options

Hello, just wondering if anyone has found a solution for this? I'm running into the same problem with sites that I host with a valid VeriSign SSL wildcard certificate. It doesn't matter if the sites are on Apache or IIS, same error. IE and Chrome see the certificate fine. Firefox versions from 3.5 - 3.6.9 fail on some clients but not others. This appears to have just started happening recently.

Example https://recruitment.haas.berkeley.edu/Posting/FacultyJobs.aspx

Alterado por jonathont em

more options

I loaded the root certificate also in our IIS server and after a day the errors went away. My guess is some timing issue FireFox has with their browser - but I have yet to have them respond.